Bug #47602 for JSON: accept scalar ref for json text

Sun Jul 05 20:26:54 2009 blue [...] thisisnotmyrealemail.com - Ticket created

Subject:

accept scalar ref for json text

for a large json string, it would be more efficient to pass a reference to the string to avoid unnecessary copying. please allow either a scalar or scalar ref for json strings.

Tue Mar 30 04:37:57 2010 makamaka [...] cpan.org - Correspondence added

On 2009-7月-05 日 20:26:54, blue wrote: Show quoted text

> for a large json string, it would be more efficient to pass a reference > to the string to avoid unnecessary copying. please allow either a scalar > or scalar ref for json strings.

Sorry, I missed your report. what you want to do is this? decode_json( \$large_json_text ); Currently I don't have a plan about the feature. But I think that a resource saving will be realized by incr_parse. Regards,

Tue Mar 30 04:37:58 2010 The RT System itself - Status changed from 'new' to 'open'

Sun Oct 31 09:24:50 2010 makamaka [...] cpan.org - Correspondence added

Closed.

Sun Oct 31 09:24:52 2010 makamaka [...] cpan.org - Status changed from 'open' to 'resolved'

Wed Mar 30 22:43:40 2011 justincase [...] yopmail.com - Correspondence added

From:

justincase [...] yopmail.com

On Tue Mar 30 04:37:57 2010, MAKAMAKA wrote: Show quoted text

> On 2009-7月-05 日 20:26:54, blue wrote:

> > for a large json string, it would be more efficient to pass a reference > > to the string to avoid unnecessary copying. please allow either a scalar > > or scalar ref for json strings.

> > Sorry, I missed your report. > what you want to do is this? > > decode_json( \$large_json_text ); > > Currently I don't have a plan about the feature. > But I think that a resource saving will be realized by incr_parse. > > Regards,

I was about to create a separate ticket for the same feature before I found this ticket. It's more convenient to allow either a scalar or scalar ref and it's a widely used pattern. See the results of this google search: http://google.com/search?q=site%3Asearch.cpan.org+allow+either+scalar+or+scalar+ref Also, the incremental parser should also accept a scalar ref since it's possible to feed a very large string to it.

Wed Mar 30 22:43:41 2011 The RT System itself - Status changed from 'resolved' to 'open'

Sun Sep 11 01:23:28 2016 ishigaki [...] cpan.org - Correspondence added

On Thu Mar 31 11:43:40 2011, justincase wrote: Show quoted text

> On Tue Mar 30 04:37:57 2010, MAKAMAKA wrote:

> > On 2009-7月-05 日 20:26:54, blue wrote:

> > > for a large json string, it would be more efficient to pass a > > > reference > > > to the string to avoid unnecessary copying. please allow either a > > > scalar > > > or scalar ref for json strings.

> > > > Sorry, I missed your report. > > what you want to do is this? > > > > decode_json( \$large_json_text ); > > > > Currently I don't have a plan about the feature. > > But I think that a resource saving will be realized by incr_parse. > > > > Regards,

> > I was about to create a separate ticket for the same feature before I > found this ticket. It's more convenient to allow either a scalar or > scalar ref and it's a widely used pattern. See the results of this > google search: > http://google.com/search?q=site%3Asearch.cpan.org+allow+either+scalar+or+scalar+ref > > Also, the incremental parser should also accept a scalar ref since > it's > possible to feed a very large string to it.

I understand the convenience you mentioned, but because \1 and \0 have special meanings in JSON and its backends, we can't accept this. Thanks.

Sun Sep 11 01:23:34 2016 ishigaki [...] cpan.org - Status changed from 'open' to 'rejected'