On Jun 27, 2006, at 10:56 AM, MB Software Solutions wrote:
Or when you can add the same named function several times,
each with a different parameter signature! Compilers have no
problem with that!
"Overloading" is what you're describing, right? I liked doing that
in PL/SQL programming.
The point is that the compiler isn't telling you anything once you
overload it with various possible parameter signatures for a method.
As far as the compiler is concerned, what you passed is one of the
possibilities that it accepts, so it is happy, but meanwhile you are
executing code that is wrong. This is where there is a false sense of
security created by compile-time checking. As Bruce Eckel stated,
strong testing, not strong typing.
-- Ed Leafe
-- http://leafe.com
-- http://dabodev.com
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
