🚀 go-pugleaf

In article <727841301.8123714@AppleLink.Apple.COM>,
ALANDAIL@AppleLink.Apple.COM (Personal Software, Alan Dail,PRT) wrote:
> 
> that C++ is better than C).  For example, anywhere you can use a ==, you can

You're right about this, and I haven't considered these issues.  The == vs.
= problem is a flaw that C++ inherits from C.  The same is true of switch
statements (where leaving out the break in each case is usually a mistake).

As someone mentioned, MPW C++ does warn you about some of these things, and
a better compiler would do a better job of warning you.

> like having various features clash when used together or having the wrong

I think there's a tradeoff here.  You could remove lots of features from
the language, but then there would be useful things that you couldn't do. 
For example, removing stack-based objects would simplify things
considerably, but stack-based objects are useful in many places.

One of the premises behind my MADA Conference talk on C++ is that if you
develop some "rules of thumb" (or "idioms" as James Coplien describes them)
for using C++ then it's much easier to deal with the language.

> defaults when using features (why isn't virtual the default?).  It's a shame

C++ was designed for maximum performance.

Larry Rosenstein
Taligent, Inc.

lsr@taligent.com