Problems with PR 21210

Mark Mitchell mark@codesourcery.com
Wed Jun 1 05:52:00 GMT 2005


Nathan (Jasper) Myers wrote:
> On Tue, May 31, 2005 at 08:09:37PM -0700, Mark Mitchell wrote:
> 
>>Nathan (Jasper) Myers wrote:

>>Under this interpretation, would you have to #include <complex> before 
>>you got to use _Complex?  (That's not true in C99.)
>  
> Of course not.

Well, I asked, because you have to #include <typeinfo> before you can 
use std::type_info, which is rather more built-in than std::complex in 
most compilers.

However, I've always thought that restriction somewhat lame. :-)

> This also depends on somebody not myself doing a not-insubstantial
> amount of core compiler work to make it happen; and somebody else
> jimmying the libstdc++ headers to match, presumably a lesser task.

I agree that this could be made to work, by essentially hard-wiring 
std::complex/_Complex into the compiler, rather than defining it in the 
library.

That would be a considerably more radical change, though; historically, 
G++ has indeed treated the types as separate.

-- 
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com
(916) 791-8304



More information about the Gcc-patches mailing list