Re: Why properties cannot be used as ref or out arguments

Dean Cleaver <[email protected]> Mon, 10 Mar 2008 23:45:31 +1300
Newsgroups gmane.comp.windows.devel.dotnet.clr
Message-ID <4543A775711185429E59B18055D4167423225E@sxslakl004.xceptionsoftware.com>
Problem is my variables are of differing types... not that I can tell
from your code snippet, but It seems they are expected to be the same
type?

-----Original Message-----
From: Discussion of development on the .NET platform using any managed
language [mailto:[email protected]] On Behalf Of Jon Skeet
Sent: Monday, 10 March 2008 22:56
To: [email protected]
Subject: Re: [DOTNET-CLR] Why properties cannot be used as ref or out
arguments

Dean Cleaver wrote:
> Yeah - getting my head around it now. Sadly, it's not VB I wanted it
> for.
>
> Is a shame- looks like I will have to declare 2 variables, pass them
in,
> and then analyse the returned responses to achieve what I want - takes
> the "ideal" 1 line call to about 7 or 8 at least - was trying to
> encapsulate a call, but it might not be feasible.

Sounds like an argument for tuple return types:

(FirstNameProperty, LastNameProperty) =3D SplitName(FullName);

:)

(Can you tell I've been learning Erlang? ;)

I've no idea how much work is required either in terms of language
design or CLR modifications to support this - I suspect it would be
feasible in "language only" but a lot more elegant with CLR integration.

Jon

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
This list is hosted by DevelopMentor(r)  http://www.develop.com

View archives and manage your subscription(s) at
http://discuss.develop.com

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
This list is hosted by DevelopMentor=AE  http://www.develop.com

View archives and manage your subscription(s) at http://discuss.develop.com