This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: __builtin_cpow((0,0),(0,0))
On 2005-03-10 01:01:18 +0100, Gabriel Dos Reis wrote:
> No. I mean when I call powi() either through built-ins or appropriate
> overload (several programming languages do so), I expect sane semantics.
What is powi()? I couldn't find it in the C standard. It isn't
in the Linux man pages either.
> The asseryion that 0^0 is mathematically undefined is not a bogus
> reason. It is a fact.
I disagree. One can mathematically define 0^0 as 1. One often does
this.
--
Vincent Lefèvre <vincent@vinc17.org> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/>
Work: CR INRIA - computer arithmetic / SPACES project at LORIA
- References:
- Re: __builtin_cpow((0,0),(0,0))
- Re: __builtin_cpow((0,0),(0,0))
- Re: __builtin_cpow((0,0),(0,0))
- Re: __builtin_cpow((0,0),(0,0))
- Re: __builtin_cpow((0,0),(0,0))
- Re: __builtin_cpow((0,0),(0,0))
- Re: __builtin_cpow((0,0),(0,0))
- Re: __builtin_cpow((0,0),(0,0))
- Re: __builtin_cpow((0,0),(0,0))
- Re: __builtin_cpow((0,0),(0,0))