comment on

Maybe you can help me pinpoint the origin of this bug.

Have you tried rewriting your program to use plain old Perl objects (no Moose::Declare)? Do you still get a segfault?

If not, then I'd start looking at Moose::Declare, beginning with the smallest possible grammar ( can you have a null grammar qr{} - what happens when you do?) and building up until you see the weird behavior. Try each grammar out with your pure Perl object and with a Moose object, noting when both fail, one fails or the other fails.

If you can reproduce the problem without MooseX::Declare then either something about the way you are using Regexp::Grammars is at issue, or as you say, there is a bug.

In reply to Re: Segfault with MooseX::Declare and Regexp::Grammars by ELISHEVA
in thread Segfault with MooseX::Declare and Regexp::Grammars by betterworld

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


P is for Practical
	PerlMonks