Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!van-bc!ubc-cs!alberta!aunro!idacom!andrew
From: andrew@idacom.uucp (Andrew Scott)
Newsgroups: comp.sys.handhelds
Subject: Re: Using CLEAR in progs (Was: Re: new puzzle, new blinky)
Keywords: 48sx, CLEAR, programs
Message-ID: <1991Jan28.215207.23128@idacom.uucp>
Date: 28 Jan 91 21:52:07 GMT
References: <1991Jan10.172803.2262@DRD.Com> <56027@eerie.acsu.Buffalo.EDU> <27a06d1f:1696.3comp.sys.handhelds;1@hpcvbbs.UUCP>
Organization: IDACOM, a division of Hewlett-Packard
Lines: 14

In article <27a06d1f:1696.3comp.sys.handhelds;1@hpcvbbs.UUCP> akcs.falco@hpcvbbs.UUCP (Andrey Dolgachev) writes:
> Considereing that it take virtually no effort to save the stack, it seems
> senseless not to.

I have been programming in Forth for several years, and have never seen
this programming style before.  Since I got my 48 and began reading
comp.sys.handhelds, I have noticed this technique (in addition to the
frowned upon usage of CLEAR).  Are there any compelling reasons for saving
and restoring the stack around a program?
-- 
Andrew Scott	| mail:		andrew@idacom.uucp
		| - or -	..!uunet!ubc-cs!alberta!idacom!andrew

"If you think baseball is exciting, pfft!  Forget it!" - Phil Esposito