On Mon, 2006-07-24 at 14:22 +0200, Jb Evain wrote:
> Hey,
>
> Matej Urbas wrote:
> > I figured that they are 'compatible'. But there is one slight
> > difference. You are missing a 'n' in DefaultConstructorConstraint :D
>
> This is fixed in SVN.
On Mon, 2006-07-24 at 11:20 +0200, Jb Evain wrote:
> > 3. Oh, and to what extent is Mono.Cecil compatible with
> > System.Reflection? E.g.: are the Mono.Cecil.GenericParamAttributes and
> > System.Reflection.GenericParameterAttributes cast safe? - I mean, can
> > they be cast from one-another an
Hey!
On Mon, 2006-07-24 at 12:33 +0200, Jb Evain wrote:
> There is a simpler way. The inheritance tree is like this:
>
> - TypeReference
>- TypeSpecification
> - ArrayType
> - PointerType
> - ReferenceType
> - FunctionPointerType
> - GenericInstanceType
> - ModTy
On Mon, 2006-07-24 at 11:20 +0200, Jb Evain wrote:
> You can find constructed generic types (GenericInstanceType) and
> constructed generic methods (GenericInstanceMethod).
>
> They both implement IGenericInstance wich provides a collection of
> argument. An argument is a TypeReference, which is
On Sun, 2006-07-23 at 12:32 -0400, Miguel de Icaza wrote:
> The complete specification for this syntax is available on the ECMA 335
> specification:
>
> http://www.ecma-international.org/publications/standards/Ecma-334.htm
>
Thank you.
I have also found the answer to the second question: it is
On Sat, 2006-07-22 at 16:29 +0200, Alejandro Serrano wrote:
>
> Decorating generic types with a grave (`) and the
> number of generic parameters is the way the CLI
> represents generic types, so we could have:
>
> Func => Func`1
> Func => Func`2
>
> because the runtime imposes that all types mus
Hi
I'm working on code completion (generics support) in MonoDevelop and I'm
making extensive use of Mono.Cecil.
I have a few questions about the way Mono.Cecil decorates full names of
generic types:
1. All generic types have such a string appended to their full name:
"`#" - where # represents
