[metaas-dev] No viable alternative error
kiroukou
kiroukou at gmail.com
Sun Feb 18 23:02:53 UTC 2007
Last error I have :
run:
line 1:0 no viable alternative at character 'Ô'
line 1:1 no viable alternative at character 'ª'
line 1:2 no viable alternative at character 'ø'
line 1:0 no viable alternative at character 'Ô'
line 1:1 no viable alternative at character 'ª'
line 1:2 no viable alternative at character 'ø'
line 1:0 no viable alternative at character 'Ô'
line 1:1 no viable alternative at character 'ª'
line 1:2 no viable alternative at character 'ø'
line 1:0 no viable alternative at character 'Ô'
line 1:1 no viable alternative at character 'ª'
line 1:2 no viable alternative at character 'ø'
Exception in thread "main" java.lang.IllegalArgumentException:
expected IDENTIFIER, but token was a STAR
at uk.co.badgersinfoil.metaas.impl.ASTUtils.identText
(ASTUtils.java:67)
at uk.co.badgersinfoil.metaas.impl.ASTASArg.getType
(ASTASArg.java:37)
Isn't the Start type supported?
Thomas
Le 18 févr. 07 à 22:32, David Holroyd a écrit :
> On Sun, Feb 18, 2007 at 08:45:31PM +0000, David Holroyd wrote:
>> On Sun, Feb 18, 2007 at 09:18:49PM +0100, kiroukou wrote:
>>> line 1:0 no viable alternative at character '?'
>>> line 1:1 no viable alternative at character '?'
>>> line 1:2 no viable alternative at character '?'
>>> line 1:0 no viable alternative at character '?'
>>> line 1:1 no viable alternative at character '?'
>>> line 1:2 no viable alternative at character '?'
>
>> I'd still be interested to know where the 'no viable alt' messages
>> are
>> coming from though. Given that they are all reported at 'line 1', I
>> imagine this is actually a message about the code you are generating,
>> rather than the code you are parsing. I suspect that the error
>> reporting in some part of the lexical analysis needs to be
>> tightened up.
>>
>> Were the reported characters question marks ('?') at your end, or are
>> these actually non-ascii characters that are getting mangled by my
>> mail
>> client?
>
> Ok, using a different mail client, I now see that these are indeed
> just
> non-ascii characters.
>
> Is this intended? i.e. if i extend the ActionScript lexer to allow
> additional characters to appear in identifier names (for instance) is
> that going to help you?
>
>
> thanks!
> dave
>
> --
> http://david.holroyd.me.uk/
>
> _______________________________________________
> metaas-dev mailing list
> metaas-dev at lists.badgers-in-foil.co.uk
> http://lists.badgers-in-foil.co.uk/mailman/listinfo/metaas-dev
More information about the metaas-dev
mailing list