For some reason (i.e. my validator code generator currently assuming bool data as "!ref($data)"), I'd prefer that JSON::{PP,XS} do not decode JSON true/false as JSON::{PP,XS}::Boolean objects, but as 1/0 instead. I don't care about being able to round-trip boolean data back to JSON at this point.

For JSON::PP, this is rather easy to do, just set $JSON::PP::true=1 and $JSON::PP::false=0 after loading the module. But this simple trick does not work for JSON::XS.

Currently I use Data::Clean::FromJSON to convert JSON::XS::Boolean objects to 1/0, but this adds overhead. It'd be nice if JSON::XS does not produce the JSON::XS::Boolean objects in the first place.

In reply to Making JSON::{PP,XS} not decode true/false to JSON::{PP,XS}::Boolean objects by sedusedan

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.