Robert DaSilva wrote: > This happen when you overRIDE an overLOADed function, but you don't > overRIDE all of the overLOADs. That sounds like something very easy to detect at compile-time. Are there practical situations with large ovrload sets where this would be a real pain for the programmer?