Re: 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) = 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

===================================
This list is hosted by DevelopMentor®  http://www.develop.com

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