[cfe-dev] static const POD object
zapadinsky at gmail.com
Tue Feb 19 00:13:36 PST 2013
> We can weaken this restriction in MS compatibility mode, but I don't
otherwise think this is a compiler defect.
It should be weaken in MS compatibility mode for sure. Now clang can't
compile our sources which pass compilation on MSVC and gcc (with
-fpermissive switch). For now I have no other option...
And it is not a compiler defect. But why not to weaken this restriction by
default? What harm can it cause? Clang is not a standard compliance tester.
Allowing to instantiate static const objects will not lead to any undefined
behavior. So its pretty safe by themselves and will save nervous to someone.
View this message in context: http://clang-developers.42468.n3.nabble.com/static-const-POD-object-tp4030470p4030487.html
Sent from the Clang Developers mailing list archive at Nabble.com.
More information about the cfe-dev