| Even if the original design is ok, when someone else comes along and
| has to fix something in code using templates.
If templates make the code *simpler*--clearer, more maintainable,
etc.--fine. If not, then they shouldn't be there, and you're seeing
an incompetent programmer at work.
I had the pleasure (I'll let you interpret that however you choose,
though it was quite interesting!) of doing a few months of C++ again
recently. The guy I was working was very smart and highly competent
technically but did have rather a tendency to overengineer and come
up with needlessly complex and generic designs, based heavily on
templates. The end result was that some simple changes that I would
have expected to take about half an hour in Java ended up taking the
two of us more than a week. I didn't like templates before; I like
them even less now. I'm afraid experiences like that (and others)
have made me very wary of generics in Java, even if they're not
exactly the same as C++ templates.
-Rolf
--
Rolf Howarth, Square Box Systems Ltd, Stratford-upon-Avon UK.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
