Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!pacbell.com!tandem!netcomsv!jls
From: jls@netcom.COM (Jim Showalter)
Newsgroups: comp.object
Subject: Re: C++ and a waitress called Ada
Message-ID: <1991Jun11.002302.2139@netcom.COM>
Date: 11 Jun 91 00:23:02 GMT
References: <1991Jun6.004107.25123@netcom.COM> <2325@media03.UUCP> <1991May24.015856.9979@csusac.csus.edu> <4034@ssc-bee.ssc-vax.UUCP> <1991May25.073216.15040@netcom.COM> <948@trotsky.mrcu> <285@devnull.mpd.tandem.com> <1991Jun6.225355.18611@netcom.COM> <1179@tetrauk
Organization: Netcom - Online Communication Services  UNIX System {408 241-9760 guest}
Lines: 30

>Perhaps the real choice should be between Ada and Eiffel - and I don't imply
>that I believe Eiffel is always preferable.  In many cases Ada will still be
>the better choice, but Eiffel offers the same approach within a "pure"
>object-oriented context.  C++ is not the only option.

My advocacy of Ada has always been based on my belief that it represents
a superb vehicle for software engineering. Other software engineering
oriented languages have appeared on the scene, and I've started learning
them too--I hope to soon be able to add Eiffel and Modula-3 to my .sig.
The only real problem I have with some of these other languages now is
maturity--it took a long time (about twice as long as expected) for real
compilers and other tools to become available for Ada, and the same can
be expected for these other languages (indeed, without the sort of funding
Ada got from the DoD, progress could be even slower). On the plus side,
there isn't the DoD "taint" to be reckoned with, so commercial acceptance
may be easier. I certainly hope so--these other languages provide a valid
alternative to the headlong dash toward C++.

In the end, the critical thing is not so much that a software development
organization choose Ada instead of Eiffel, or Modula-3 instead of C++.
The truly important thing is that a software development organization choose
ANY of these four languages to help it convert to modern software engineering
practices, rather than sticking with FORTRAN, COBOL, C, etc. Trying to
engineer software with languages invented 20-30 years ago makes about as
much sense as trying to build skyscrapers with a stone axe.
-- 
**************** JIM SHOWALTER, jls@netcom.com, (408) 243-0630 ****************
*Proven solutions to software problems. Consulting and training on all aspects*
*of software development. Management/process/methodology. Architecture/design/*
*reuse. Quality/productivity. Risk reduction. EFFECTIVE OO usage. Ada/C++.    *