Skip Menu |

This queue is for tickets about the Grammar-Formal CPAN distribution.

Report information
The Basics
Id: 92310
Status: open
Priority: 0/
Queue: Grammar-Formal

Owner: Nobody in particular
Requestors: feratilbeau [...]

Bug Information
Severity: Wishlist
Broken in: 0.01
Fixed in: (no value)

Subject: Grammar free options
MIME-Version: 1.0
X-Mailer: MIME-tools 5.504 (Entity 5.504)
Content-Disposition: inline
X-RT-Interface: Web
Message-ID: <rt-4.0.18-6907-1390252276-1375.0-0-0 [...]>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
X-RT-Encrypt: 0
X-RT-Sign: 0
Content-Length: 190
Download (untitled) / with headers
text/plain 190b
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 ? Thanks / JD.
From derhoermi [...] Mon Jan 20 20: 37:13 2014
MIME-Version: 1.0
X-Spam-Status: No, score=-2.02 tagged_above=-99.9 required=10 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.121] autolearn=ham
In-Reply-To: <rt-4.0.18-6907-1390252276-1714.92310-4-0 [...]>
X-Mailer: Forte Agent 3.3/32.846
X-Spam-Flag: NO
X-Provags-ID: V03:K0:bLpYLhzxXhUL3gtiTaG9tqOW3UGX4HLGKfvhmEf9lxwp8EEHx3/ YOCXOHjiUl15GIrjMEKoArf9scCELKbQyYKvWKWoDNTqcHIa9xjz7LCVzEStNaHrZsNdkzz I/4y2lDOQtmiyppfS34lMENn4iuuxH/3jh2zDJ6shfmxALGHnoN+XroShaAT5Z1bZ30TA77 6E5UBHmbBB76crQT5B6nA==
X-RT-Interface: API
References: <RT-Ticket-92310 [...]> <rt-4.0.18-6907-1390252276-1714.92310-4-0 [...]>
X-Virus-Scanned: Debian amavisd-new at
Message-ID: <9ijrd9ddorv2b8ag0q2uauvlvf2ah37254 [...]>
content-type: text/plain; charset="utf-8"
X-RT-Original-Encoding: utf-8
X-Spam-Score: -2.02
Received: from localhost (localhost []) by (Postfix) with ESMTP id B91B5240E17 for <cpan-bug+Grammar-Formal [...]>; Mon, 20 Jan 2014 20:37:13 -0500 (EST)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 64wpNUeMniLm for <cpan-bug+Grammar-Formal [...]>; Mon, 20 Jan 2014 20:37:12 -0500 (EST)
Received: from ( []) by (Postfix) with SMTP id 5C5012401AC for <bug-Grammar-Formal [...]>; Mon, 20 Jan 2014 20:37:12 -0500 (EST)
Received: (qmail 7190 invoked by alias); 21 Jan 2014 01:37:11 -0000
Received: from (HELO ( by (qpsmtpd/0.28) with ESMTP; Mon, 20 Jan 2014 17:37:10 -0800
Received: from netb ([]) by (mrgmx101) with ESMTPSA (Nemesis) id 0LmfKJ-1VWMN21GYF-00aEGu for <bug-Grammar-Formal [...]>; Tue, 21 Jan 2014 02:37:05 +0100
Delivered-To: cpan-bug+Grammar-Formal [...]
Subject: Re: [ #92310] Grammar free options
Return-Path: <derhoermi [...]>
X-Original-To: cpan-bug+Grammar-Formal [...]
X-RT-Mail-Extension: grammar-formal
Date: Tue, 21 Jan 2014 02:37:05 +0100
To: bug-Grammar-Formal [...]
Content-Transfer-Encoding: 8bit
From: Bjoern Hoehrmann <derhoermi [...]>
RT-Message-ID: <rt-4.0.18-6309-1390268234-1315.92310-0-0 [...]>
Content-Length: 1107
* 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 · · Am Badedeich 7 · Telefon: +49(0)160/4415681 · 25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 ·

This service is sponsored and maintained by Best Practical Solutions and runs on infrastructure.

Please report any issues with to