🚀 go-pugleaf

In article <1992Dec16.124633.1@kosmos.wcc.govt.nz>, banks_p@kosmos.wcc.govt.nz writes:
>In article <1gke2bINN2up@swan.doc.ic.ac.uk>, mybg@doc.ic.ac.uk (M Y Ben Gershon) writes:
>> dbh@doc.ic.ac.uk (Denis Howe) writes:
>[bits deleted]
>> -Set FS <FileSwitch$CurrentFilingSystem>
>> -SetEval CSD "<FS>:"+FileSwitch$<FS>$CSD
>> 
>> I am sorry to disappoint you, but this does not work either!  It remains
>> constant and is not altered when the csd is changed.
>
>   Of course it doesn't. It is not a code variable. To do what you want
>would reqire writing some short assembler. This approach is designed to
>allow you to find out the CSD at a *particular point in time*. This is
>useful for Obey scripts that need to know the CSD or whatever but is by no
>means intended to be a continually updating CSD variable.
>

Would it not be possible to create a macro variable which did an eval as above?
I don't have access to a machine at the moment, so I can't play with the idea.

Jason
--
( Recommended Reading: Zen and the Art of Motorcycle Maintainance 
                       Robert M. Pirsig                                       )