Home » Modeling » TMF (Xtext) » Comma Separated List
| Comma Separated List [message #790909] |
Sun, 05 February 2012 01:58  |
 Eric Springer
Messages: 5
Registered: January 2012 |
Junior Member |
|
|
I've simplified my problem to the point it sounds a bit silly, but if you can help me solve this, I can solve my real problem.
Imagine a comma separated list:
Ok, that's easy to parse:
Parser: vals+=ID (',' vals+=ID)*
But my grammar allows 1 or more separating comma, so this is valid:
Ok, still no problems:
Parser: vals+=ID (','+ vals+=ID)*
And my grammar has to allow 1 or more commas before the list, so this is valid:
Still, no problems:
Parser: ','* vals+=ID (','+ vals+=ID)*
Now, for the tricky part: my grammar allows 1 or more commas after this list. So this is valid:
,,,aaa,bbb,,,ccc,,ddd,,
Now, I can left-factor and get something like this:
Parser: ','* (val=ID rest=ParserRest)?;
ParserRest: ','+ (val=ID rest=ParserRest)?;
Which seems to work, but gives me an ugly "linked-list" sort of structure of vals. Is there a better way to do this, and is it possible to use the "tree rewrite" operations in fixing this up?
[Updated on: Sun, 05 February 2012 02:25] Report message to a moderator |
|
|
| Re: Comma Separated List [message #791027 is a reply to message #790909] |
Sun, 05 February 2012 06:33  |
Ed Willink
Messages: 6614
Registered: July 2009 |
Senior Member |
|
|
Hi
For the problem as you described it,
,,,aaa,bbb,,,ccc,,ddd,,
could be parsed by
Parser: ','* vals+=ID (','+ vals+=ID)* ','*
but I suspect that you want a sequence of Parser, which is where you
will hit problems. Do the ','s (new-lines) belong with the preceding or
subsequent Parser. It is ambiguous and the tool cannot decide.
You may be able to achieve something with syntactic precedences to
favour one direction of resolution, but without understanding why you
want to parse the new-lines at all, I cannot suggest a resolution. It
would seem much easier to leave the new-lines as whitespace and rescue
the surrounding characters from the tokens once parsing has completed.
Consider the Java
int a; // This is a
// This is some text
int b; // This is b
Does "This is some text" elaborate "a" or "b"? Who knows? A simple
choice is that comments end at the end of the line containing the
associated token, so "This is some text" goes with "b". Perhaps your
new-lines need a similar plausible policy.
Regards
Ed Willink
On 05/02/2012 01:58, Eric Springer wrote:
> I've simplified my problem to the point it sounds a bit silly, but if
> you can help me solve this, I can solve my real problem.
>
>
> Imagine a comma separated list:
>
> aaa,bbb,ccc,ddd
>
> Ok, that's easy to parse:
>
> Parser: vals+=ID (',' vals+=ID)*
>
> But my grammar allows 1 or more separating comma, so this is valid:
>
> aaa,bbb,,,ccc,,ddd
>
> Ok, still no problems:
> Parser: vals+=ID (','+ vals+=ID)*
>
>
> And my grammar has to allow 1 or more commas before the list, so this
> is valid:
> ,,,aaa,bbb,,,ccc,,ddd
>
>
> Still, no problems:
> Parser: ','* vals+=ID (','+ vals+=ID)*
>
>
> Now, for the tricky part: my grammar allows 1 or more commas after
> this list. So this is valid:
>
> ,,,aaa,bbb,,,ccc,,ddd,,
>
>
> But I'm totally stumped how to do this in XText or a non-backtracking
> LL parser. Any help would be appreciated.
>
>
> [For those wondering, in my real grammar they're not comma's but new
> lines :d]
>
>
|
|
| |
Goto Forum:
Current Time: Sun Mar 29 07:08:49 GMT 2020
Powered by FUDForum. Page generated in 0.02158 seconds |
Search
Help
Register
Login
Home
