[Mono-list] More documentation info
A Rafael D Teixeira
Wed, 13 Mar 2002 12:30:22 -0300
>From: "Jason Diamond" <firstname.lastname@example.org>
>To: <email@example.com>, <firstname.lastname@example.org>
>Subject: Re: [Mono-list] More documentation info
>Date: Wed, 13 Mar 2002 06:58:13 -0800
> > Lines to extract will have to be marked by the "apostrophe followed by
> > underscore" character sequence as the first non-whitespace content in
> > line.
>Just out of curiosity, why did you choose "apostrophe followed by an
>There's a sample macro that comes with VS.NET called VBDocComments. It adds
>XML comments to the current method automatically by using the IDE to parse
>the code so that it can add the appropriate param names, etc. It uses three
>apostrophes as the prefix. These comments can't be extracted by vbc yet but
>just I assumed that the three apostrophes prefix was going to be used by
>in the future since that would be consistent with the three slashes csc
>But I don't write in VB so don't really care. :-)
I think 3 apostrophes would be error-prone, because the IDE has toolbar
buttons to comment/uncomment blocks and you can by mistake or just for some
temporary reason comment a block containing an already commented block (a
very common pattern in my dayly use I can say of VB and VB.NET).
If done twice you would end with unintended code/comments extracted as
BTW, If you block comment some code with documentation lines those will not
be extracted, but that will happen with my solution, too, and is in truth
the right thing to happen.
The reason for all that trouble is that VB does not have something like /*
*/, so that block commenting is done by line commenting each line in the
block. An VB developers are used to it.
That is why I proposed an very unlikely combination of the line-coment
marker (the apostrophe) with the line-continuation marker (the underscore).
Oh, yes, VB syntax is line oriented...
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp.