> It is maddening to see all those circular references in header files.
I guess I should have added "a good framework..." :) Circular references
are evil...
> And then to see non error checking construction of objects willy nilly
> thoughout the code. God what the hell was I thinking when I liked
> that language!
Well, I wouldn't blame that on C++...I've seen:
pFoo = malloc(iFooSize);
if (!pFoo)
{
// error message
}
multiple times...tell me how THAT code is going to work! :)
What DOES get ugly is some of the errors your compiler can generate if
you're using templates...especially the STL...but there are some pages out
there on the web that illustrate filtering out the unncessary bits (don't
remember them off the top of my head).
> After this punishment I am now solidly of the opinion that if the
> problem is too complex to code in C with a few structures and memory
> handles then you should break it down into simpler terms, rather than
> abstract it into C++.
For my simple mind, using OO and C++ makes it much easier for me to
understand the problem domain...it's easy to write ugly C++ (everything's
public, and everybody's my friend!), but it's just as easy to write ugly C
(who needs objects when you can cast void * to be anything you want? :)
Now THAT'S polymorphism!)
Craig
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
