This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: throw(), pure and const flags on functions
On Wed, Apr 15, 2009 at 10:57 PM, Mark Mitchell <mark@codesourcery.com> wrote:
> Gabriel Dos Reis wrote:
>
>> Yes. ?But now, if f() is a standard C function that cannot
>> possibly throw, then annotating g() 'throw()' makes g unnecessarily
>> bigger and slower. ?Thus my suggestion of having the compiler
>> uses the standard semantics of f() it already has as opposed
>> to having to annotate g().
>
> That's not in dispute.
Great!
So, what is in dispute? :-)
> ?Of course if the compiler knows something
> valuable, it should use that fact.
>
> --
> Mark Mitchell
> CodeSourcery
> mark@codesourcery.com
> (650) 331-3385 x713
>
- References:
- Re: throw(), pure and const flags on functions
- Re: throw(), pure and const flags on functions
- Re: throw(), pure and const flags on functions
- Re: throw(), pure and const flags on functions
- Re: throw(), pure and const flags on functions
- Re: throw(), pure and const flags on functions
- Re: throw(), pure and const flags on functions
- Re: throw(), pure and const flags on functions
- Re: throw(), pure and const flags on functions
- Re: throw(), pure and const flags on functions