Pet peeves

Post #5,469 by wharris2 8/16/01 4:38:54 PM Reply	Pet peeves Operator overloading in C++. Idiots writing C++ code that doesn't properly take care of memory (you know, blah = new blahclass without delete blah) Undocumented sources - not the source itself (although people who write code without a single comment are hurting themselves and others), but where the code came from, if anywhere. Combine that with making your own code unattributable by not providing a minimal header. Re-inventing the wheel, when there are several types of wheels out there to pick from. OK, OK, it isn't always possible to reuse code and sometimes actually harmful, but it would be just plain stupid to write a string class from scratch in C++. Even if you don't want the templatized standard library string, there are many implementations to choose from. Most of these are C++ examples, because I've been working on a library that exhibits many of these features. The first time I encountered setjmp() was in an Amiga program ported from Unix. "Hmm, what's setjmp()?" I said, pulling up the man page. I read the man page. "GASP GLARGGGPPPHHTT!!! ARGHJKLKJ#@%!^&^U!" I exclaimed, and rolled my chair over backwards as I fainted.
Post #5,471 by tuberculosis 8/16/01 5:09:43 PM Reply	Well, if you just want to list those I'll wrap the whole thing up in "People who use C++ to write application code". Done. setjump is a perfectly good routine. Its used for exception handling in Objective C and it works OK. It just happens to break what C++ crowd is pleased to call their "runtime architecture".
Post #5,473 by wharris2 8/16/01 5:18:02 PM Reply	I don't care what the C++ crowd calls it Setjmp is a miserable solution to a built-in language problem - this is from a C perspective. C programs also use it for exception handling, though probably much less coherently than Objective C. I don't think I've ever seen a C++ program use it. The first time I encountered setjmp() was in an Amiga program ported from Unix. "Hmm, what's setjmp()?" I said, pulling up the man page. I read the man page. "GASP GLARGGGPPPHHTT!!! ARGHJKLKJ#@%!^&^U!" I exclaimed, and rolled my chair over backwards as I fainted.
Post #5,659 by deSitter 8/17/01 3:10:16 PM Reply	Argh! Operator overloading in C++ is one of the few things about it that's any good. It's very useful in numerical work.
Post #5,672 by tuberculosis 8/17/01 4:37:23 PM Reply	Well hang in there because its coming to Java I think. Although, if they make the same compromises they made with the Generic extensions (templates), its going to be horribly inefficient for numerics work.
Post #5,716 by wharris2 8/17/01 10:31:56 PM Reply	Two uses Complex numbers and strings. Can't think of any other reasonable uses. To have a language specification that builds an item on two rare uses is crazy. French Zombies are zapping me with lasers!

Welcome to IWETHEY!