Beefy Boxes and Bandwidth Generously Provided by pair Networks Joe
"be consistent"
 
PerlMonks  

Re^3: Segfault with MooseX::Declare and Regexp::Grammars

by ELISHEVA (Prior)
on Feb 27, 2011 at 13:41 UTC ( #890417=note: print w/ replies, xml ) Need Help??


in reply to Re^2: Segfault with MooseX::Declare and Regexp::Grammars
in thread Segfault with MooseX::Declare and Regexp::Grammars

If plain Perl objects and plain Moose objects don't cause this problem, could you clarify further what you are trying to pinpoint. What makes you unsure that this isn't an issue with MooseX::Declare and whatever magic it is conjuring up?

It would seem to me that newer add-on packages like MooseX::Declare have a responsibility to work cleanly with core packages like Data::Dumper, as well as any non-core packages they extend (i.e. Moose). This is all the more so with something like MooseX::Declare which claims to be a safer way of doing the kinds of things people once tried to do with source filters.


Comment on Re^3: Segfault with MooseX::Declare and Regexp::Grammars
Re^4: Segfault with MooseX::Declare and Regexp::Grammars
by betterworld (Deacon) on Feb 27, 2011 at 14:13 UTC

    You are right that it is likely that the bug is in MooseX::Declare or one of its dependencies. I would like to find a way to reproduce this without resorting to other complicated modules like Regexp::Grammars (even though this module is pure Perl).

    Update: Other segmentation faults have already been described that are triggered by RGís extensive use of the regex engine, so itís not that unlikely that the culprit is in the regex engine.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://890417]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others about the Monastery: (12)
As of 2014-04-18 15:15 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    April first is:







    Results (469 votes), past polls