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

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.

Comment on Re^9: 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^10: 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 20, 2015 at 15:46 UTC
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]
Re^11: After compiling a script using PAR::Packer I get the error Can't locate XML/LibXML/SAX.pm in @INC by Anonymous Monk on May 21, 2015 at 01:38 UTC
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. Ridiculous.	[reply]
Re^12: 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 21, 2015 at 18:03 UTC
No, it's not ridiculous. XML::Parser's mis-handling of namespaces is well documented and easy to demonstrate Update: Expanded pronouns for clarity.	[reply]
Re^13: After compiling a script using PAR::Packer I get the error Can't locate XML/LibXML/SAX.pm in @INC by Anonymous Monk on May 21, 2015 at 20:11 UTC