Hello, > > But in this world of imperfections we need to support all of that source > > code that has been produced with inline documentation with the Microsoft > > format. > > And that's where I want to push mcsdoc. Not only it will be able > generate the XML file as with the "/doc" switch, but also has a > doc-engine where I intend to provide the full features as of the > javadoc's Doclet and Taglet framework.
Thanks for the explanation. Now the question is: how is this different from the /doc switch that we are adding today to mcs? Would it be possible to instead just use the output produced by mcs /doc? My concern is that I do not want to add code to the compiler without having a good reason for having it there. What are docklet and taglets? > However, you are (read: anybody is) open to add another provider to > convert them to ECMA XML docs. Yeah, but it takes time ;-) So the issue is: would it not be best to focus our efforts on a single solution? For example, adding chm support to Monodoc would be a great addition. Miguel _______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
