That's a good point. Of course, polymorphism works at the object level, essentially extending function overloading to types. The problem (or not, depending on your point of view) is that objects are only polymorphic within an inheritance hierarchy. Another problem is that creating derived classes is a lot of work (relatively speaking) and at least carries with it the potential of a performance hit. As I mentioned before, I think a lot of this has to with making life easier for the compiler writer, not the application programmer.
--- Gary Monger <[EMAIL PROTECTED]> wrote: > > I find it curious that as languages and applications move toward > higher > levels of abstraction, they still enforce strong typing. Meanwhile, > programmers overload functions and methods to reduce the headache it > causes. > > === Gregory Woodhouse <[EMAIL PROTECTED]> "Design quality doesn't ensure success, but design failure can ensure failure." --Kent Beck ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
