On 9/26/07, Michael G Schwern [EMAIL PROTECTED] wrote:
demerphq wrote:
On 12/5/06, Ken Williams [EMAIL PROTECTED] wrote:
On Dec 4, 2006, at 12:35 PM, Julian Mehnle wrote:
Is it likely that this occurs with CPANTS in the first place?
Unfortuna-
tely, CPANTS doesn't tell the
demerphq wrote:
If that's the case, perhaps the docs for Terse could use stronger language.
Right now it's a little obtuse.
· $Data::Dumper::Terse or $OBJ−Terse([NEWVAL])
When set, Data::Dumper will emit single, non‐self‐referential
values as atoms/terms rather than statements. This
On 9/26/07, Michael G Schwern [EMAIL PROTECTED] wrote:
demerphq wrote:
If that's the case, perhaps the docs for Terse could use stronger language.
Right now it's a little obtuse.
· $Data::Dumper::Terse or $OBJ−Terse([NEWVAL])
When set, Data::Dumper will emit single,
demerphq wrote:
Would something like the following patch be good in your opinion?
Yeah, I like the idea of having the best practice encoded as a function.
--
There will be snacks.
On Sep 25, 2007, at 4:55 PM, demerphq wrote:
Im shocked that anyone is using Terse in production code. It is
completely unsafe and intended ONLY for debugging purposes. In fact id
say that using Data::Dumper without Purity(1) as a serialization
mechanism in production code is simply insane.
