Re: Ada.Directories

[Kilgallen@SpamCop.net (Larry Kilgallen)]

In article <wccejflhkz7.fsf@shell01.TheWorld.com>, Robert A Duff <bobduff@shell01.TheWorld.com> writes:
> Kilgallen@SpamCop.net (Larry Kilgallen) writes:
> 
>> In article <ffkdem$1oe$1@infosun2.rus.uni-stuttgart.de>, Peter Hermann <ica2ph@lucky.ihr.uni-stuttgart.de> writes:
>>> Adam Beneschan <adam@irvine.com> wrote:
>>>> Maybe the GNAT folks can add a subpackage of Ada.Directories that
>>> 
>>> maybe there exists some code for
>>> standardized portable handling of path strings?
>>
>> I doubt it.  Handle this:
>>
>> 	SYS$SYSTEM:SECURITY.AUDIT$JOURNAL;-1
>>
>> Typically SYS$SYSTEM is a logical name pointing to a rooted directory,
>> but there have been cases where particular customers have made it a
>> triple-rooted directory rather than single.  The only reliable way to
>> figure out what is going on is to call the appropriate VMS system servce.
> 
> What's a triple-rooted directory?

I should have said "double" instead of "single" above, which would be:

$ show logical sys$sysroot
   "SYS$SYSROOT" = "DSA6:[SYS0.]" (LNM$SYSTEM_TABLE)
        = "SYS$COMMON:"
1  "SYS$COMMON" = "DSA6:[SYS0.SYSCOMMON.]" (LNM$SYSTEM_TABLE)

a triple rooted directory example is:

$ show logical DECW$SYSTEM_DEFAULTS
   "DECW$SYSTEM_DEFAULTS" = "SYS$LOGIN_DEVICE:[GREG.TOOLS.DECW]" (LNM$PROCESS_TABLE)
        = "SYS$COMMON:[DECW$DEFAULTS.USER]"
        = "SYS$COMMON:[DECW$DEFAULTS.SYSTEM]"
        = "SYS$LIBRARY:"
1  "SYS$LIBRARY" = "SYS$SYSROOT:[SYSLIB]" (LNM$SYSTEM_TABLE)
   "DECW$SYSTEM_DEFAULTS" = "SYS$SYSROOT:[DECW$DEFAULTS.USER]" (DECW$LOGICAL_NAMES)
        = "SYS$SYSROOT:[DECW$DEFAULTS.SYSTEM]"
        = "SYS$LIBRARY:"
1  "SYS$LIBRARY" = "SYS$SYSROOT:[SYSLIB]" (LNM$SYSTEM_TABLE)
$

> Common Lisp has pretty good support for mostly-portable handling of path
> names.  It includes support for VMS, if I remember correctly.

Certainly that is possible, but it involves OS-specific code not
implied by sentence that prompted my comment.

>>> maybe there exists some code for
>>> standardized portable handling of path strings?