🚀 go-pugleaf

Yes, you might have problems when using a script, but try this out
and see how far you get.  If your program was launched under CLI or
Shell (true programs officially from CA), then:
          myproc->pr_CLI->cli_CommandName
is a BSTR to the path used to invoke your program as typed in on the
command line.  If there are now path seperators here, then the
program was in the current directory (a quick Lock() should answer
that question).  If the lock fails, then walk the path seglist in:
          myproc->pr_CLI->cli_CommandDir
attempting locks on the path directories.  You can try this right
now by running one program using an explicit path.  In another CLI
type,  status full .  Check out those paths!!!

   Danger Will Robinson!!!!!  The prophets have announced that AmigaDOS
will receive some serious changes in the next few years.  As such, the
sturctures named here may wither and die.  The best long-term solution
may be to ask for a DOS function call to return the lock.  For short
term, allow this method to work while SysBase->version < 40...  If
program private resources are ever to become reality (ala Mac), then
this function call must be available.

   Danger Will Robinson!!!!!  If you program came into being from 
some one LoadSeg()ing-CreateProc()'ing, chances are there won't be
a CLI structure.  At that point, you're just an orphan... :-(


--- When you re-zone vacate cemetry land for apartment buildings,
    do you have to notify the next of kind of those buried nearby?
--- brian witt
--- well!aleks@ucbvax.Berkeley.EDU