[Mono-devel-list] Weird results from corcompare

Atsushi Eno atsushi at ximian.com
Fri Jun 18 20:19:29 EDT 2004


Am seeing weird things in corcompare results.

We have XmlDocument.NodeChanged event as such. No attributes defined:

	public event XmlNodeChangedEventHandler NodeChanged;

And it results in like this by corcompare (mono-api-info):

	<event name="NodeChanged" attrib="1536"
		eventtype="System.Xml.XmlNodeChangedEventHandler" />

while MS.NET returns:

	<event name="NodeChanged" attrib="0"
		eventtype="System.Xml.XmlNodeChangedEventHandler" />

I wonder if I need special trick to avoid those differences. (I compiled
System.Xml.dll with mcs).

One more thing (off-topic), we have System.Xml.XPath.XPathResultType
enumeration as such:

		Number = 0,
		String = 1,
		Boolean = 2,
		NodeSet = 3,
		Navigator = 4,
		Any = 5,
		Error = 6,

However, corcompare result requires us to change it like

		String = 1,
		Navigator = 1,

I will never "fix" this problem, unless any important reason to change.
Our XSLT engine uses .Navigator. We should not lose the whole
result-tree-fragment support just to conform to MS mistake.

Atsushi Eno

More information about the Mono-devel-list mailing list