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 [EMAIL PROTECTED] http://bugzilla.ximian.com/show_bug.cgi?id=79117 --- shadow/79117 2006-08-23 12:30:40.000000000 -0400 +++ shadow/79117.tmp.21009 2006-08-23 14:36:07.000000000 -0400 @@ -257,6 +257,20 @@ However, after looking close at the MS docs I noticed that there was indeed a difference between name mangling for Unicode and Ansi which matches the Mono behavior .... For Ansi, it should first search for the unmangled name, while for Unicode it should first probe for the mangled name ... Sorry for the bogus report ... + +------- Additional Comments From [EMAIL PROTECTED] 2006-08-23 14:36 ------- +> Robert, I thought the mangling issue was there when exactspelling was +> false (not true). You probably just made a typo, as the results you +> get match those you get when ExactSpelling is false. With +> ExactSpelling set to true you would have gotten an +> EntryPointNotFoundException in all three cases (on both Mono and +> MS.NET). + +Oops, of course I changed the signature (*A, *W) in the C# code. +Otherwise "ExactSpelling = true" won't make sense. + +Indeed, "ExactSpelling = false" behaves like you wrote. + _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
