Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!sdd.hp.com!hp-pcd!hpcvra.cv.hp.com!rnews!hpcvbbs!akcs.falco
From: akcs.falco@hpcvbbs.UUCP (Andrey Dolgachev)
Newsgroups: comp.sys.handhelds
Subject: Re: Using CLEAR in a program
Message-ID: <27aa4087:1840.1comp.sys.handhelds;1@hpcvbbs.UUCP>
Date: 2 Feb 91 04:40:07 GMT
References: <3302@gmuvax2.gmu.edu>
Lines: 15

O.K., what if you have a program which has many arguments floating around
on the stack, and then you have a quit key which stops the program from
any point.  Now, before you stop the program, you want to clear the stack
of all the arguments which are needed anymore.  Now, of course, it would
be possible and feasible to drop the specific # of objects, dependig on
where you stoppped, but it would require additional programming, which
depending on the complexity of the program, could be too length. 
Instead, if you save the stack before the program begins, only a clear
would be required, which would be far simpler, easier, faster, etc.
Another problem is that if you have a buggy program which accidently
takes more for internal arguments than it should, it could end up
accidently using up one of the arguaments which were on the stack before
the program was executed, instead of just erroring out.
Well, just a few ideas, however, I do agree that using CLEAR is extremely
ssloppy if it is used with out a valid reason.
        --Falco