🚀 go-pugleaf

In article 95Aug17235324@physics2.Berkeley.EDU, rupenp@sdd.hp.com (Rupen Patel) writes:
>Does anyone know where I can get a copy of the draft standard?  Is it in any
>new books (ie. Strostroup's(sp) C++ book).
>

Here is an excerpt from the Readme file at the ftp site:
---
Steve Clamage, stephen.clamage@eng.sun.com

---------------------------------------------------------


The files in this directory are available from the following sites:

	research.att.com:/dist/c++std/WP
	ftp.maths.warwick.ac.uk:/pub/c++/std/WP
	ftp.su.edu.au:/pub/C++/CommitteeDraft

In this directory, you will find fourteen files:

	README		(this file)
	
	coversheet.ps.Z
	foreword.ps.Z
	contents.ps.Z
	body.ps.Z
	index.ps.Z
	concordance.ps.Z

	covershe.pdf
	foreword.pdf
	contents.pdf
	body.pdf
	index.pdf
	concorda.pdf

	body.pd1
	body.pd2

The files with .ps in their names are compressed PostScript files,
intended to be printed in the sequence given above.  The whole thing
takes up 720 pages, of which most is in the body.

The files with .pdf in their names are in Adobe PDF format, intended
to be read by the Adobe Acrobat browser.  This browser is available
free of charge for several popular platforms from Adobe by anonymous
FTP from ftp.adobe.com; look in directory pub/adobe/Acrobat.

Files body.pd1 and body.pd2 when concatenated form a file identical to
body.pdf; they are split this way so that each one will fit on a
single DOS diskette.

The purpose of each file should be obvious--except for `concordance,'
which connects subclause numbers with their symbolic names.  Each
subclause has a number, a title, and a symbolic name (which appears in
square brackets after the title).  Future editions of this Working
Paper may well have different subclause numbers, but the symbolic
names are intended to remain constant as long as the subclauses to
which they refer continue to exist.

[ comp.std.c++ is moderated.  Submission address: std-c++@ncar.ucar.edu.
  Contact address: std-c++-request@ncar.ucar.edu.  The moderation policy
  is summarized in http://dogbert.lbl.gov/~matt/std-c++/policy.html. ]