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

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.

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

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.

  Puff Addison
--

Dr. J. D. ADDISON
System Manager
Transport Parallel Computing Centre
University of London Centre for Transport Studies
University College London
email:puff@transport.ucl.ac.uk