This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Gabriel Dos Reis <gdr@cs.tamu.edu> writes:
[...]
| Attempt to get the GNU C++ compiler through the same massage is | underway (but I'm going to bed shortly ;-)).
I can also report that I got the GNU C++ compiler through -- and apart form uses of C++ keywords (template, namespace, class), it worked out. A note on type sfety issue though: lookup_name() is declared in c-tree.h as
extern tree lookup_name (tree);
and used in c-common.c:handle_cleanup_attribute() according to that signature. It is however declared and defined in cp/ as
extern tree lookup_name (tree, int);
That was caught at link time (and dealt with).
-- Gaby
Would it be possible to add a diagnostic to GCC to warn when C++ keywords are being used as identifiers? Maybe also add any objective C keywords too.
This seems like it would be useful to someone writing library functions that could, at some later time, be imported (cut and paste) into code for the other languages, as well as for code being converted from C to C++.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |