This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug c++/21543] Full specialization of templates not supported in classes


------- Additional Comments From sven at clio dot in-berlin dot de  2005-05-15 18:20 -------
(In reply to comment #8) 
> Let me say this,  the standard is needed otherwise, there is no language  
> defined as C, just like there phython is not really defined. 
 
Did You know that You can not write a C preprocessor in ANSI C (at least none, 
You want to work with)? ANSI C lacks the necessary standardization of the 
underlying file system, thus, You do not know how to combine a path with an 
include file enclosed in brackets (#include <stdiio>). 
 
Python is defined. There is only one Python interpreter and Python is, what 
the interpreter does. It has the advantage, that it is not standardized but 
developed by the comunity. Compared to C (which has beside ANSI the POSIX, 
XOPEN, BSD and what not as a library 'standard') I see this aproach as an 
advantage. I do not think that there is any C compiler which implements _only_ 
the ANSI/ISO standard. Of course, ANSI/ISO C is underdefined (as far as I 
know) because the standardization comitee does not publish a test suite for 
standard conformance (unlike Python, Perl, Java, PHP). 
 
> Oh, and people who write GCC are both on the C and C++ ISO committees. 
 
Sorry, if You feel personal insulted. It was not intended. 
 

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21543


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]