[ndoc-devel] Re: [Mono-devel-list] monodoc provider for doc comments

[Donald Kackman]

Take a look at RFE# 918014.
(http://sourceforge.net/tracker/index.php?func=detail&aid=918014&group_id=36
057&atid=416081)

It's not directly related to this topic but from the looks of the initial
comment, the submitter had a MC++ /doc compiler working (or in the works).

It looks to me like they use a C macro (probably a combination of __FILE__
and __LINE__) along with a custom attribute in the C++ code.

I dropped the guy a note wondering if he'd be willing to share, but he never
got back to me.

It looks like an interesting approach.

don

> -----Original Message-----
> From: ndoc-devel-admin at lists.sourceforge.net [mailto:ndoc-devel-
> admin at lists.sourceforge.net] On Behalf Of Ferdinand Prantl
> Sent: Thursday, April 08, 2004 4:25 AM
> To: Donald Kackman; 'Gert Driesen'; 'Joshua Tauberer'
> Cc: 'Paul Thomas'; Mono-devel-list at lists.ximian.com; ndoc-
> devel at lists.sourceforge.net
> Subject: RE: [ndoc-devel] Re: [Mono-devel-list] monodoc provider for doc
> comments
> 
> Hi,
> 
> > From: Donald Kackman [mailto:dkackman_2000 at yahoo.com]
> >
> > I think having a set of companion projects to NDoc, to
> > generate /doc comments for non-standard scenarios would be
> > extremely useful.
> >
> > I for one could use a MC++ documenter.
> 
> I have knocked up support for more .NET languages in the MSDN documenter
> and
> its XSLs and JSs, with the same javascript-switching as there is in MSDN.
> Currently in my modification I have C#, MC++, VB and JS switchable. I did
> also some more modifications and now I am integrating it into the beta of
> 1.3 to be able to submit it as a contribution. Output of mc++ works so.
> 
> The problem with input for MC++ is the lack of generator for the similar
> XML
> as csc.exe does from C# sources. CL.EXE can do from MC++ sources it from
> VS
> 2005, but for the new syntax only, as I taste bitterly now...
> 
> Now I am considering (and trying) the three possiblities:
> 
> 1) to modify doxygen to accept MC++ sources and generate a better support
> for the .NET full names in the ouput XML + to create a XSL doxy2dotnet
> 2) try to achieve the generation of the NDoc/.NET compatible XML by
> utilizing the openc++ parser, probably together with reflecting to the
> existing assembly or not (it could be useful to have the without)
> 3) let everyhing on cl.exe from the upcoming VS (well, not so good for the
> OSS world...)
> 
> Evaluation of the 1) shows, that it is pretty complex and rather misusing
> of
> the tool but I will see. The second one I am going to like, let's see
> after
> the weekend.
> 
> Ferda
> 
> > don
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux Tutorials
> Free Linux tutorial presented by Daniel Robbins, President and CEO of
> GenToo technologies. Learn everything from fundamentals to system
> administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> _______________________________________________
> ndoc-devel mailing list
> ndoc-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ndoc-devel