[il-antlr-interest: 24368] [antlr-interest] Some about C header parser problems

Hi, I am writing a C header parser, but I find some problems about macro define specifier. There are three kinds of macro define specifier: 1. No arguments macro define specifier.The general form is: #define identifier string(#define Ext extern) 2. With arguments macro define specifier.

[il-antlr-interest: 24366] [antlr-interest] FW: Some about C header parser problems

From: fo...@live.cn To: antlr-interest-ow...@antlr.org Subject: Some about C header parser problems Date: Fri, 26 Jun 2009 08:20:11 +0800 Hi, I am writing a C header parser, but I find some problems about macro define specifier. There are three kinds of macro define specifier: 1. No

[il-antlr-interest: 24365] Re: [antlr-interest] using ANTLR for IDL compiling/code generation

Yep. Thanks. On Thu, Jun 25, 2009 at 12:53 PM, Gavin Lambert wrote: > At 04:51 25/06/2009, Tim Black wrote: > >> My main hesitation is that it looks like I am still going to have to >> implement a preprocessor of sorts to allow #including other .idl files. Is >> there anything like support for th

[il-antlr-interest: 24364] Re: [antlr-interest] incorrect order for executing actions?

Your references should be $sel and not sel. If that does not work then you are most likely not actually hitting the rule that you think you are or you are getting to the rule that accesses the scope through a rule path that does not create the scope so the scope stack is empty. Use the java

[il-antlr-interest: 24363] [antlr-interest] incorrect order for executing actions?

Hi, I use ANTLR to instantiate a metamodel of Java by calling the appropriate constructors in actions. Sometimes, I must pass on an expression to other rules using dynamic scopes. But in the example below, which is based on the Java.g grammar on your website, things go wrong. I have remove

[il-antlr-interest: 24362] Re: [antlr-interest] using ANTLR for IDL compiling/code generation

At 04:51 25/06/2009, Tim Black wrote: >My main hesitation is that it looks like I am still going to have >to implement a preprocessor of sorts to allow #including other >.idl files. Is there anything like support for this in ANTLR? You mean like this:

[il-antlr-interest: 24361] NAIL FUNGAL INFECTION IS NOT A CHOICE OF YOURS. (TABS - 430)

L|CENSED P|LLS ONL|NE GO GO GO --~--~-~--~~~---~--~~ 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,

[il-antlr-interest: 24360] [antlr-interest] Question about CommonTokens in Java Hashmaps

Hi, i have short question about org.antlr.runtime.Token instances in Java standard collections. Since (as far as i can see from the source) the mentioned class does not override hashCode and equals i have troubles to use this with standard containers like HashMap or Vector. What can i do to solve

[il-antlr-interest: 24358] [antlr-interest] How can I selectively avoid tokenization?

Hi, In my current project, I need to recognize and parse expressions marked by $<...> (where '...' represents the omitted expression) in an arbitrary text (not containing $<). How can I tell the (Antlr-generated) lexer to ignore text outside the $<...> marks? I have tried to recognize each chun

[il-antlr-interest: 24357] Re: [antlr-interest] using ANTLR for IDL compiling/code generation

Hi Tim, On Wed, Jun 24, 2009 at 6:51 PM, Tim Black wrote: > My main hesitation is that it looks like I am still going to have to > implement a preprocessor of sorts to allow #including other .idl files. Is > there anything like support for this in ANTLR? I haven't yet tried to handle includes my