Parameter metadata

From: Michael Sparks (michael.sparks_at_remove.this.sbcglobal.net)
Date: 04/29/04 

Date: Thu, 29 Apr 2004 02:13:31 GMT

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

  • [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)
  • Re: Parameter metadata
    ... The difference is for the automatic marshaller. ... The signature contains all that is needed by the CLR to make method calls ... > the param table. ...
    (microsoft.public.dotnet.framework.clr)
  • Re: MS Office 2007: Digital Signature does not protect Meta-Data
    ... Considering that the MetaData not protected by the signature contains ... Considering that the signature creation time is stored and protected by ... Betreff: MS Office 2007: Digital Signature does not protect Meta-Data ... Microsoft Office documents carry meta data information ...
    (Bugtraq)
  • Re: MS Office 2007: Digital Signature does not protect Meta-Data
    ... In fact the visual clue you gave for a signed document in Word 2007 ... All GUI edits to the MetaData are prohibited, ... Considering that the MetaData not protected by the signature contains ... Betreff: MS Office 2007: Digital Signature does not protect Meta-Data ...
    (Bugtraq)