UPDATE

The suggested use of JSON::XS#INCREMENTAL-PARSING looks like the much better solution for such kind of parsing problems. graff++

> If there is a good separator like blank line(s), you can set the input record separator $/ accordingly.

You didn't show us more than one object and your link is broken. So I had to guess they all start with '{"created_at":' at line's start.

And I shortened your objects for better demonstration

use v5.12.0;
use warnings;
use Data::Dump;
use JSON::XS;

my $ident ='{"created_at":';
local $/ = "\n$ident";


my $prefix="";


while (<DATA>) {
    chomp;                              # removes $/ from the end
    my $obj = "$prefix$_";
    ddx $obj;
    say "-" x 30;
    dd decode_json($obj);
    #say "-" x 72;
    $prefix = $ident;
}



__DATA__
{"created_at":"Sat Mar 02 18:45:26 +0000 2013","id":307924626426695681
+,"id_str":"307924626426695681","etc":"***YADDA YADDA ***","id_str":"2
+621098741943851970"}
{"created_at":"Sat Mar 02 18:45:26 +0000 2013","id":307924626426695681
+,"id_str":"307924626426695681","etc":"***YADDA YADDA ***","id_str":"2
+621098741943851970"}
{"created_at":"Sat Mar 02 18:45:26 +0000 2013","id":307924626426695681
+,"id_str":"307924626426695681","etc":"***YADDA YADDA ***","id_str":"2
+621098741943851970"}

[download]

# raw_json.pl:16: "{\"created_at\":\"Sat Mar 02 18:45:26 +0000 2013\",
+\"id\":307924626426695681,\"id_str\":\"307924626426695681\",\"etc\":\
+"***YADDA YADDA ***\",\"id_str\":\"2621098741943851970\"}"
------------------------------
{
  created_at => "Sat Mar 02 18:45:26 +0000 2013",
  etc => "***YADDA YADDA ***",
  id => 307924626426695681,
  id_str => 2621098741943851970,
}
# raw_json.pl:16: "{\"created_at\":\"Sat Mar 02 18:45:26 +0000 2013\",
+\"id\":307924626426695681,\"id_str\":\"307924626426695681\",\"etc\":\
+"***YADDA YADDA ***\",\"id_str\":\"2621098741943851970\"}"
------------------------------
{
  created_at => "Sat Mar 02 18:45:26 +0000 2013",
  etc => "***YADDA YADDA ***",
  id => 307924626426695681,
  id_str => 2621098741943851970,
}
# raw_json.pl:16: "{\"created_at\":\"Sat Mar 02 18:45:26 +0000 2013\",
+\"id\":307924626426695681,\"id_str\":\"307924626426695681\",\"etc\":\
+"***YADDA YADDA ***\",\"id_str\":\"2621098741943851970\"}\n"
------------------------------
{
  created_at => "Sat Mar 02 18:45:26 +0000 2013",
  etc => "***YADDA YADDA ***",
  id => 307924626426695681,
  id_str => 2621098741943851970,
}

[download]

Cheers Rolf
(addicted to the Perl Programming Language :)
Wikisyntax for the Monastery

In reply to Re^4: JSON::XS Wide Character Problem (updated) by LanX
in thread JSON::XS Wide Character Problem by cormanaz

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.