http://www.perlmonks.org?node_id=663079


in reply to Re: B::Deparse has a problem with Perl6::Export:Attrs?
in thread B::Deparse has a problem with Perl6::Export:Attrs?

Thought so. Unfortunately the same seems to apply to Class::Std, which we also use more often since PBP rules here...

Bye
 PetaMem
    All Perl:   MT, NLP, NLU

Replies are listed 'Best First'.
Re: ...and with CLass::Std
by stvn (Monsignor) on Jan 18, 2008 at 17:02 UTC
    Unfortunately the same seems to apply to Class::Std, which we also use more often since PBP rules here

    You might want to try to get away from Class::Std, as I pointed out here, Class::Std has 56 outstanding Bugs some over 2 years old and many which are quite serious. And it also seems to be no longer maintained (last upload was Feb. 2006). Again, with all due respect to TheDamian, Class::Std is starting to look like abandonware to me.

    Of course I am going to recommend Moose as a replacement, but I am a little biased on that. Of course Moose classes won't survive a deparse either, but we have MooseX::Storage for that. Also work is currently being done on an optimizing compiler for Moose part of which is a mechanism for storing metaclass objects on disk, and since a metaclass is nothing but an object which models a class, that is pretty close to a "deparsed class".

    -stvn