Dear Debian developers,
On 04/15/2012 04:15 AM, Miles Bader wrote:
> In my experience, "EBNF" and "LL"/"SLR"/"LALR" are widely known (they
> are "classic compiler terms"), for the type of person who might be
> interested in parser generators, but "GLR" isn't.
Thank you all for your feedback on th
Adam Borowski writes:
> On Sat, Apr 14, 2012 at 11:22:06AM +0200, Jakub Wilk wrote:
>> >GLR means "Generalized Left-to-right Rightmost deviation parser"
>> >or maybe "Generalized LR parser". EBNF is the Extended BackusâNaur
>> >Form. Acronyms like these - i.e. LL, LL(k), SLR, LALR - are pretty
>
"Bernhard R. Link" writes:
> For the grammer I personally would prefer it expanded, though I
> think it is more understandable as "EBNF (Extended Backus-Naur Form)
> Grammar" than the other way around.
I agree -- in reinforces the fact that these are well-known terms
which are often known by thei
* Markus Wanner [120414 13:32]:
> On 04/14/2012 11:22 AM, Jakub Wilk wrote:
> > Sure, they are also much more common than GLR. And if you are "just"
> > interested in parsing and not a computer scientists, there's a chance
> > you've never heard about any of them.
>
> Based on two votes for extend
Hi,
On 04/14/2012 02:12 PM, Tollef Fog Heen wrote:
> I've written parsers (using bison, though) and can't recall having heard
> the term GLR parser before. Maybe I'm unique in that respect, but I
> doubt it.
Note that bison also supports building GLR parsers. That's a somewhat
recent addition, I
On Sat, 2012-04-14 at 15:09 +0300, Andrew Shadura wrote:
> During my university studies I had a course dedicated to compilers
> theory, but while I knew (and still know) the meaning of all those
> abbreviations I rarely tried to spell them out in full, but rather was
> always using their abbreviate
On 04/14/2012 01:12 PM, Adam Borowski wrote:
> I can't really imagine someone writing a parser using such tools without
> having heard these acronyms first, though. And I'd risk saying they are
> actually more widely known than their expansions.
Yeah, that's why I think the acronyms must be inclu
]] Adam Borowski
> I can't really imagine someone writing a parser using such tools without
> having heard these acronyms first, though. And I'd risk saying they are
> actually more widely known than their expansions.
I've written parsers (using bison, though) and can't recall having heard
the
Hello,
On Sat, 14 Apr 2012 13:12:48 +0200
Adam Borowski wrote:
> I can't really imagine someone writing a parser using such tools
> without having heard these acronyms first, though. And I'd risk
> saying they are actually more widely known than their expansions.
During my university studies I
On Sat, Apr 14, 2012 at 11:22:06AM +0200, Jakub Wilk wrote:
> * Markus Wanner , 2012-04-14, 10:45:
> >>I would like to suggest to explicit the "GLR", "RPF", and
> >>perhaps "EBNF" acronyms in the long description.
> >
> >GLR means "Generalized Left-to-right Rightmost deviation parser"
> >or maybe "
Hi,
On 04/14/2012 11:22 AM, Jakub Wilk wrote:
> Sure, they are also much more common than GLR. And if you are "just"
> interested in parsing and not a computer scientists, there's a chance
> you've never heard about any of them.
Based on two votes for extending the acronyms, I propose to change t
* Markus Wanner , 2012-04-14, 10:45:
I would like to suggest to explicit the "GLR", "RPF", and perhaps
"EBNF" acronyms in the long description.
Thanks for your suggestions.
GLR means "Generalized Left-to-right Rightmost deviation parser" or
maybe "Generalized LR parser". EBNF is the Extended
Dear Charles,
On 04/14/2012 05:37 AM, Charles Plessy wrote:
> I would like to suggest to explicit the "GLR", "RPF", and perhaps "EBNF"
> acronyms in the long description.
Thanks for your suggestions.
GLR means "Generalized Left-to-right Rightmost deviation parser" or
maybe "Generalized LR parser
Hello,
On Sat, 14 Apr 2012 12:37:00 +0900
Charles Plessy wrote:
> > * Package name: dparser
> > Description : a scannerless GLR parser generator
> > DParser is a scannerless GLR parser generator based on the Tomita
> > algorithm. It is self-hosted and very easy to use. Grammars are
Le Thu, Apr 12, 2012 at 10:00:52PM +0200, Markus Wanner a écrit :
>
> * Package name: dparser
> Description : a scannerless GLR parser generator
>
> DParser is a scannerless GLR parser generator based on the Tomita
> algorithm. It is self-hosted and very easy to use. Grammars are
> w
Package: wnpp
Severity: wishlist
Owner: Markus Wanner
* Package name: dparser
Version : 1.26
Upstream Author : John Bradley Plevyak
* URL : http://dparser.sourceforge.net/
* License : BSD
Programming Lang: C and Python
Description : a scannerless GLR p
16 matches
Mail list logo
