SCOUG Logo


Next Meeting: Sat, TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!










SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999

The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2024, Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.

The Southern California OS/2 User Group
USA

SCOUG-Programming Mailing List Archives

Return to [ 03 | January | 2004 ]

<< Previous Message << >> Next Message >>


Date: Sat, 3 Jan 2004 22:51:05 PST8
From: "Bob" <tt336a5u02@sneakemail.com >
Reply-To: scoug-programming@scoug.com
To: scoug-programming@scoug.com
Subject: SCOUG-Programming: QA equals testing, Part One:Detection

** Reply to message from "Peter Skye pskye@peterskye.com" on Sat, 3 Jan 2004
22:12:50 PST8

> Let's read a simple text file. Sometimes the lines end with CR,
> sometimes with CR LF, sometimes with LF CR, sometimes with CR CR LF,
> sometimes with CR LF FF, and sometimes with FF. And what about those
> VTs? Is CR LF LF one line or two? *And*, should my output use whatever
> the input file was using, or should I use my own arbitrary choice (which
> happens to be CR LF).

This problem will never be solved. If you get data from a foreign (operating
system other than the one you are using) source you will definitely need to
know the file structure. In this case nothing has changed since the second
computer was built.

> Have I given enough examples? If a programmer doesn't _understand_ his
> system then he cannot write great software. And he cannot understand
> what he cannot see.

I said the programmer did not need to know the hardware instruction set, I
never said the programmer did not need to know the basics of the operating
system he is using. Depending on what a programmer needs to do there is a wide
variation of knowledge needed, sometimes very little sometimes a great deal.

I had some college students living next door at one time. Some of them were
taking a COBOL programming class. They never saw the computer, did not know
what an operating system was, but were expected to write a program. They were
given the input and output file name and told what transformation was to be
done. You do not need to know the hardware or operating system to write the
program. I helped them and never bothered to ask about the hardware or
operating system, I did not care.

--
Robert Blair

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-programming".

For problems, contact the list owner at
"rollin@scoug.com".

=====================================================


<< Previous Message << >> Next Message >>

Return to [ 03 | January | 2004 ]



The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA

Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.