Patrick LeBoutillier wrote:
Nope, that could/should be considered a bug. It has just been fixed (r125400) and will be availableHi all,
I'm loading a .pm file using PerlPostConfigRequire (1.99_19) and I can't get it to load without specifying an absolute path. Even if my module is installed someplace under @INC,
PerlPostConfigRequire Apache/Whatever.pm
or even
PerlPostConfigRequire Carp.pm
doesn't work. But
PerlRequire Carp.pm
works fine.
Is this normal behaviour?
in the next release. Thanks for the bug report.
I couldn't find much documentation specific to PerlPostConfigRequire.It's a fairly new feature. If you find the documentation lacking, please do submit a documentation
patch ;-) (Or did you have a specific question about PerlPostConfigRequire ?)
--------------------------------------------------------------------------------
Philippe M. Chiasson m/gozer\@(apache|cpan|ectoplasm)\.org/ GPG KeyID : 88C3A5A5 http://gozer.ectoplasm.org/ F9BF E0C2 480E 7680 1AE5 3631 CB32 A107 88C3A5A5
signature.asc
Description: OpenPGP digital signature