It is awesome that you have started to port to Xtext 1.0. I did a quick
attempt the other day but got stuck on some scoping issues and then I have
not had time to look at it more.
One thing in the grammar that I think we should change is the way we handle
unordered groups. At a lot of places we have things like
((attributes+=DslAttribute) |
(references+=DslReference))*
I think that should be done with &
Look in http://www.eclipse.org/Xtext/documentation/1_0_0/xtext.html Xtext
doc , search for 'Unordered Groups'.
/Patrik
wrungel wrote:
>
> Hello,
> I'm trying to port the sculture framework to Xtext Version 1.0.1 and have
> an issue with Sculptordsl.xtext:
>
> Output of the GenerateSculptordsl.mwe:
> warning(205):
> ../org.xtext.example.mydsl.ui/src-gen/org/xtext/example/mydsl/ui/contentassist/antlr/internal/InternalMyDsl.g:1:8:
> ANTLR could not analyze this decision in rule Tokens; often this is
> because of recursive rule references visible from the left edge of
> alternatives. ANTLR will re-analyze the decision with a fixed lookahead
> of k=1. Consider using "options {k=1;}" for that decision and possibly
> adding a syntactic predicate.
> warning(209):
> ../org.xtext.example.mydsl.ui/src-gen/org/xtext/example/mydsl/ui/contentassist/antlr/internal/InternalMyDsl.g:32917:1:
> Multiple token rules can match input such as "'w'": T129, RULE_ID,
> RULE_ANY_OTHER
> As a result, tokens(s) RULE_ID,RULE_ANY_OTHER were disabled for that input
> warning(209):
> ../org.xtext.example.mydsl.ui/src-gen/org/xtext/example/mydsl/ui/contentassist/antlr/internal/InternalMyDsl.g:32917:1:
> Multiple token rules can match input such as "'>'": T25, RULE_ANY_OTHER
> As a result, tokens(s) RULE_ANY_OTHER were disabled for that input
> ...
>
> The warning results in erroneous auto-completion in the generated DSL
> Editor.
>
> After some experiments with reducing the Xtext grammar I realized that
> removing either "attributes" or "references" in the grammer rule
> "DslCommandEvent" fixes the warning but some Xtend generator templates
> gets broken.
>
> What can be wrong with the grammar? There are no problems with Xtext 0.7.X
> and same grammar.
>
> I think this question is rather to Xtext/ANTLR experts.
>
> May be there are such experts here?
>
>
>
>
>
--
View this message in context:
http://old.nabble.com/ANTLR-issue-with-Xtext-1.0.1-tp29613279s17564p29614729.html
Sent from the Fornax-Platform mailing list archive at Nabble.com.
------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:
Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
Fornax-developer mailing list
Fornax-developer@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fornax-developer
