Skip Menu |

This queue is for tickets about the JSON-XS CPAN distribution.

Report information
The Basics
Id: 53975
Status: rejected
Priority: 0/
Queue: JSON-XS

People
Owner: Nobody in particular
Requestors: gregoa [...] debian.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: decode does not behave as documented
Date: Mon, 25 Jan 2010 16:43:51 +0100
To: bug-JSON-XS [...] rt.cpan.org
From: gregor herrmann <gregoa [...] debian.org>
We've resolved the following bug report in the Debian BTS (http://bugs.debian.org/566822) Please consider looking into this issue. Thanks in advance, gregor, Debian Perl Group ----- Forwarded message from Florian Weimer <fweimer@bfk.de> ----- From: Florian Weimer <fweimer@bfk.de> To: submit@bugs.debian.org Subject: Bug#566822: decode does not behave as documented Date: Mon, 25 Jan 2010 09:15:00 +0000 Reply-To: Florian Weimer <fweimer@bfk.de>, 566822@bugs.debian.org Package: libjson-xs-perl Version: 2.270-1 Severity: important The documentation says this: $perl_scalar = $json->decode ($json_text) The opposite of "encode": expects a JSON text and tries to parse it, returning the resulting simple scalar or reference. Croaks on error. JSON numbers and strings become simple Perl scalars. JSON arrays become Perl arrayrefs and JSON objects become Perl hashrefs. "true" becomes 1, "false" becomes 0 and "null" becomes "undef". But this example use JSON::XS (); use Data::Dumper; print Dumper(JSON::XS->new->decode('{"test":true}')); results in the following output: $VAR1 = { 'test' => bless( do{\(my $o = 1)}, 'JSON::XS::Boolean' ) }; Expected output, based on the documentation, is: $VAR1 = { 'test' => 1 }; -- Florian Weimer <fweimer@bfk.de> BFK edv-consulting GmbH http://www.bfk.de/ Kriegsstraße 100 tel: +49-721-96201-1 D-76133 Karlsruhe fax: +49-721-96201-99 Show quoted text
----- End forwarded message ----- -- .''`. http://info.comodo.priv.at/ -- GPG Key IDs: 0x00F3CFE4, 0x8649AA06 : :' : Debian GNU/Linux user, admin, & developer - http://www.debian.org/ `. `' Member of VIBE!AT & SPI, fellow of Free Software Foundation Europe `- NP: Treibhaus: Colosseum
Download signature.asc
application/pgp-signature 836b

Message body not shown because it is not plain text.

Subject: Re: [rt.cpan.org #53975] decode does not behave as documented
Date: Mon, 25 Jan 2010 19:41:16 +0100
To: gregor herrmann via RT <bug-JSON-XS [...] rt.cpan.org>
From: Marc Lehmann <schmorp [...] schmorp.de>
Hi! You sent a possible bug report on or via rt.cpan.org. Please read this mail carefully if you want to be heard. Most likely, your report will be ignored. Please close the ticket again and sent it to the official contact address for the module in question (or send it to rt.cpan.org@schmorp.de). Why is this necessary? rt.cpan.org has many deficiencies which makes it tedious and hard to use, increasing the workload on the people who provide all the perl modules you probably appreciate (and that is really to be avoided - module authors should be able to invest all their time into improving their modules and not fighting with rt.cpan.org's bugs). Still, for some people, rt.cpan.org is useful to have, and some people even like it and really want to use it. That is fine, too. Unfortunately, the designers of rt.cpan.org didn't make their "service" optional - you can neither opt-in nor opt-out of rt.cpan.org as a module author. Just like a spammer, rt.cpan.org forces its "service" (whether wanted or unwanted) on everybody. Just like a spammer, they don't care for the people they actively hurt. Just like a spammer, they don't don't care to fix these issues and make their "service" ethically acceptable. You cannot even configure it to redirect tickets to somewhere else. Unfortunately, ignoring rt.cpan.org is not an option either: for people reporting possible bugs there is no indication that their report will be ignored, and for module authors it means they miss possibly vital bug reports (and of course it's a great impression if rt.cpan.org has lots of bug reports that are unanswered, making a module unmaintained when in fact the opposite might be true). This is why it is important that you delete/resolve your ticket. I am sorry that this wasted a bit of your time, but please understand that I am just as much a victim as you are - the problem is the unethical stance of the rt.cpan.org providers who force their "service" on everybody. Please redirect your bug report as stated in the beginning of this mail, and please consider petitioning the rt.cpan.org providers to stop their unethical behaviour and allow opt-in, opt-out, or some redirect option. Thanks a lot, Marc Lehmann <rt.cpan.org@schmorp.de>
submitter fails to understand overloading, see "man overload".