in reply to Re: XML::LibXSTL/Windows autoload problem
in thread XML::LibXSLT/Windows autoload problem

Hi jbrugger,
Yes indeed, what the difference a Cap makes...!
And not immediately obvious (to me) how that might end up in an aborted attempt to autoload New.

Thanks for solving the problem!
Best regards,
Allan

PS: well, on 2.thought, I think i do understand that perl (the interpreter) doesn't recognize New as a method of LibXSLT, and thus as a last resort tries to autoload it, which of course fails... Thus a failed autoload might in general be a good indication that you misspelled a method name...
  • Comment on Re^2: XML::LibXSTL/Windows autoload problem

Replies are listed 'Best First'.
Re^3: XML::LibXSTL/Windows autoload problem
by PodMaster (Abbot) on Oct 04, 2005 at 08:07 UTC
    ... Thus a failed autoload might in general be a good indication that you misspelled a method name...
    You don't say ;) 'perldoc perldiag' :
    Can't locate auto/%s.al in @INC

    (F) A function (or method) was called in a package which allows autoload, but there is no function to autoload. Most probable causes are a misprint in a function/method name or a failure to AutoSplit the file, say, by doing make install.

    MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"
    I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).
    ** The third rule of perl club is a statement of fact: pod is sexy.

[reply]
      Arrrrgghhhh... -- Okee, i get the hint :)

      I've written out the perldiag page and nailed it above my computer screen. Promise to check it next time!

      Best regards
      allan
[reply]
[reply]

In Section Seekers of Perl Wisdom