Its quicker to fail on buggy json than RFC: A walkthrough from JSON ABNF to Regexp::Grammars
sub fa {
my $time = time;
my $ref = from_json(@_);
$time = time-$time;
print "T$time ", Dumper( $ref ),"\n";
}
fa(q{["double extra comma",,]}); ## THE BUGGY
fa(q{[1,[2,[3],[]]]}); ## THE REGULAR
fa( q{[{"k":"v"},{"v":"k"}] } );
fa( q{{"ro":["sham","bo"],"t":{"i":{"c":{"t":{"o":"c"}}}}}} );
__END__
T5 $VAR1 = 'no match';
T0 $VAR1 = [
1,
[
2,
[
3
],
[]
]
];
T0 $VAR1 = [
{
'k' => 'v'
},
{
'v' => 'k'
}
];
T0 $VAR1 = {
'ro' => [
'sham',
'bo'
],
't' => {
'i' => {
'c' => {
't' => {
'o' => 'c'
}
}
}
}
};
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.