[Mono-bugs] [Bug 80344][Nor] Changed - GetMembers behaviour does not match MS with BindingFlags.FlattenHierarchy

[bugzilla-daemon at bugzilla.ximian.com]

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 robertj at gmx.net.

http://bugzilla.ximian.com/show_bug.cgi?id=80344

--- shadow/80344	2006-12-22 12:42:03.000000000 -0500
+++ shadow/80344.tmp.21849	2006-12-23 20:02:30.000000000 -0500
@@ -2,21 +2,20 @@
 Product: Mono: Class Libraries
 Version: 1.0
 OS: other
 OS Details: 
 Status: NEW   
 Resolution: 
-Severity: 
+Severity: Unknown
 Priority: Normal
 Component: CORLIB
 AssignedTo: mono-bugs at ximian.com                            
 ReportedBy: rolfkvinge at ya.com               
 QAContact: mono-bugs at ximian.com
 TargetMilestone: ---
 URL: 
-Cc: 
 Summary: GetMembers behaviour does not match MS with BindingFlags.FlattenHierarchy
 
 The following code prints different output on MS and Mono.
 
 using System;
 using System.Reflection;
@@ -48,6 +47,17 @@
 Output on MS:
 Property System.Windows.Forms.Form:ClientSize
 
 Output on Mono (both v1.1 and 2.0 profile):
 Property System.Windows.Forms.Form:ClientSize
 Property System.Windows.Forms.Control:ClientSize
+
+------- Additional Comments From robertj at gmx.net  2006-12-23 20:02 -------
+This is unrelated to FlattenHierarchy, which is applied only to static
+members. Since you request Public | Instance, FlattenHierarchy
+has no effect.
+
+The real problem seems to be that MS.NET implies DeclaredOnly while
+Mono doesn't: if you change the flags to 
+Public | Instance | DeclaredOnly, the test case succeeds on both
+runtimes.
+