But that particular case does NOT require overloading.
I'd call that a bug in BlitzMax.
For functions (unlike what happens with methods), which function to call is entirely resolved at compile-time, so we should be able to have two homonym functions in a base type and a derived type, even if they have different parameters. They're in different namespaces, and no dynamic dispatch is involved, so there's no problem.
Much like you can currently have 2 homonym fields in the base type and derived type.
So I'd suggest to post a bug report for that. I for one would love to see it fixed.
I'd call that a bug in BlitzMax.
For functions (unlike what happens with methods), which function to call is entirely resolved at compile-time, so we should be able to have two homonym functions in a base type and a derived type, even if they have different parameters. They're in different namespaces, and no dynamic dispatch is involved, so there's no problem.
Much like you can currently have 2 homonym fields in the base type and derived type.
So I'd suggest to post a bug report for that. I for one would love to see it fixed.