X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f From: =?UTF-8?B?UmFmYcWC?= Newsgroups: comp.os.msdos.djgpp Subject: Re: Modern c++, c++0x (g++ 4.4 and above) in DJGPP Date: Sat, 26 Jul 2008 23:11:41 +0200 Organization: limcore.com Lines: 25 Message-ID: References: <92187018-bd11-41d0-a2ff-b7c7135393b8 AT z66g2000hsc DOT googlegroups DOT com> NNTP-Posting-Host: aaiz110.neoplus.adsl.tpnet.pl Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Trace: inews.gazeta.pl 1217106864 29108 83.4.233.110 (26 Jul 2008 21:14:24 GMT) X-Complaints-To: usenet AT agora DOT pl NNTP-Posting-Date: Sat, 26 Jul 2008 21:14:24 +0000 (UTC) X-User: lcnews User-Agent: KNode/0.10.9 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Rugxulo wrote: > Also, C++0x isn't finalized yet (hence, the 'x'). So even if there is > experimental support in GCC, I don't think most people (should?) use > it yet, at least not for another year or so. People are already writting in C++0x (using parts of C++0x that are working in g++ 4.3, and some even this from 4.4) > Modern C++ programs?? Such as what?? What exactly won't compile with G+ > + 4.2.3 which we already have and use? http://gcc.gnu.org/projects/cxx0x.html Rvalue references are very interesting trick for example (too bad they dont yet work fully) And I can't wait for the "auto" variable (as in, auto-type variable, not the old "auto" keyword).