Related articles |
---|
maturity of the c++ compiler technology Vincenzo.DeFlorio@esat.kuleuven.ac.be (Vincenzo De Florio) (1999-10-04) |
Re: maturity of the c++ compiler technology ian@five-d.com (1999-10-06) |
Re: maturity of the c++ compiler technology jkahrs@castor.atlas.de (Juergen Kahrs) (1999-10-06) |
Re: maturity of the c++ compiler technology paul@toilet.dera.gov.uk (1999-10-11) |
Re: maturity of the c++ compiler technology jandk@easynet.co.uk (Jonathan Barker) (1999-10-11) |
Re: maturity of the c++ compiler technology per@bothner.com (Per Bothner) (1999-10-11) |
Re: maturity of the c++ compiler technology joerg.brunsmann@FernUni-Hagen.de (Joerg Brunsmann) (1999-10-11) |
Re: maturity of the c++ compiler technology Juergen.Kahrs@t-online.de (Juergen Kahrs) (1999-10-13) |
From: | Joerg Brunsmann <joerg.brunsmann@FernUni-Hagen.de> |
Newsgroups: | comp.compilers |
Date: | 11 Oct 1999 02:38:43 -0400 |
Organization: | Compilers Central |
References: | 99-10-023 99-10-029 |
Keywords: | C++, practice |
Juergen Kahrs wrote:
> Really, has it reached a "reliable status" ?
After reading
http://www.mozilla.org/hacking/portable-cpp.html
the answer is 'no'. For example:
1.Don't use C++ templates.
2.Don't use static constructors.
3.Don't use exceptions.
4.Don't use Run-time Type Information.
5.Don't use namespace facility.
...
J=F6rg
Return to the
comp.compilers page.
Search the
comp.compilers archives again.