On Mon, Feb 12, 2007 at 01:30:41PM -0800, Richard Henderson wrote: > On Mon, Feb 12, 2007 at 01:16:43PM -0800, Ian Lance Taylor wrote: > > Mark Mitchell <[EMAIL PROTECTED]> writes: > > > > > But, aren't big C++ shared libraries rather different? Does KDE > > > actually use throw() everywhere, or visibility attributes? But, > > > presumably, most people don't replace the implementation of > > > ScrollBar::ScrollUp or whatever. I'd be happy to know I'm wrong here, > > > but I'd be surprised if there aren't large amounts of legacy code that > > > would be hurt by this change. Do you disagree? > > > > I don't really have any doubt that somebody, somewhere, wants to > > override a function in a C++ shared library, and wants the overriding > > function to throw an exception. There is really only one correct > > compiler behaviour here. > > I strongly agree that there is only one correct behaviour here. > > If KDE doesn't use throw(), or visibility attributees, that's a > failing in KDE, not the compiler.
Will 4.1.2 be worse than 4.1.1 for code that has these kinds of failings? If so, then it might be better to push the fix that allows overrides that throw back to 4.2, and circulate warnings to affected projects that they will want to use throw() and attributes more, giving them until 4.2 to fix any issues found.
