Peter Prymmer writes:
> Charles Lane wrote:
>> Dan Sugalski wrote:
>> > When you get right down to it, perl's hosed if it's library's
>> > dysfunctional, so if folks *do* mess things up we can just tell 'em "Don't
>> > *do* that!"
>>
>> %PERL-F-DOPESLAP, logical PERL_ROOT not found, don't *DO* that!
>>
>> I do wonder what kind of weird situations one might run up against:
>> perl embedded with libraries not used/libraries on a remote DECNET
>> node that's unreachable most of the time; etc. etc. But at some
>> point you have to say 'enough!'
> There are a lot of people that do this practice. I even know some that
> institutionalize it. Check the perl newsgroups and see all the newbie
> posts about "Foo.pm not found in @INC".
If you look for VMSPIPE and can't find it at all, what do you do?
You can't run system(), you can't do piped i/o. I'd say that a -F-
is an appropriate response to that kind of failure, maybe a *bit*
on the harsh side.
> Note that one of the reasons that rpm was rewritten in C was so that a
> floppy based install did not have to have a perl binary lying around.
> It'd be nice if perl could regain some of it's little portable utility
> character (er, maybe :-).
Perl? Little? Surely you jest!
So let's see: PERL_ROOT might not be there, the Perl executable itself
may be on a floppy or elsewhere. So that leaves the "write a tempfile"
solution.
Maybe as a last-gasp, everything-else-fails, solution.
BTW, the reason I suggested that putting VMSPIPE.COM in [.t] is
possibly a bad idea was not that it wouldn't work, but that there are
tests (that I've run afoul of before) that check for files in [.t] and
bomb if they don't see what they want, or if they find more than they
want.
I don't expect this to be a "real" problem, but it does highlight the
difficulties of operating in a "no PERL_ROOT" environment.
--
Drexel University \V --Chuck Lane
----------------->--------*------------<[EMAIL PROTECTED]
(215) 895-1545 / \ Particle Physics [EMAIL PROTECTED]
FAX: (215) 895-5934 /~~~~~~~~~~~ [EMAIL PROTECTED]
