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

would be more straightforward and less error-prone than

Nonsense

Whichever method you use, it doesn't need to be done before the module is loaded; just before XMLin is called.

true

Safer:

Nonsense

  • Comment on Re^3: 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^4: 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 17, 2015 at 02:08 UTC
    If you think it doesn't matter which parser is used, you've been lucky or you haven't used XML::Simple much. You don't have to be an asshole about it.
[reply]

      If you think it doesn't matter which parser is used, you've been lucky or you haven't used XML::Simple much. You don't have to be an asshole about it.

      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

      Equally neither is more or less error prone than the oper, especially since the op is using PAR::Packer

      For such a hyper pedant you sure have a flare for saying nonsense and being rude when you're called on it.

[reply]

        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.

[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom