in reply to Re^5: 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

There is no difference in regards to "safety" if the op sets the preffered parser via $ENV{XML_SIMPLE_PREFERRED_PARSER} or via $XML::Simple::PREFERRED_PARSER , they're both equally safe

One is less reliable than the other. $ENV{XML_SIMPLE_PREFERRED_PARSER} is overridden by $XML::Simple::PREFERRED_PARSER.

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

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

Replies are listed 'Best First'.
Re^7: 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 18, 2015 at 08:03 UTC

    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.

      I'm pretty sure his program uses modules.

        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.