Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!apple!usc!sdd.hp.com!zaphod.mps.ohio-state.edu!wuarchive!rex!uflorida!haven!decuac!decatl!shlump.nac.dec.com!jareth.enet.dec.com!edp
From: edp@jareth.enet.dec.com (Eric Postpischil (Always mount a scratch monkey.))
Newsgroups: comp.sys.handhelds
Subject: Re: Bugs in the HP48SX
Message-ID: <15069@shlump.nac.dec.com>
Date: 31 Aug 90 12:09:55 GMT
References: <PEDZ.90Aug30120814@bigben.mpd.tandem.com> <2013@charon.cwi.nl> <14944@shlump.nac.dec.com>
Sender: newsdaemon@shlump.nac.dec.com
Reply-To: edp@jareth.enet.dec.com (Eric Postpischil (Always mount a scratch monkey.))
Organization: Digital Equipment Corporation
Lines: 17

In article <PEDZ.90Aug30120814@bigben.mpd.tandem.com>,
pedz@bigben.mpd.tandem.com (Perry Smith) writes:

[About the fact that RCL follows a directory path in a list and then recalls the
last object.]

>I knew that but my complaint is that it actually changes the current
>directory which is not what I want.  I'd like to think of { DIRLIST
>VAR } as an path to VAR much like it is in Unix.

Huh?  No, it doesn't.  Perhaps you are thinking of evaluating a list?  That
changes the current directory path.  But performing a RCL on a list follows the
directory path and recalls the last object, but leaves the current directory
unchanged.


				-- edp