🚀 go-pugleaf

In article 95Aug3145118@motos.tsg.ucl.ac.uk, puff@motos.tsg.ucl.ac.uk (J. D. Addison X1572) writes:
>
>Can anyone point me to a summary of changes to C++ that cause what was once
>valid code to become broken code. In particular changes since "Ellis and
>Stroustrup" was published. I do not want to print all 720 pages of
>the standardisation working paper and there seems to be no easy way of
>printing parts, at least from the Postscript distribution. 

An appendix to Stroustrup's "C++ Programming Language" contains a
summary of changes to the language since the ARM. A postscript version
of this appendix is updated from time to time and is made available
for anonymous fpt at ftp.std.com in directory /AW/stroustrup2e.

---
Steve Clamage, stephen.clamage@eng.sun.com

puff@transport.ucl.ac.uk writes:
>Can anyone point me to a summary of changes to C++ that cause what was once
>valid code to become broken code. In particular changes since "Ellis and
>Stroustrup" was published. I do not want to print all 720 pages of
>the standardisation working paper and there seems to be no easy way of
>printing parts, at least from the Postscript distribution. 

From the gnu.g++.help FAQ:

The ANSI/ISO C++ standards committee have adopted some changes to the
C++ language since the publication of the original ARM, and newer
versions of g++ (2.5.x and later) support some of these changes, notably
the mutable keyword (added in 2.5.0), the bool type (added in 2.6.0),
and changes in the scope of variables defined in for statements (added
in 2.7.0).
You can obtain an addendum to the ARM explaining these changes by FTP
from ftp.std.com in @file{/AW/stroustrup2e/new_iso.ps}.

(The addendum isn't complete, but it lists the major stuff).

-- 
-- Joe Buck 	<jbuck@synopsys.com>	(not speaking for Synopsys, Inc)
Anagrams for "information superhighway":	Enormous hairy pig with fan
						A rough whimper of insanity

clamage@Eng.Sun.COM (Steve Clamage) wrote:
>In article 95Aug3145118@motos.tsg.ucl.ac.uk, puff@motos.tsg.ucl.ac.uk (J. D. Addison X1572) writes:
>>
>>Can anyone point me to a summary of changes to C++ that cause what was once
>>valid code to become broken code. In particular changes since "Ellis and
>>Stroustrup" was published. I do not want to print all 720 pages of
>>the standardisation working paper and there seems to be no easy way of
>>printing parts, at least from the Postscript distribution.
>
>An appendix to Stroustrup's "C++ Programming Language" contains a
>summary of changes to the language since the ARM. A postscript version
>of this appendix is updated from time to time and is made available
>for anonymous fpt at ftp.std.com in directory /AW/stroustrup2e.
>
>---
>Steve Clamage, stephen.clamage@eng.sun.com
>
>
The ARM itself is also updated periodically. The edition I have was
reprinted in April 1994. In this printing chapter 19 "summarizes the
major resolutions ... as of March 1994."



          Michael Taylor
	    michaelt@asymetrix.com