[Mono-bugs] [Bug 71300][Min] Changed -
TestGetConstructorNullElementType
bugzilla-daemon at bugzilla.ximian.com
bugzilla-daemon at bugzilla.ximian.com
Thu Jan 5 07:42:16 EST 2006
Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.
Changed by rharinath at novell.com.
http://bugzilla.ximian.com/show_bug.cgi?id=71300
--- shadow/71300 2006-01-02 16:44:05.000000000 -0500
+++ shadow/71300.tmp.22902 2006-01-05 07:42:16.000000000 -0500
@@ -1,13 +1,13 @@
Bug#: 71300
Product: Mono: Class Libraries
Version: unspecified
OS: unknown
OS Details:
-Status: RESOLVED
-Resolution: FIXED
+Status: REOPENED
+Resolution:
Severity: Unknown
Priority: Minor
Component: CORLIB
AssignedTo: sebastien at ximian.com
ReportedBy: miguel at ximian.com
QAContact: mono-bugs at ximian.com
@@ -114,6 +114,15 @@
have problem in Activator when we do not supply null as a parameter
(as we can't directly infer the type).
------- Additional Comments From sebastien at ximian.com 2006-01-02 16:44 -------
Fixed in SVN (r54982) with new unit tests for both Activator and Type
(r54983).
+
+------- Additional Comments From rharinath at novell.com 2006-01-05 07:42 -------
+Unfortunately, this doesn't seem to do the right thing. It's breaking
+System.Runtime.Remoting
+
+The reason: the parameter type is IDictionary, but the actual argument
+is Hashtable. System.Reflection.Binder does the right thing, but
+we're circumventing it by doing the less optimal FindBestCtor match.
+
More information about the mono-bugs
mailing list