Re: Rest of trivial decorations

[Jan Hubicka <hubicka at ucw dot cz>]

> On Sat, Apr 18, 2009 at 16:47, Jan Hubicka <hubicka@ucw.cz> wrote:
> >
> > OK, thanks for pointer! ?Does this seem fine?
> > Honza
> >
> > [...]
> >
> > +#ifndef _GLIBCXX_NOTHROW
> > +# ifdef __cplusplus
> > +# ?define _GLIBCXX_NOTHROW throw()
> > +# else
> > +# ?define _GLIBCXX_NOTHROW __attribute__((nothrow))
> > +# endif
> > +#endif
> > +
> >
> 
> By my reading, those two definitions have different meanings
> (http://gcc.gnu.org/onlinedocs/gcc-4.3.3/gcc/Function-Attributes.html),
> since throw() can lead to terminate, whereas the latter is presumably
> UB if an exception is thrown.
> 
> Since these are cases that certainly don't throw, is there a reason to
> not just use __attribute__((nothrow)) always?  That ought to solve any
> issue with spurious try/catch additions, too...

Adding nothrow attribute to these c/c++ headers is fine with me too.

Honza
> 
> ~ Scott