Joern Rennecke <amyl...@spamcop.net> writes:

> Quoting Ian Lance Taylor <i...@google.com>:
>
>> Joern Rennecke <amyl...@spamcop.net> writes:
>>> ...   Could we use a #define
>>> for this?  E.g. put in system.h
>>> #ifdef __cplusplus
>>> #define CONST_VAR_DECL extern const
>>> #else
>>> #define CONST_VAR_DECL const
>>> #endif
>>
>> Yes, that is certainly the way to go if it is in fact not safe to use
>> "extern const int i = 1;" for all C compilers.  I hadn't planned to deal
>> with this issue yet, but since you bring it up, we should decide whether
>> that construct is safe, or whether we need the macro.
>
> I think it would also be a better interim solution, since it is easier to
> code, easier to switch experimentally, and easier to globally replace with
> extern const if we decide that that is safe for all the C bootstrap compilers
> we care about.

Seems reasonable, though I'd like to wait at least a couple of days to
see if anybody else has a comment.  I think the macro name should simply
be EXTERN_CONST.

Ian

Reply via email to