Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!ub!acsu.buffalo.edu
From: cloos@acsu.buffalo.edu (James H. Cloos)
Newsgroups: comp.sys.handhelds
Subject: Using CLEAR in progs (Was: Re: new puzzle, new blinky)
Keywords: 48sx, CLEAR, programs
Message-ID: <56027@eerie.acsu.Buffalo.EDU>
Date: 25 Jan 91 02:15:45 GMT
References: <1991Jan10.172803.2262@DRD.Com> <25590090@hpcvra.cv.hp.com.>
Sender: news@acsu.Buffalo.EDU
Organization: State University of New York @ Buffalo
Lines: 25
Nntp-Posting-Host: lictor.acsu.buffalo.edu

In article <25590090@hpcvra.cv.hp.com.> billw@hpcvra.cv.hp.com. (William C Wickes) 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

Just want to agree with this opinion.  As someone once put it, when
discussing another stack-based system:  DON'T POP WHAT YOU DIDN'T PUSH!
(author forgotten [SIGH].)

I would point out that I just saw another program here that uses
CLEAR, even to the point of excessiveness.  Different discussion
thread, though.

-JimC
--
James H. Cloos, Jr.		Phone:  +1 716 673-1250
cloos@ACSU.Buffalo.EDU		Snail:  PersonalZipCode:  14048-0772, USA
cloos@ub.UUCP			Quote:  <>