Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!snorkelwacker!mit-eddie!uw-beaver!rice!cs.utexas.edu!milano!cadillac!vaughan@mcc.com
From: vaughan@mcc.com (Paul Vaughan)
Newsgroups: comp.lang.c++
Subject: Re: C++ Not Ready for Commercial Use
Message-ID: <3319@cadillac.CAD.MCC.COM>
Date: 16 Oct 89 16:37:55 GMT
References: <24.UUL1.3#913@acw.UUCP>
Sender: news@cadillac.CAD.MCC.COM
Reply-To: vaughan@mcc.com (Paul Vaughan)
Organization: MCC VLSI CAD Program
Lines: 20
In-reply-to: guthery@acw.UUCP (Scott Guthery)


	   6) C++ violates much of Wirth's advice about how programming languages
	   should be designed & developed; programming languages are not just
	   bags of tricks and features to be added to at will but this is how
	   C++ is being developed.

	While nearly everyone dabbles in proposing features for C++, I
think Bjarne is doing an excellent job of identifying the real
requirements and carefully assessing the consequences of the various
proposals.  While you might say that he adds features at will, I would
add that his will is well considered and respectable.
	Also, in my use of the g++ succession of revisions, I find
that updating programs to use the latest and greatest is not
particularly difficult and that it usually uncovers latent bugs and
inefficiencies.  Changing my code is no problem, waiting for someone
else to change theirs (libraries, for instance) can be.  Compiler
evolution is not such a bad thing.

 Paul Vaughan, MCC CAD Program | ARPA: vaughan@mcc.com | Phone: [512] 338-3639
 Box 200195, Austin, TX 78720  | UUCP: ...!cs.utexas.edu!milano!cadillac!vaughan