[MonoDevelop] Doc comments

C.J. Collier cjcollier at colliertech.org
Wed Jan 25 17:04:23 EST 2006

Hash: SHA1


Are you familiar with monodocer ?  Is it what you're looking for?



Jacob Ilsø Christensen wrote:
> Hi.
> I have looked a bit at fixing this issue, but it seems that the C#
> parser does not support doc comments at the moment. Is this true or
>  am I missing something. I looked in the cs.ATG file. On another
> note, how do we switch to supporting .NET 2.0. Can this parser be
> autogenerated from some mono code?
> /Jacob
> On 12/9/05, *Atsushi Eno* <atsushi at ximian.com
> <mailto:atsushi at ximian.com>> wrote:
> Hi,
> John Luke wrote:
>> Atsushi Eno wrote:
>>> You might want to reuse some code in cs2ecma.cs in monodoc,
> if you
>>> are really interested in implementing it (though I dislike C#
>>> doc comments as a kind of translator dude, I remember I wrote
> such code).
>> I know I'm jumping off topic, but why does this present a
> problem for
>> translators?
> There is simply no built in support for localization in C# doc
> comments and IF we include those translations in the sources as
> well, the lengthy documentation will mess you. And if you split
> translation documents out from the source, it won't reflect
> on-the-fly documentations for you.
> When it comes to monodoc, we can at least theoretically use
> non-"en" documentations as its basis (and it would be pretty simple
> to localize).
>> Another possibility is to get the inline doc information with the
>>  monodevelop parser.
> Yes. Am not familiar with MD sources so I might misunderstand, but
> since monodevelop has its own parser, so it would make much sense
> to have its own doc comment support.
> Atsushi Eno

- --
<cjcollier at colliertech.org>
+1 206 226 5809
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org


More information about the Monodevelop-list mailing list