in reply to Re^6: After compiling a script using PAR::Packer I get the error Can't locate XML/LibXML/SAX.pm in @INC
in thread After compiling a script using PAR::Packer I get the error Can't locate XML/LibXML/SAX.pm in @INC

It's using local I said was safer. Without it, one module using XML::Simple won't break another using XML::Simple.

Module? The op is packing a program, just add the overrides in the program when packing with PAR, and thats the end of that.

  • Comment on Re^7: After compiling a script using PAR::Packer I get the error Can't locate XML/LibXML/SAX.pm in @INC

Replies are listed 'Best First'.
Re^8: After compiling a script using PAR::Packer I get the error Can't locate XML/LibXML/SAX.pm in @INC
by ikegami (Patriarch) on May 19, 2015 at 16:14 UTC
    I'm pretty sure his program uses modules.
[reply]

      I'm pretty sure his program uses modules.

      Yes, and they can all use the same combination of XML::Simple+XML::Parser , or whichever parser OP chooses to ship.

      There nothing to break by avoiding local, nothing to gain by using local. OP packs+ships one parser.

[reply]
        So you argument for why "If you think it doesn't matter which parser is used, you've been lucky or you haven't used XML::Simple much" is wrong is that "they can all use XML::Parser"? That's just plain wrong. XML::Parser completely mishandles namespaces, for one.
[reply]

In Section Seekers of Perl Wisdom