Hi All.

I thought I would get my feet wet by writing a parser for Objective-C  
type encodings. I thought it would be pretty easy for such a brief  
"language", but it is turning out to be pretty difficult.

One of the problems lies in parsing something like this:

     {vids=^vids}

which means a struct named "vids", which is composed of void * (^v),  
int, double, and short.

After the "{", I need to interpret vids as a single token, and after  
the "=", I need to interpret the characters as separate tokens.

One of the interesting things I found was that this is legal:

     NUMBER : '0'..'9';

but this is not:

     number : '0'..'9';

I bumped into this because I thought I'd "inline" the rule for the  
name after the "{". Can someone explain this?

Is there a way I can say, "use tokenizer rule A after the "{", but use  
tokenizer rule B after the "=".

AntlrWorks has been great for learning by playing. Thanks for any help!

-Kenny


List: http://www.antlr.org:8080/mailman/listinfo/antlr-interest
Unsubscribe: 
http://www.antlr.org:8080/mailman/options/antlr-interest/your-email-address


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"il-antlr-interest" group.
To post to this group, send email to il-antlr-interest@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/il-antlr-interest?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to