>>What I had in mind is the situation where, for example, http://beginnersbook.com/2013/03/polymorphism-in-java/ defines overloading of methods just as something you have to do in a typed language - a different version of a method for each applicable set of parameter types.
>
>Actually, that overloading pattern sometimes makes code clearer, as the parameter checking for different method signatures in vfp or JS will get hairy if many cases have to be considered and put the method length above the 2 screens I consider maximum. Breaking out core functionality with some addendum added to the function name is my typical refactoring scheme, and that will often mimic the pattern found in overloading patterns found in Java or C#.

Now VFP being written in c++, I wonder how many internal versions of the between() function does it contain?