Bug 316486 (MONO69676) - monodoc treats nested classes oddly
Summary: monodoc treats nested classes oddly
Status: RESOLVED FIXED
Alias: MONO69676
Product: Mono: Doctools
Classification: Mono
Component: Core (show other bugs)
Version: 1.0
Hardware: Other Other
: P3 - Medium : Normal
Target Milestone: ---
Assignee: Ben Maurer
QA Contact: Mono Bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-11-18 22:43 UTC by Dan Winship
Modified: 2007-09-15 21:24 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Wiest 2007-09-15 18:59:12 UTC


---- Reported by danw@gnome.org 2004-11-18 15:43:28 MST ----

If you have

namespace Foo {
    class One { ... }
    class Two {
       class Nested { ... }
    }
}

monodoc will generate/expect doc files named

   Foo/One.xml
   Foo/Two.xml
   Foo/Nested.xml

But if you then add either "Foo.Nested" or "Foo.One.Nested" to
the namespace, you'll lose, because there'll be a naming conflict.



---- Additional Comments From sebastien@ximian.com 2004-11-18 22:26:55 MST ----

#60826 (public nested class are listed in the documentation even if
the parent class isn't public) is another issue with nested class.



---- Additional Comments From miguel@ximian.com 2004-11-29 22:35:44 MST ----

Ben, can you look at these two?



---- Additional Comments From bmaurer@users.sf.net 2004-11-30 19:53:42 MST ----

Fixed, but we will need someone to update the docs we have (the
updater will do it, but it needs some svn magic)


Unknown operating system unknown. Setting to default OS "Other".