[32567] in Perl-Users-Digest

home help back first fref pref prev next nref lref last post

Perl-Users Digest, Issue: 3834 Volume: 11

daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Mon Dec 10 06:09:16 2012

Date: Mon, 10 Dec 2012 03:09:04 -0800 (PST)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)

Perl-Users Digest           Mon, 10 Dec 2012     Volume: 11 Number: 3834

Today's topics:
        Data::Dumper (was: How to print function with the code  <rweikusat@mssgmbh.com>
        Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)

----------------------------------------------------------------------

Date: Mon, 10 Dec 2012 10:38:21 +0000
From: Rainer Weikusat <rweikusat@mssgmbh.com>
Subject: Data::Dumper (was: How to print function with the code in the function body?)
Message-Id: <87lid66vky.fsf_-_@sapphire.mobileactivedefense.com>

Rainer Weikusat <rweikusat@mssgmbh.com> writes:

[...]

> Using this option will force using the Perl implementation of the
> dumper, since the fast XSUB implementation doesn't support it.

I'm using Data::Dumper (from perl versions 5.10.0 and 5.10.1) do
serialize a set of 'database' into text files (composed of a reference
to an array holding references to objects containg 'plain' data
members and other objects). Some of the older code also uses the
'Freezer' mechanism to transform the 'live' objects into a state
suitable for serialization (by moving transient data items 'out of the
way'). I stopped using the XS implementation mid June this year
because using it would reproducibly cause memory corruption inside the
perl process which ultimatively lead to a segmentation fault
('crash') when serializing 'large' databases (with some hundreds or a
few thousands of array entries). This was a descision I made after
looking at the code of the 'fast' implementation --- debugging that,
especially considering that this has required experimenting with busy
customer installations, didn't seem feasible (this was the kind of
code one can use provided it works but would be better advised to
replace wholesale than trying to work out what it actually does in
case of any problems).

(In general, any 'optimized' implementation of anything should be
avoided --- no amount of 'test cases' will even come close to the
diversity of actual 'use cases' and third-party provided libraries
with a hideously complicated implementation are always a
liability[*]).


[*] That's the "make it so complicated that it has no obvious bugs"
part :->.


------------------------------

Date: 6 Apr 2001 21:33:47 GMT (Last modified)
From: Perl-Users-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin) 
Subject: Digest Administrivia (Last modified: 6 Apr 01)
Message-Id: <null>


Administrivia:

To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.

Back issues are available via anonymous ftp from
ftp://cil-www.oce.orst.edu/pub/perl/old-digests. 

#For other requests pertaining to the digest, send mail to
#perl-users-request@ruby.oce.orst.edu. Do not waste your time or mine
#sending perl questions to the -request address, I don't have time to
#answer them even if I did know the answer.


------------------------------
End of Perl-Users Digest V11 Issue 3834
***************************************


home help back first fref pref prev next nref lref last post