Unfortunately, this one isn't improving your batting average :-)
Or is this not the mysterious behaviour you're referring to, as I did have two mysterious behaviours to deal with here? Looks like I'm going to have to keep with my custom JSON-ish output until I find a better dumper :-) (Which is getting woefully off-topic for this thread, but I'll point out that I like the conciseness of JSON, but need some more flexibility, e.g., dumping stuff other than scalars, arrays, hashes, and nulls, but at the same time, not dumping all the contents of every object like Data::Dump(er) are wont to do.)$ perl5.8.8 /tmp/z.pl About to set $SIG{CHLD} About to set $SIG{CHLD} encountered CODE(0x10ec290), but JSON can only represent references to + arrays or hashes at /tmp/z.pl line 162 encountered CODE(0x10ec290), but JSON can only represent references to + arrays or hashes at /tmp/z.pl line 162
However, I don't think this is related to my original problem where I'm not using JSON::XS, either, but my own pseudo-JSON-ish generator. The read-only error crops up in that generator code (thus why it shows up in my original node), but it's called from the signal handling code, where I'm suspicious the real error comes from.
In reply to Re^2: Modification of read-only value (XS--)
by Tanktalus
in thread Modification of read-only value
by Tanktalus
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |