On Wed, May 30, 2012 at 3:47 AM, Florian Weimer <fwei...@redhat.com> wrote: > On 05/29/2012 06:41 PM, Gabriel Dos Reis wrote: >> >> On Tue, May 29, 2012 at 11:00 AM, Florian Weimer<fwei...@redhat.com> >> wrote: >>> >>> This patch flags operator new on variably modified types as an error. >>> If this is acceptable, this will simplify the implementation of the >>> C++11 requirement to throw std::bad_array_new_length instead of >>> allocating a memory region which is too short. >>> >>> Okay for trunk? Or should I guard this with -fpermissive? >> >> >> I must say that ideally this should go in. However, this having >> been accepted in previous releases, I think people would like >> one release of deprecation. So my suggestion is: >> -- make it an error unless -fpermissive. >> -- if -fpermissive, make it unconditionally deprecated. >> -- schedule for entire removal in 4.9. > > > On the other hand, it is such an obscure feature that it is rather unlikely > that it has any users. The usual C++ conformance fixes and libstdc++ header > reorganizations cause much more pain, and no depreciation is required for > them. > > Perhaps we can get away here without depreciation, too?
That is a good point. Jason, what do you think? -- Gaby
