* jddurand via RT wrote:
Show quoted text>I can happen that a grammar has options understandable only by the
>engine supporting - in practive: Marpa.
>What about a Grammar::Formal::Options that would be a hashRef of Ref ?
Could you elaborate on what you are looking for here? Generally, if
there are patterns (operators or operands) specific to a particular
tool, the expectations is that you would create a package using one
of, say, ::Pattern, ::Unary, ::Binary as base and simply hook that
into the tree. Alternatively, but less elegant, a ::Pattern could be
created and the `user_data` attribute could be set as appropriate. I
could make another more explicit generic extension point, say a
`::Custom` package with a simple `data` member, but it would be nice
to understand any problems with the alternatives first. I could also
be totally off in my interpretation of your suggestion.
--
Björn Höhrmann · mailto:bjoern@hoehrmann.de ·
http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 ·
http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 ·
http://www.websitedev.de/
RT for rt.cpan.org