J
Jorgen Grahn
It strikes me as a common sense rule to avoid confusing callers.
But are people confused by function overloading?
I know some tools are, and I assume it's confusing to C programmers
.... but personally I don't assume functions have anything in common
just because part of the signature is the same.
One of which is all overloads have the same semantics. Can cite a
counterexample?
The smoke() example above is one -- even if it's a bit artificial.
In the standard library, I cannot easily. But it's the /standard
library/ -- it doesn't deal with a wide range of unrelated real-world
objects like application code would. And it's more polished.
/Jorgen