| [XPand] strange failure (no viable alternative at input) [message #643074] |
Fri, 03 December 2010 17:42  |
Eclipse User |
|
|
|
Originally posted by: toh.fh-zwickau.de
Hi,
I'm switching from XPand 0.7.2 to the current XPand 1.0.1 and get an error, which is often related with encoding issues:
ERROR | WorkflowRunner | no viable alternative at input 'Â' on line 1
org.eclipse.internal.xtend.xtend.parser.ParseException: no viable alternative at input 'Â' on line 1
Because all templates worked fine under XPand 0.7.2, I played a bit around and tried to isolate the problem. If a have a template like this, everything works fine:
«REM»
Performs the generation of javadoc comments
works not deterministic
«ENDREM»
«IMPORT gcore»
«DEFINE Root FOR MModel -»
«ENDDEFINE»
If I change just the words in the third line of the comment, so the template appears as follows, it doesn't work anymore:
«REM»
Performs the generation of javadoc comments
i dont understand it
«ENDREM»
«IMPORT gcore»
«DEFINE Root FOR MModel -»
«ENDDEFINE»
However, I found a general workaround to move the import statement before the comment, so the template is again working correctly:
«IMPORT gcore»
«REM»
Performs the generation of javadoc comments
i dont understand it
«ENDREM»
«DEFINE Root FOR MModel -»
«ENDDEFINE»
This problem is somehow weird. It seams it has something to do with the multi line comment. Do you have any idea about the reason for this behavior? Personally I can live with the workaround, but interested in the cause of the problem. All templates are utf-8 encoded.
kind regards
tobi
|
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04142 seconds
Home