[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mono-devel-list
Subject:    [Mono-dev] should we really use
From:       Atsushi Eno <atsushi () ximian ! com>
Date:       2007-05-31 9:34:57
Message-ID: 465E96C1.2060601 () ximian ! com
[Download RAW message or body]

Hello,

I just noticed that after replacing MonoTODO attributes with one
of those derived ones such as MonoNotSupported, they get *hidden*
from the class status pages. As a result, we're getting wrong MoMA
reports. Is it really intended, or should we avoid using those
derived attributes? (For example see
System.ComponentModel.MemberDescriptor.GetInvocationTarget() in
System.dll)

I don't think those attributes are ready to be used unless
corcompare stuff are changed to consider them.

Atsushi Eno
_______________________________________________
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic