Sorta related ...
We encountered a bug where we were writing to disk a data structure
using XML2JSON, on a machine that had both JSON::Syck and JSON::XS
It appears in this situation that XML2JSON prefers JSON::Syck.
Our problem was that we were then later on reading in that json file
from disk using JSON::XS.
The output from JSON::Syck is sometimes, but not always, compatible with
JSON::XS.
The fix for us was to force XML2JSON to use JSON::XS
my $xml2json = XML::XML2JSON->new( module => 'JSON::XS' );
I speculate that doing this might implicitly silence the erroneous
warning reported in this bug report, because JSON::Syck will simply not
get loaded if you tell XML2JSON to use JSON::XS
That nobody has previously reported this bug might suggest many are
already preferring JSON::XS explicitly.
While it would actively change the "API" behaviour of this module, I
wonder if it is at all worth considering that XML2JSON prefer JSON::XS
over JSON::Syck by default?
