an "overloaded subroutine" example

[James D Jarvis]

That's all no overloading, as overloading is the ability to define subs or functions with the same NAME but DIFFERENT arguments or results and the compiler picks the right routine at compile time based on the given arguments.

That's not possible in QB64, as the compiler would immediately complain about duplicate names when you try to use the same sub/function name for more than one routine.

All you guys did, and as also I do in the GuiTools Framework with my TagString API, is to make ONE smart routine which is able to handle a bunch of different arguments given as a delimited string. That works, but that is NO overloading.

I hear you. What's that called however? Need a better term for it than "ONE smart routine which is able to handle a bunch of different arguments".  I did put it in " "  because I know I'm fibbing a little.