[Mono-list] Re: [Mono-hackers-list] Re: Patch for mcs
Gaurav Vaish <email@example.com>
Wed, 3 Nov 2004 19:57:13 +0530
> Oh, np, I did't :)
Great to note that. :-)
> According to the C# /** ... */ rule, heading '*' characters in
> each comment line must be removed when (and only when) it
> starts with spaces and '*'. It is C# specific rule. (well, mcs
> is C# compiler ;-)
Ok. Agree to it. But can I assume that you'd be doing this in
cs-tokenizer.cs? If so, don't worry... I'll take care of it for my
> before a get accessor is invalid (CS1587 warning will be raised):
Fully accepted and acknowledged.
> So, I guess you cannot expect any arbitrary documentation grammar
> to conform to C# documentation/tokenization rules.
Ditto as my previous comment.
> Please clarify; do you actually have working functionality? If not,
> why do you need to commit your changes to CVS before you finish
> the actual document generation functionality?
Ok... the status right now is that my tool cannot generate comments
as of now. It can read comments (by patching cs-parser.jay,
cs-tokenizer.cs, decl.cs etc), understand some of them but cannot
generate HTML files right now.
Two parts to it: One the changes needed in mcs to expose
raw-comments. Second, generating documentation (HTML, chm or blah).
The changes that I made to mcs belonged to mcs-1.1 (.Net 1.1) and now
C# language itself has changed a lot with partial classes etc.
It gave me a tough time patching new mcs-2.0 for my mcsdoc.
Tomorrow, I may have another mcs-3.0 and all that pain. So, I just
needed raw doc/comments.