in reply to Re: RFC: Data::Dumper::Lite
in thread RFC: Data::Dumper::Lite

Data::Dumper has been able to do this for some time. Check out $Data::Dumper::Deparse in the Data::Dumper POD.
A search of CPAN shows two versions, 2.101 (which I have) and 2.12 (bundled with Perl 5.8.0). As far as I can tell, $Data::Dumper::Deparse isn't supported until version 2.12.

Why should I use Data::Dumper::Lite instead of Data::Dumper or Storable?
That is a very good question and my knee jerk response is "Why not?" :-)

I am trying to write a (mostly*) pure perl version of Data::Dumper that has a smaller code base (read: easier to maintain) and easier to use since there are no options what so ever. D::D::L started out as a way for me to learn more but it has grown in functionality while the code base has shrunk.

* Mostly. I have to use B::Deparse to get at the code references. Perhaps I could make use of autouse or autoload to reduce the overhead of using B::Deparse when it is not used.

Replies are listed 'Best First'.
Re: Re: Re: RFC: Data::Dumper::Lite
by Juerd (Abbot) on May 28, 2003 at 06:37 UTC

    I have to use B::Deparse to get at the code references. Perhaps I could make use of autouse or autoload to reduce the overhead of using B::Deparse when it is not used.

    perldoc -f require

    Juerd # { site => 'juerd.nl', plp_site => 'plp.juerd.nl', do_not_use => 'spamtrap' }

      Talk about overlooking the obvious! :-)