This is the mail archive of the gcc-help@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]

gcc gets in the way of writing C that is also C++ wrt const



I try to write C code that is valid C++ and has the same meaning in C++.


const int a = 1;


does not have the same meaning in C and C++.


So I would write:


extern const int a = 1;


which does have the same meaning in both, but for some reason gcc doesn't quite like this and gives a warning.


I end up doing:


/* const is extern const in C, but static const in C++,
* but gcc gives a warning for the correct portable form "extern const" */
#if defined(__cplusplus) || !defined(__GNUC__)
#define EXTERN_CONST extern const
#else
#define EXTERN_CONST const
#endif


EXTERN_CONST int a = 1;



which is just lame.


- Jay


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]