Re: Parameter metadata

From: Brian Tyler (brianmtyler_at_yahoo.com)
Date: 04/30/04 

Date: Fri, 30 Apr 2004 15:59:42 -0500

The difference is for the automatic marshaller (PInvoke, COM Interop, etc.).
The signature contains all that is needed by the CLR to make method calls
(whether it is by ref or not). I assume it is split off from the signature
in order to save space (only a small number of methods use the marshaller).

"Michael Sparks" <michael.sparks@remove.this.sbcglobal.net> wrote in message
news:fxZjc.4171$266.2618@newssvr23.news.prodigy.com...
> The metadata for parameters is split between the parameter's signature and
> the param table.
> I noticed that the in/out specifiers get stored in the param table as
> opposed to the signature.
> Is there a reason for this?
> I'm sure that I'm just missing something, but I can't seem to think up any
> scenario where you'd want two methods to match on signature, but then be
> uncallable due to an in/out conflict.
>
> Thanks,
> Mike
>
>

Relevant Pages

  • Re: Parameter metadata
    ... > The difference is for the automatic marshaller (PInvoke, COM Interop, ... > The signature contains all that is needed by the CLR to make method calls ...
    (microsoft.public.dotnet.framework.clr)
  • [Patch] [LTC] ECC <= 112
    ... Please note that these short hash codes are NOT secure. ... To keep signature size small, ... @param out The destination for the signature ... goto LBL_ERR; ...
    (sci.crypt)
  • Re: Parameter metadata
    ... > the param table. ... > opposed to the signature. ... ref parameters, you have a BYREF signature element (which indicates that ...
    (microsoft.public.dotnet.framework.clr)
  • Parameter metadata
    ... The metadata for parameters is split between the parameter's signature and ... I noticed that the in/out specifiers get stored in the param table as ... opposed to the signature. ...
    (microsoft.public.dotnet.framework.clr)