Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!elroy.jpl.nasa.gov!ncar!gatech!purdue!haven!umbc3!gmuvax2!peraino
From: peraino@gmuvax2.gmu.edu (Bob Peraino)
Newsgroups: comp.sys.handhelds
Subject: Clean code
Keywords: hp48
Message-ID: <3290@gmuvax2.gmu.edu>
Date: 25 Jan 91 19:53:16 GMT
Organization: George Mason Univ., Fairfax, Va.
Lines: 20


 
In article <25590090@hpcvra.cv.hp.com.> billw@hpcvra.cv.hp.com. (William C Wicke
   s) writes:
>I hate to complain about an otherwise nice program, but...
>
>Using CLEAR is a nasty thing to do to an unsuspecting 48.  IMHO, any
>program should be able to clean up after itself without trashing stack
>objects that it didn't put there.  And I shouldn't have to read a
>program's listing to figure out how to defend against its side
>effects.
>
>Bill Wickes
>HP Corvallis
 
     I wholeheartedly agree! The 48 is a VERY modular machine. Code
should ALWAYS leave the machine in the state it was before entering the
code. This goes beyond the stack; don't forget flags and variables.

peraino@gmuvax.gmu.edu