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 [ 04 | August | 2003 ]

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


Date: Mon, 4 Aug 2003 11:53:07 PDT7
From: Peter Skye <pskye@peterskye.com >
Reply-To: scoug-programming@scoug.com
To: scoug-programming@scoug.com
Subject: SCOUG-Programming: Re: Warpstock 2003 Presentation

Content Type: text/plain

Lynn H. Maxson wrote:
>
> While "faster, better, cheaper" makes good for
> comparison purposes it also represents an
> iterative goal we should have in improving software.

I agree that the iterative approach should be the expected norm; in
fact, only a demonic egotistical eccentric would dare to say that they
could write programs that were always bug-free and always designed
perfectly, and hence never required any "iterations".

> You make a strange argument, logically inconsistent,
> which I have to comment upon here. If the assembly
> language programmer knows that no sort field will exceed
> 16 characters, he can incorporate that in his code. The
> HLL programmer, having the same knowledge as the assembly
> programmer, can do it also. The difference lies in how
> that is communicated to the software tool.

If the HLL programmer has the same knowledge as the assembly language
programmer and writes using the best-fit optimizations for the specific
problem, then as far as I can tell there won't be any difference between
the set of statements written by each of them. Thus, there's no
differentiation between the HLL source and the assembly source. Thus,
your argument is stranger than mine is. :)))

But if the assembly guy writes a full sort routine without using a
library and the HLL guy sorts by using "CALL SORT p1,p2,...pn" then we
have a situation where the HLL code appears to be a higher level than
assembler but the desired optimization is impossible. Lynn, can you
show me some actual code for a hypothetical HLL sort routine written for
a specific case? I don't want a theoretical paragraph relegating a
concrete example to irrelevance; I want instead to see the concrete
example.

- Peter

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

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 [ 04 | August | 2003 ]



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.