Newsgroups: comp.sys.handhelds
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!ira.uka.de!fauern!faui43.informatik.uni-erlangen.de!faui14!kskalb
From: kskalb@faui14.informatik.uni-erlangen.de (Klaus Kalb)
Subject: Re: hp48sx: variable rename?
Message-ID: <kskalb.670887146@faui14>
Organization: CSD., University of Erlangen, Germany 
References: <1991Apr2.140223.7718@zip.eecs.umich.edu> <298uZ1w163w@ireta.cynic.wimsey.bc.ca> <9612@mentor.cc.purdue.edu>
Date:  5 Apr 91 21:32:26 GMT
Lines: 24

ahernsd@mentor.cc.purdue.edu (Dynastar) writes:

>In <298uZ1w163w@ireta.cynic.wimsey.bc.ca> rob@ireta.cynic.wimsey.bc.ca (Rob Prior) writes:
>>kamidon@zip.eecs.umich.edu (Keith Amidon) writes:
>>> >	\<< \-> old new \<< old RCL new STO old PURGE \>> \>>
>>I think it will fall apart right here.  When you call 'old', it will
>>evaluate the contents of 'old' on the stack, putting you into the
>>directory.  My 48sx isn't handy, so I can't try this, but I think that's
>>what will happen.

>Hmmm, this is interesting.  What you say should happen, so I tried a
>couple examples out.

[ example deleted ]

RTFM Vol.2 ch25 p476 
...
When a local name is evaluated, the object stored in the corresponding
variable is returned to the stack but is *not* evaluated. 
...

So what ?

-KK