JSON encodes numbers differently than strings. JSON::PP uses B to peek at the internals of scalars to figure out how the value of the scalar is stored to guess if it's more appropriate to store a scalar as a string or as a number.

You could create a copy of JSON::PP that encodes everything as strings, removing the need for B. (Scalar::Util's reftype would do for the other uses of B, and ref could be used if even that's not available.)

An alternative would be to install JSON::XS on one machine and copy the installed files over. That would require a machine with the same architecture and Perl version as the target. The perl on the source would have to be built with the same options as the perl on the target.

In reply to Re: Non JSON.pm solution for JSON by ikegami
in thread Non JSON.pm solution for JSON by matija

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.