You cannot post messages because only members can post, and you are not currently a member.
Description:
This mailing list is for discussions related to the PyGgy parser generator for Python. This list may be used to discuss how to use PyGgy as well as report bugs and discuss implementation issues.
|
|
|
issue implementing the following in a .pyl file
|
| |
I'm parsing IIS logs and am having a hell of a time getting a regex
that will work for the page portion of the file.
given something like : 2007-02-09 23:59:59 GET /ABC.aspx or
2007-02-09 23:59:59 GET /Search/Styles/XYZ.css
i need to match on the blah.aspx, blah/blah.css, etc.. portion of the... more »
|
|
|
Getting some more info about from ParseError.
|
| |
Hi, I am using Pyggy to parse our simple DSL. Most of the time it is just simple expressions. While the expressions are by the grammar everything works fine. The problem is that when the expression is bad i.e. '(1 + 2' or '1 + / 2' the thrown ParseError exception has very little info about the error except the bad token and its text. It would be very useful if... more »
|
|
|
Parsing incpmplete statements?
|
| |
I would like to use PyGgy to parse command-line input, similar to the way SQL is parsed by a database command-line utility. When entering a SQL statement, if no semi-colon is encountered, then the prompt changes to indicate the statement is incomplete, and more input is collected. I'm not that familiar with the interfaces between PyGgy and PyLly. Is... more »
|
|
|
Contextless between the grammar and the lexer
|
| |
Hi all, I want to use this tool in order to generate from an ABNF grammar a parser for it and i m running to some problems. My election was due that together with DParser are the only GLR parser generators. So far i saw that the rules specified earlier have precedence. My problem is that there is no context with the grammar. To be more... more »
|
|
|
Yet Another ambiguous grammar
|
| |
I've been attempting to put together a parser to recognize a substantial subset of an SQL dialect (specifically the DB2 dialect), but have run into ambiguity problems fairly early on. Here's a (much) reduced grammar demonstrating the issue (the constant and identifier non-terminals are omitted, but I can provide the... more »
|
|
|
more ambiguous parser help
|
| |
I've got another issue that I can't seem to get pyggy to deal with. I distilled my problem down to this example. Is there anyway to make this unambiguous? Here's my lexer and parser: foo.pyl: INITIAL: ",": return "COMMA" "[[:digit:]]+": return "CONSTANT" "[[:blank:]]": return "\n": return... more »
|
|
|
help with an ambiguous grammar
|
| |
Hello again, I'm trying to write a grammar that allows for space separated lists. Here's my grammar: %right NEG; %left MINUS; %nonassoc SHORT; %nonassoc LONG; expression -> %prec(MINUS) expression SUB expression | %prec(NEG) SUB expression | CONSTANT | %prec(LONG) LPAREN expression (expression)* RPAREN... more »
|
|
|
pgy_calc.py can't parse "5 - -5"
|
| |
It looks like the unary minus setup for pgy_calc.pyg doesn't work at the moment. However, the one for ply does properly parse "5 - -5". Is there a simple fix for this (since I want to use this kind of grammar in my code)". Thanks, -e
|
|
|
Stuck with $EOF$ token
|
| |
Hi, I'm a bit new to parsers and Pyggy, and I have a (very rough, ambiguous and incomplete) grammar that dies at the very end of the parsing with this error: [32] $EOF$ <<EOF>> reduce 7 reduce 2 reduce 3 parse error: "<<EOF>>": line 296: That is, when it reaches the end it's not an accepting parser I guess.... more »
|
|
|
Difficulty with if/else precedence
|
| |
I'm parsing a C-style language and I'm facing a dangling-else ambiguity problem: if (rel1) if (rel2) stmt1 else stmt2 My statement nonterminal includes the following productions seemingly relevant here: statement ->assignexpression SEMICOLON | L_BRKT statements? R_BRKT | SEMICOLON | %prec(CLOSEDIF) IF relation statement ELSE statement... more »
|
|
|
|
