I can think of several reasons why not:

JSON::PP apparently is an OO class, but it is not well-factored and compartmentalised in the sense that it is possible to sub-class it to achieve what I want. It has lots of internal global state expressed as upper-scoped variables, like parsers traditionally do, and even refers to the original package name a lot, even complicated by the fact that it treats the package name specially to work together with the optional ::XS variant. Just renaming the package and inserting the check like you said is not enough to make it work.

Having to keep the modified copy in sync with upstream is annoying.

Copy-pasta code opens another can of worms. So far in the project we only have code written on our own, uniformly licenced. Since we distribute the code, I have to spend time figuring out what is affected by this licence-wise "foreign object", and in the end it might well turn out that we just need three additional lines here and there, but that's not at all what I like to spend my time with as a programmer.

Therefore I would go this direction only as a last resort.

In reply to Re^2: make duplicate JSON keys an error by daxim
in thread make duplicate JSON keys an error by daxim

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.