From: Andrew <andnews AT ihug DOT com DOT oz DOT au>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: References to temporary objects in C++
Date: Sun, 18 May 2003 17:03:16 +1000
Organization: ECLiPSE
Lines: 42
Message-ID: <a8becvstep9c51onppd4g6ihjugvq0o1gh@4ax.com>
References: <3EC69975 DOT 55BE1034 AT alpha DOT delta DOT edu> <t7hdcvgmaocc9kjbmo1e3fu8tjunu7m253 AT 4ax DOT com> <3EC71725 DOT 6CF80C79 AT alpha DOT delta DOT edu>
NNTP-Posting-Host: p238-tnt4.syd.ihug.com.au
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Trace: lust.ihug.co.nz 1053241400 1036 203.173.134.238 (18 May 2003 07:03:20 GMT)
X-Complaints-To: abuse AT ihug DOT co DOT nz
NNTP-Posting-Date: Sun, 18 May 2003 07:03:20 +0000 (UTC)
X-Newsreader: Forte Agent 1.93/32.576 English (American)
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

>> You didn;t indicate with GCC you are using. It would be GCC, for more
>> info on GCC see the GCC main page:-
>> http://www.gnu.org/software/gcc/gcc.html
>
>  I apologize for being unclear.  The frustrating experience I had in
>recent years was with one of the versions just before GCC 3.0 was
>released -- probably GCC 2.95, or something.  The version I used
>yesterday was GCC 3.22, a very recent release.
If you are using the DJGPP 2.03 then go and grab the GCC 3.2.3 as this
fixed a small problem which has been present in 3.0.x <= GCC <= 3.2.2.
If you are using the 2.04 alpha 1 release then stick with it until the
next alpha release.
>  My intention was not to complain, but to indicate pleasant surprise. 
>I was wondering if anyone else -- who has been using DJGPP all along --
>knew when support for passing temporary objects by reference became
>supported, out of curiosity.  It had to be within the past 2 years
>sometime.  I was just happy to see that some of Stroustrup's simple
>examples would finally work with DJGPP.
With each GCC release the changes make me more aware of the standard
and GCC 3.3 is no exception.  With GCC 3.3 it has tighter checks for
type casting which is just starting to be looked at because it affects
the DJGPP LIBC code. 

Have a look at the GCC change log or have a look at the GCC page and
see if you can find out when, but I would expect that this probably
occured in the GCC 3.0 release.

>  This is not meant as a criticism, much less an insult.  I have always
>been very grateful for the efforts of the DJGPP workers, and have meant
>to contribute to the project for several years.  It has, so far, been
>impossible for me to find time to bring my skills up to a level anywhere
>near what would be necessary.
I didn't take as an insult, I took it more as a query that I do not
know the exact answer, but do know where to point you so you can find
out yourself.

BTW the GCC 3.3 is still not fully compliant with the latest C++
standard and the plans are to keep on improving it. The GCC page has
links to the 3.4 delevelopment area if you want to see what will be
done in the future.

Andrew