Path: utzoo!attcan!uunet!acw!guthery
From: guthery@acw.UUCP (Scott Guthery)
Newsgroups: comp.lang.c++
Subject: C++ Not Ready for Commercial Use
Message-ID: <24.UUL1.3#913@acw.UUCP>
Date: 15 Oct 89 12:55:35 GMT
Organization: Austin Code Works
Lines: 50

When thinking about using C++ for a real programming project consider the 
following:

	1) C++ is *NOT* a superset of C.
	2) C++ has been under development for over 10 years and it 
           still isn't done.
	3) An incompatible Release 2.0 just came out this year; existing
	   C++ projects must either be rewritten or use two different
	   incompatible compilers for the same langauge in their builds.
	4) C++ experts are still arguing about how many features of C++ 
           do work and should work.
	5) Release 3.0 of C++ is under active development; still more
	   features will be added and existing featurres "improved"; no
	   guarantees about upward compatibility with 2.0 have been made.
	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.
	7) According to its author, C++ is designed for programs
	   measured in thousands of lines of code.  The author goes
	   to say that if the program is measured in tens of thousands
	   of lines of code "mere progrmming language structuring
	   facilities can provide little relief."  He's absolutely right.
	8) There is no software management methodology for inheritance,
	   overloading, or persistent state among other C++ features.
	9) The current version of the language has only a operational 
	   definition; the final version has no definition at all.
       10) There are no industrial grade development, debugging,
           software management, configuration control or proram analysis 
           tools for C++.

There's no way a software project manager who cares about the quality, 
deliverability, manageability, or long-term viability of his product 
would commit a real software project to C++ in its current state.  In
fact I've got to wonder about the software engineering skills of 
someone who would even think about committing a project to an undefined
programming language.  While you wait for Release 3.0, read "The Dark Side 
of C++" in the Proceedings of ECOOP '88.

							Cheers, Scott

+*+*+*+*+*+*+*+*+*+*+*+*+ Austin Code Works +*+*+*+*+*+*+*+*+*+*+*+*+*+*+**+*+
NET Domain: guthery@uunet.uu.net           Post:  11100 Leafwood Lane
COM Domain: guthery@acw.com                       Austin, Texas 78750-3409 USA
US  Domain: guthery@acw.austin.tx.us       FAX:   +1 (512) 258-1342
Path:       {uunet}!acw!guthery            Voice: +1 (512) 258-0785
Work:       guthery@asc.slb.com            TELEX:    446370 (austincodewrks)
Packet:     N5MDE @ KB5PM                  EasyLink: 62752994
Fidonet:    1:382/12                       Prodigy:  KSWS89A 
+*+*+*+*+*+*+*+*+*+*+*+*+* The Source of C +*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+