Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: maurits.de.jong at ericsson dot com
Created attachment 34387
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34387&action=edit
The offending source separately
I would have expected this
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64509
--- Comment #2 from Martien de Jong ---
That's just rephrasing my bugreport. The question is, should it type check
while parsing an expression that may not be realized? The entire idea of
switching on a type is to prevent and fix type errors, no?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64509
--- Comment #4 from Martien de Jong ---
I understand. What a shallow and ugly feature it is then. I think it can only
usefully be employed using a preprocessor macro, yet it is part of the
expression syntax. It is meant to resolve type issues, y
