Re: C# and VB.Net?
- From: "Michael S" <no@xxxxxxxx>
- Date: Tue, 13 Dec 2005 19:15:08 +0100
"Jon Skeet [C# MVP]" <skeet@xxxxxxxxx> wrote in message
news:MPG.1e0912251fa4e03b98cb31@xxxxxxxxxxxxxxxxxxxxxxx
> Michael S <no@xxxxxxxx> wrote:
>
> <snip>
>
>> And the latter group typically don't adopt OO-principles. They still view
>> a
>> class as some module you just put code and som Dims in, they keep on
>> concatinating strings, declaring their arrays, and don't get why an
>> ArrayList or a StringBuilder could ever be useful. The think in terms of
>> variables and don't get the 'reference on stack, object on heap' model
>> and
>> can't undestand why passing a huge array to a method would be the bad
>> thing.
>
> I don't understand why passing a huge array to a method would be a bad
> thing either though. Arrays are reference types - you're not passing a
> load of data. What kind of problem are you thinking of?
>
> --
> Jon Skeet - <skeet@xxxxxxxxx>
> http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
> If replying to the group, please do not mail me too
My Bad!
I ment huge structs, in loops.
I re-wrote that part a couple of times and wanted to mention value/reference
and also boxing/unboxing. It was not any good, so I erased stuff to get rid
of complex examples, and I guess array just got there and I went along
continuing writing...
Thanks Jon, for making sure people get that passing arrays is not bad.
- Michael S
.
- References:
- C# and VB.Net?
- From: Mantorok
- Re: C# and VB.Net?
- From: Michael S
- Re: C# and VB.Net?
- From: Jon Skeet [C# MVP]
- C# and VB.Net?
- Prev by Date: Re: C# and VB.Net?
- Next by Date: Re: Problem passing in reference of calling class into DLL
- Previous by thread: Re: C# and VB.Net?
- Next by thread: Re: C# and VB.Net?
- Index(es):
Relevant Pages
|