🚀 go-pugleaf

In article <dick.3311@woodwrk.UUCP> dick@woodwrk.UUCP (Richard H. Wood) writes:
>>In article <13119@cbmvax.commodore.com> jesup@cbmvax.commodore.com (Randell Jesup) writes:
>>	It's easy under 2.0:  GetProgramDir() returns a lock on the directory,
>>or references things via PROGDIR:.  Under 1.3, it's harder.  You have to try
>>to second-guess the shell (search the path, etc), and that doesn't help if
>                                                       ^^^^^^^^^^^^^^^^^^^^
>>the command-line specified a directory.
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
>Not much of a consolation, but:  Don't all C's return the entire string
>(i.e., the command part of the command-line) in arg[0]?  I haven't
>tried this with Aztec 5.0, but on VAX C it appears to (on a VMS
>machine).  If you checked this first and found a path, you wouldn't
>even have to do your second(third ?)-guess routine. ;-)

	Only if the shell lets the command see that path.  The standard
Commdore Shell (and CLI) don't, and most other shells don't (though perhaps
one or two do).  If the startup code can't see the shell command-line, it
can't use it.  I'm fairly sure this isn't tightly specified in ANSI, I suspect
it's merely listed as "command name", with no reference to paths, aliases, etc,
which are all system-dependant.

-- 
Randell Jesup, Keeper of AmigaDos, Commodore Engineering.
{uunet|rutgers}!cbmvax!jesup, jesup@cbmvax.cbm.commodore.com  BIX: rjesup  
Common phrase heard at Amiga Devcon '89: "It's in there!"