Path: utzoo!utgpu!news-server.csri.toronto.edu!torsqnt!hybrid!torag!utdoe!generic!pnet91!ericmcg
From: ericmcg@pnet91.cts.com (Eric Mcgillicuddy)
Newsgroups: comp.sys.apple2
Subject: Re: Re- HLLs vs. Assembly
Message-ID: <660@generic.UUCP>
Date: 26 Apr 91 23:15:06 GMT
Sender: root@generic.UUCP
Organization: People-Net [pnet91], Etobicoke, ON
Lines: 27

>with this).  Whenever she declares an integer variable, she ALWAYS declares
>it as a FOUR BYTE variable... even when she KNOWS that it's value will always
>contain a number between 0 and 199 (a variable for the Y location on a
320x200
>res. screen).  She does that because she doesn't know that a 2 byte variable
>----------------------------------------
>  BITNET--  mquinn@utcvm    <------------send files here
>  pro-line-- mquinn@pro-gsplus.cts.com

You are incorrect. You do not KNOW that the variable will always be less than
256, two bytes might be possible 64k scan lines is unlikely in the near
future. However, what if the output device is not a screen? What if this were
outputing to a laser printer? Or what if the output were being sent to chained
monitors with some hardware connection such that scan lines greater than 65535
were possible?

Her programming structure makes fewer assumptions about the environment than
yours does and is planned for the future. You have programmed for today and
screw the maintenance programmer that has to fix it in coming years. Memory is
cheap. Speed is cheap. The only exceptions are the Apple II in both cases and
the GS in the second case. It is worth the extra to make allowance for ports
to a Mega-Pixel display which might just be NeXT year's standard.

Eric McGillicuddy

UUCP: bkj386!pnet91!ericmcg
INET: ericmcg@pnet91.cts.com