On Tue, Mar 25, 2003 at 09:56:19AM -0500, [EMAIL PROTECTED] wrote:
> !$ perl -wle "require Pod::Man; print $@"
> !
> !$ perl -wle "eval 'require Pod::Man'; print $@"
> !Pod/Man.pm did not return a true value at (eval 1) line 3.
> !
> !$ perl -v
> !
> !This is perl, v5.8.0 built for VMS_AXP
> !
> !
> !Pod::Man doesn't have an explicit true value at the end. I've seen this
> !with other modules. Why is the behavior different when its eval'd?
> !
> !I only see this behavior on VMS.
>
> Using perl 5.8.1 I see these behaviors (note the ''
> quotation marks in the first invocation):
>
> $ perl -wle "require 'Pod::Man'; print $@"
> Can't locate Pod::Man in @INC (@INC contains: perl_root:[lib.VMS_AXP.5_8_1]
> perl_root:[lib] perl_root:[lib.site_perl.VMS_AXP] perl_root:[lib.site_perl]
> /perl_root/lib/site_perl .) at -e line 1.
> %SYSTEM-F-NOSUCHNODE, remote node is unknown
> $ perl -wle "require Pod::Man; print $@"
> $
The above behavior is correct. require Pod::Man is different from
require 'Pod::Man'. The first looks for [Pod]Man.pm the latter looks for a
file called Pod::Man. bareword vs string.
require Pod::Man and eval 'require Pod::Man' should be equivalent. The
only difference being one is in an eval.
--
Follow me to certain death!
http://www.unamerican.com/
