[Mono-bugs] [Bug 60826][Cos] New - public nested class are listed in the documentation even if the parent class isn't public

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Mon, 28 Jun 2004 10:20:56 -0400 (EDT)


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 sebastien@ximian.com.

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

--- shadow/60826	2004-06-28 10:20:56.000000000 -0400
+++ shadow/60826.tmp.15320	2004-06-28 10:20:56.000000000 -0400
@@ -0,0 +1,51 @@
+Bug#: 60826
+Product: Mono: Doctools
+Version: unspecified
+OS: All
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Cosmetic
+Component: Core
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: sebastien@ximian.com               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: public nested class are listed in the documentation even if the parent class isn't public
+
+Description of Problem:
+Public nested class are listed in the documentation even if the parent
+class isn't public.
+
+
+Steps to reproduce the problem:
+1. Generate documentation for System.Security
+2. Look for classes ElementNames, AttribtueNames... in monodoc
+
+
+Actual Results:
+public class nested in internal class are visible in monodoc (but aren't
+visible in corcompare).
+
+
+Expected Results:
+public nested class aren't accessible so they shouldn't be part of the
+documentation.
+
+
+How often does this happen? 
+Always
+
+
+Additional Information:
+from mcs/class/System.Security/System.Security.Cryptography.Xml/XmlSignature.cs
+
+namespace System.Security.Cryptography.Xml {
+
+	// following the design of WSE
+	internal class XmlSignature {
+
+		public class ElementNames {