#668556 RFP: dparser -- a scannerless GLR parser generator

Package:
wnpp
Source:
wnpp
Submitter:
Markus Wanner
Date:
2014-07-28 13:27:16 UTC
Severity:
wishlist
#668556#5
Date:
2012-04-12 20:00:52 UTC
From:
To:
* Package name    : dparser
  Version         : 1.26
  Upstream Author : John Bradley Plevyak <jplevyak@acm.org>
* URL             : http://dparser.sourceforge.net/
* License         : BSD
  Programming Lang: C and Python
  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
 written in a natural style of EBNF and regular expressions and
 support both speculative and final actions.

There's an archived RPF for dparser: #248589
#668556#10
Date:
2012-04-14 03:37:00 UTC
From:
To:
Le Thu, Apr 12, 2012 at 10:00:52PM +0200, Markus Wanner a écrit :

Dear Markus,

I would like to suggest to explicit the "GLR", "RPF", and perhaps "EBNF"
acronyms in the long description.

Have a nice week-end,
#668556#15
Date:
2012-04-14 06:38:38 UTC
From:
To:
Hello,

In my opinion, this isn't needed. Those (except for RFP which is
request for packaging) are well-known abbreviations are need not be
explained to potential users of the package.
#668556#20
Date:
2012-04-14 08:45:33 UTC
From:
To:
Dear Charles,

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 common when
talking about parsers.

RPF is actually a typo, I meant to point to the archived Request For
Packaging (RFP) bug in Debian, see here:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=248589

That last sentence isn't meant to be part of the long description of the
package. I wasn't sure how to make that clear.

Regards

Markus
#668556#23
Date:
2012-04-14 09:22:06 UTC
From:
To:
* Markus Wanner <markus@bluegap.ch>, 2012-04-14, 10:45:

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.
#668556#28
Date:
2012-04-14 11:12:48 UTC
From:
To:
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.
#668556#33
Date:
2012-04-14 11:14:24 UTC
From:
To:
Hi,

Based on two votes for extending the acronyms, I propose to change the
long description as follows:

 DParser is a scannerless, generalized left-to-right, rightmost
 deviation (GLR) parser generator based on the Tomita algorithm. It is
 self-hosted and very easy to use. Grammars are written in a natural
 style of extended Backus-Naur form (EBNF) and regular expressions and
 support both speculative and final actions.

I'm not a native speaker, so please feel free to comment on spelling,
grammar, comma or other errors.

Regards

Markus
#668556#38
Date:
2012-04-14 12:16:13 UTC
From:
To:
Yeah, that's why I think the acronyms must be included in the long
description as well. But it cannot hurt to provide the expansion. At
best, it might even increase the number of people who actually know what
the acronyms stand for (Although I - for example - am not sure I'm able
to remember the GLR one...).  ;-)

Regards

Markus Wanner
#668556#43
Date:
2012-04-14 12:12:06 UTC
From:
To:
]] Adam Borowski

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.
#668556#48
Date:
2012-04-15 02:15:33 UTC
From:
To:
Adam Borowski <kilobyte@angband.pl> writes:

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.

So I'd provide an expansion (maybe in parentheses) for the latter only.

Moreover, one wants to err on the side of being too verbose, at least
in the long description; of course one should provide both the acronym
and the expansion in case the person only recognizes the former
[e.g. "XYZ (Xxx Yyyy Zzzz)"].
#668556#53
Date:
2012-04-16 06:05:31 UTC
From:
To:
Dear Debian developers,

Thank you all for your feedback on the long description. I've completed
packaging now and sent out an RFS here:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668966

Please go after sponsoring as eagerly as you discussed the long
description. ;-)

Regards

Markus Wanner
#668556#64
Date:
2014-07-28 13:10:30 UTC
From:
To:
retitle 668556 RFP: dparser -- a scannerless GLR parser generator
noowner 668556
tag 668556 - pending
thanks

Hi,

A long time ago, you expressed interest in packaging dparser. Unfortunately,
it seems that it did not happen. In Debian, we try not to keep ITP bugs open
for a too long time, as it might cause other prospective maintainers to
refrain from packaging the software.

This is an automatic email to change the status of dparser back from ITP
(Intent to Package) to RFP (Request for Package), because this bug hasn't seen
any activity during the last 15 months.

If you are still interested in packaging dparser, please send a mail to
<control@bugs.debian.org> with:

 retitle 668556 ITP: dparser -- a scannerless GLR parser generator
 owner 668556 !
 thanks

It is also a good idea to document your progress on this ITP from time to
time, by mailing <668556@bugs.debian.org>.  If you need guidance on how to
package this software, please reply to this email, and/or contact the
debian-mentors@lists.debian.org mailing list.

Thank you for your interest in Debian,