Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cwjcc!gatech!mcnc!rti!sas!toebes
From: toebes@sas.UUCP (John Toebes)
Newsgroups: comp.sys.amiga.tech
Subject: Re: What is my name?
Message-ID: <1114@sas.UUCP>
Date: 21 Jul 89 12:43:07 GMT
References: <26385@agate.BERKELEY.EDU> <20565@cup.portal.com> <1227@atanasoff.cs.iastate.edu> <26459@agate.BERKELEY.EDU>
Reply-To: toebes@sas.UUCP (John Toebes)
Organization: SAS Institute Inc, Cary NC
Lines: 19

One thing that seems to be forgotten in this discussion is that it is
entirely possible that a commands has no 'inherant' path.  Take for example
a resident command (written in C and made residentable) that is on the resident
list.  When it is run, there is no path that it came from...  The only way
to work in the presence of the various shells (which may have hidden paths
such as WShell) is to utilize the (admiditly ugly) method of creating an overlay
program which WILL retain an open handle on the original file.  This has
the one problem of not being able to locate the directory as all you have
is a file handle.  Converting from a file handle to a lock is not a legal
operation (currently)... However you do have the ability to store information
as part of the file itself.

Have you considered environment variables??? :-) :-) :-)

--
 |0|\   John A. Toebes, VIII                    usenet:..mcnc!rti!sas!toebes
 |.|/  Coordinator of The Software Distillery   BBS: (919)-471-6436
 ===    Bix: JTOEBES      Plink: JTOEBES     CI$:"sorry Charlie"