>
>Oh well, another argument bites the dust :-}

If that is what it takes to learn something - why not


>What if the called method is in a different app domain ?

Dunno

>IAC, I'd stiil argue that using 'out' rather than 'ref' gives a clear indication to the caller of the behaviour of the method - i.e 'don't bother passing in an object because it don't mean nothin'

I agree - it's (1) clearer, and (2) I cannot recall passing something by ref that did not mean out

In the example of LotsOfDoubles, passing by ref actually outperforms passing by value
The call = copy 80 bytes, returning = copy 80 bytes onto the stack and copy 80 from the stack to the variable

LotsOfDoubles x = new LotsOfDoubles()

x = Method(x)

Guess that's why they say to keep the structs down to 16 bytes in size