At 04:43 PM 3/21/00 -0600, Craig A. Berry wrote:
>At 04:59 PM 3/21/00 -0500, Dan Sugalski wrote:
> >At 03:55 PM 3/21/00 -0600, Craig A. Berry wrote:
> >>At 02:23 PM 3/21/00 -0500, Dan Sugalski wrote:
> >> >I bet this'd bite with older versions of perl and the -S switch. There's
> >> >no reason not to have some defensive code in there to catch it, though.
> >>
> >>Other than such code being difficult to write, difficult to test, and
> >>causing a potentially annoying performance hit :-(. Not that such things
> >>have stopped us before :-).
> >
> >It's not that tough actually. Do a quick $trnlnm to see if something
> pops up and, if it does, turn the name into a physical device spec instead.
>
>Ah, but what's the definition of "pops up"? I guess you could translate the
>dev spec and see if there's anything after the colon; there shouldn't be for
>a volume logical. That of course fails to trap the case where the logical
>merely points to the wrong device rather than to the wrong directory on the
>right device as in Peter's example.
Well, if we get a device back (say USER) then we go look for a logical. If
that logical exists then we translate the device name to a physical name
and use that, otherwise we use the device name. That should work, unless
I'm confused, which has happened before. :)
> >I'd like to have some way to fix the problem for SYS$COMMON and suchlike
> linked directories, though I don't know how at the moment. :(
>
>Following Carl's suggestion, perhaps it's as simple as a substitution on
>the file spec:
>
>s/[SYSCOMMON/[VMS$COMMON/
Yeah, but if there are other linked directories we'd still lose. Of course,
the docs *strongly* discourage this, but I'd hate to get bit by it.
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
