On Aug 23, 2006, at 1:15 PM, Daniel Stenning wrote:
On 23/8/06 17:35, "Mars Saxman" <[EMAIL PROTECTED]> wrote:
Overloading is hard to use precisely when it causes ambiguity, and
obscures
rather
than clarifying programmer intent.
Not sure what that means exactly -but in any case surely isnt it for
US
users to decide when such use would cause ambiguity?
This situation right here:
Sub Foo( i as Integer )
Sub Foo( s as String )
Class Bar
GetValue() As String
GetValue() as Integer
End Class
Foo( myBar.GetValue() )
In the current implementation, this can't be ambiguous. However, if
overloaded return types were allowed, this would be ambiguous.
HTH,
Jon
--
Jonathan Johnson
[EMAIL PROTECTED]
REAL Software, Inc.
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
