|
|
|
|
|
|
|
|
|
Re: generated ParsetreeConstructor file doesn't compile after upgrade from xtext 2.9.2 to xtext 2.13 [message #1781910 is a reply to message #1781906] |
Wed, 14 February 2018 15:11 |
Clément Hurlin Messages: 10 Registered: February 2014 |
Junior Member |
|
|
I wasn't aware it was so easy to replace the fragment being used! I confirm it fixes the bug on all 3 grammars I tested, thank you very much; we can continue our update now.
And I've confirmed with the local xtext master that we'll update to the new generator soon :-) so hopefully we won't bother you again ☺
On a final note, I've tried to turn all multiline comments into single line comments (//) in our grammars, but there was one position where */ was used in a rule, which still triggered the bug:
ML_StandaloneSMDoc:
{ML_StandaloneSMDoc}
// first line
body+=ML_StandaloneSMDocFirstLineBody
// Intermediate lines
(body+=NewLine //
//
body+=ML_SMDocNextLineBody)* //
// closing
body+=NewLine?
'*/'; // <- Here's the one
so it isn't a viable workaround after all.
[Updated on: Wed, 14 February 2018 15:13] Report message to a moderator
|
|
|
|
Powered by
FUDForum. Page generated in 0.03452 seconds