Nothing like a good example to set everyone straight... This "feature" no longer looks to be "hard" it now looks impossible!!
~joe -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jonathan Johnson Sent: Wednesday, August 23, 2006 1:25 PM To: REALbasic NUG Subject: Re: methods with different return types > 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>
