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 [ 11 | January | 2006 ]


Date: Wed, 11 Jan 2006 22:22:41 PST8
From: Sheridan George <s-geo@usa.net >
Reply-To: scoug-programming@scoug.com
To: scoug-programming <scoug-programming@scoug.com >
Subject: SCOUG-Programming: Pushing ahead

Content Type: text/plain

It has occurred to me to asking Greg to compare Watcom and gcc is misplaced at this time (he hasn't
been given any presentation time to do so anyhow). While we do need to know, at some point, which
compiler would be best, I don't think now is the time.

In order to put Lynn's idea into play we should be laying out the requirements for the editor that
is to be the driving force behind his "compiling system". After all we will have to make major
changes to whatever editor we choose to modify. Those changes need to be discussed in detail and
the results of the discussion put to paper.

The way I understand it the editor not only will have the standard duty of managing screen data and
attendant files but must interface with three or four databases to implement the full system. Plus
it must know about the features of PL1 and APL (if I have my compilers correct) so the desired data
set and character set can be accommodated and color coded.

I'm of the opinion that programming is 50% planning/design/layout, 25% algorithm design, 10% coding,
and 15% smashing inadvertent bugs. I would like to get started planning the system. As we plan and
break the larger problem down into smaller and smaller pieces we will finally be faced with which
compiler to use/modify. By then we should have a better idea of what compiler facilities we need.
It will probably give us better insight on how much the compiler must be changed. That may make our
decision (as to which one) for us.

I'm sure I've butchered Lynn's idea sufficiently for him to set me straight. That will be good
because it will refresh our thinking and serve as a basis of planning. Let's get started.

Sheridan

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

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
"postmaster@scoug.com".

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


Return to [ 11 | January | 2006 ]



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.