[cfe-dev] static const POD object

David Blaikie dblaikie at gmail.com
Tue Feb 19 00:30:30 PST 2013

On Tue, Feb 19, 2013 at 12:13 AM, zapadinsky <zapadinsky at gmail.com> wrote:

> > 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.

This is a proposal/suggestion to provide a language extension. Here's the
documentation/process the Clang community uses to assess such proposals:

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20130219/84ade4bb/attachment.html>

More information about the cfe-dev mailing list