g -
> >to
> > > ask my specific question.
> > >
> > > My question was (It may sound dumb!) :
> > > Why the value type instance was not boxed in the supplied code ?
> > >
> > > Regards,
> > > Girish Jain
> > >
> >
AIL PROTECTED]>
Reply-To: "Unmoderated discussion of advanced .NET topics."
<[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: [ADVANCED-DOTNET] Methods Calls on value types
Date: Thu, 25 Nov 2004 11:52:45 -0800
Because there's no reason to box it. All that's need
>
>
> - Original Message -
> From: "Shawn A. Van Ness" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Wednesday, November 24, 2004 1:46 AM
> Subject: Re: [ADVANCED-DOTNET] Methods Calls on value types
>
> > > IL_0002: ldloca.s
type instance was not boxed in the supplied code ?
Regards,
Girish Jain
- Original Message -
From: "Shawn A. Van Ness" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, November 24, 2004 1:46 AM
Subject: Re: [ADVANCED-DOTNET] Methods Calls on value types
> IL_0002: ldloca.s V_0 // Load local variable address on to
> the stack
Sounds like you understand, just fine. The CPU pushes the address of
the valuetype onto the stack, before making the function call. That's
a pointer, on the stack, *to* something else on the stack (but
slig
Hi All,
I am really confused as to how the instance method calls on the value types
are processed. My initial understanding was that since value types do not
have an object header associated with them as compared to reference types,
for all instance method calls on the value type the value type ins
