On Mon, Apr 3, 2017 at 9:34 AM, David Chisnall <[email protected]> wrote:
> On 2 Apr 2017, at 19:28, Niels Grewe <[email protected]> wrote: > > > > Yes, it seems that gcc and clang disagree on how to interpret const. > Here's a PR that addresses this particular problem: > > > > https://github.com/gnustep/libobjc2/pull/22 > > This still looks like a GCC issue. The C standard includes values stored > in other const variables as permitted in integer constant expressions. > > David > 5.4 is almost a year old, so maybe this was fixed. However, I'm not sure it would be so bad to have a workaround for this compiler? There is already a warning that clang should be used (which I, of course, switched to; I prefer it anyway). But having a workaround to make it work with GCC, even in a basic, unsupported way, is probably still good?
_______________________________________________ Gnustep-dev mailing list [email protected] https://lists.gnu.org/mailman/listinfo/gnustep-dev
