* Overloaded functions:

These are tricky. The idea is nice, but there are several 'gotchas'. For example...

Function T( x:Float )
End Function

Function T( x:Double )
End Function

T 10 'what gets called? Float, 'coz it's 'closer' to Int? Double 'coz it's more precise? Error because there's no exact match?

...or...

Type T

Method M( x:Float )
Method M( x:Double )

End Type

Type D Extends T

Method M( x:String )
End Method

Method Q( x:Int )
M x 'what happens?
End Method

Method Q( x:Float )
M x 'And this? etc...
End Method

End Type

Yes, you can come up with rules for these situations, but in my experience there is no avoiding 'surprises' with overloaded functions whatever rules you pick. Blitz's 'relaxed' attitude to type conversions also complicates things.

@bruzard
oop ist NCHT fürn arsch .
zumindest dann nicht wenn du deinen code weitergeben willst oder fremden code einbinden willst.