I concur that this works, unfortunately, it doesn't affect the parsing functions. If you treat the functions as object methods, things break, because the functions aren't expecting the object as its first parameter.

It seems that there's a discrepancy between the docs and the functionality (appears to be both, but I'm not positive). If nobody else can confirm by EOD today, I'll open a bug report (if it's not done by then), and simply link to this thread as it has all of the relevant information.

I don't use JSON::Parse (I use JSON), but a possible alternative would be to use eval:

my $perl; my $ok = eval { $perl = parse_json('[x]'); 1; }; if (! $ok){ warn "json load failed...\n"; ...; # do something else }

In reply to Re^2: JSON::Parse how to warn_only()? by stevieb
in thread JSON::Parse how to warn_only()? by bliako

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.