Re: Cocoa Newbie
Re: Cocoa Newbie
- Subject: Re: Cocoa Newbie
- From: Rainer Brockerhoff <email@hidden>
- Date: Tue, 9 Oct 2001 11:21:05 -0300
>
From: "Erik M. Buck" <email@hidden>
>
Date: Tue, 9 Oct 2001 00:20:32 -0500
>
>
People interested in the rationale behind C++ should read Stroustrup's
>
"Design and Evolution of C++". I call it the "apology". Even a casual
>
reader will realize the Stroustrup had no idea what he was doing and just
>
stumbled into the current quagmire. His goals were counter to good OO
>
practices.
>
...
>
Ah... remember PL1 ?
There's worse than that, remember Algol-68? Van Wijngaarden's book and the "Offical Algol 68 Report" are treasured documents which I reread - or at least try to - every time I'm tempted to ask for new language features (for any language).
Brrrhh.
>
...Mr.
>
Stroustrup has summarized many complaints and explained that C++ is not well
>
suited for use with many applications to which it has been applied. I
>
agree. No language is best suited to solving all problems. I just haven't
>
found any problem for which C++ is best suited in spite of being involved
>
with many projects including hundreds of thousands of lines of C++. For
>
extremely static systems, Eiffel is usually preferred. For extremely
>
dynamic systems, Smalltalk, Lisp, and numerous script languages are usually
>
preferred. For fairly dynamic systems composed of reusable components that
>
need to interoperate with C, Objective-C is sometimes a great choice. Logic
>
programming is interesting with Prolog. Text processing is interesting with
>
Snobal, perl, and others. There are nice expert system languages, and
>
neural net languages. Ada has some interesting qualities, but I usually
>
prefer Eiffel.
Well, these are all mainframe and desktop applications for which those alternatives are available. For several years I've done quite successful applications in C++ for palmtop and embedded systems, and even for the old Mac OS with PowerPlant.
But, of course, without touching templates or STL, and I think I used multiple inheritance only for PowerPlant where it's unavoidable. I think using this C++ subset, as a more flexible C, worked for me very well.
--
Rainer Brockerhoff <email@hidden>
Belo Horizonte, Brazil
"Originality is the art of concealing your sources."
http://www.brockerhoff.net/ (updated Oct. 2001)