Parse with source code language in mind (C vs. C++ vs. Objective-C)

hzzc1987 / jnaerator

Automatically exported from code.google.com/p/jnaerator

0 stars 0 forks source link

Parse with source code language in mind (C vs. C++ vs. Objective-C) #7

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago

Currently the parser doesn't mind which language the input files were written 
into.

As a result, "class", which is a reserved keyword in C++, is not parsed as a 
valid identifier in C.

Likewise, it is hard to know whether a symbol should be C++-mangled (behaviour 
by default in 
*.cpp files) or not (behaviour by default in *.c files).

We should either provide a command-line switch or use the existing 
__cplusplus__ symbol to force 
a language.

Original issue reported on code.google.com by olivier.chafik@gmail.com on 20 Feb 2009 at 8:54

GoogleCodeExporter commented 8 years ago

Original comment by olivier.chafik@gmail.com on 20 Feb 2009 at 8:54

Added labels: Parser

GoogleCodeExporter commented 8 years ago

Original comment by olivier.chafik@gmail.com on 21 Feb 2009 at 9:58

Added labels: Component-Parser
Removed labels: Parser

GoogleCodeExporter commented 8 years ago

Original comment by olivier.chafik@gmail.com on 3 Jun 2009 at 5:43

Changed state: Started

GoogleCodeExporter commented 8 years ago

Hi,
This issue moved to Github :
https://github.com/ochafik/nativelibs4java/issues/115

Thanks for not updating this page anymore and adding further comments on Github.
Cheers
--
zOlive

Original comment by olivier.chafik@gmail.com on 1 Sep 2011 at 7:23

Changed state: MigratedToGitHub