[Mono-list] Some more class library compliance issues
Tue, 12 Mar 2002 11:08:07 -0800
Good catch. The reason for this is twofold:
1) my bad. I didn't realize fields & events could have the same names
and the field for the event was hiding the event itself.
2) the XmlNodeChangedEventHandler 'Node*' fields in corlib's XmlDocument
are actually called 'onNode*Delegate' in mscorlib. It doesn't matter for
corcompare because they're private (so not shown), but this may be why
the NDoc stuff was acting weird.
From: Jason Diamond [mailto:email@example.com]
Sent: Tuesday, March 12, 2002 7:55 AM
Subject: Re: [Mono-list] Some more class library compliance issues
> If you see any false negatives, please let me know.
> -- System.Xml.dll --
> WARNING: System.Xml.XmlDocument.NodeInserting is: 'Field' [should be:
> WARNING: System.Xml.XmlDocument.NodeInserted is: 'Field' [should be:
> WARNING: System.Xml.XmlDocument.NodeRemoving is: 'Field' [should be:
> WARNING: System.Xml.XmlDocument.NodeRemoved is: 'Field' [should be:
> WARNING: System.Xml.XmlDocument.NodeChanging is: 'Field' [should be:
> WARNING: System.Xml.XmlDocument.NodeChanged is: 'Field' [should be:
These actually are events. If I recall correctly, NDoc had to do hack
around the fact that events look like fields when you're using
Mono-list maillist - Monofirstname.lastname@example.org