----- Original Message ----- From: "Miguel de Icaza" <[EMAIL PROTECTED]> To: "Gaurav Vaish" <[EMAIL PROTECTED]> Sent: Saturday, February 22, 2003 01:35 Subject: Re: [Mono-list] Re: CS-Doc
>
> Can you show an example of what seems to be the problem? I think that
> the property approach would effectively solve the issue that you
> mention.
--------------------------------
using System;
/// <summary>test_12</summary>
public interface test_12
{
/// <summary>Returns M1</summary>
int GetM1();
/// <summary>Gets or Sets P1</summary>
int /// <remarks>Nuisance</remarks>
P1 { get; set; }
}
--------------------------------
Output:
--------------------------------
[EMAIL PROTECTED] /cygdrive/f/gvaish/projects/csdoc/csdoc/src/csdoc
$ ./csdoc.exe ../tests/test_12.cs
Total keys: 3
GetM1:
/// <summary>Returns M1</summary>
test_12:
/// <summary>test_12</summary>
P1:
/// <summary>Gets or Sets P1</summary>
/// <remarks>Nuisance</remarks>
Compilation succeeded
--------------------------------
So, with the property "P1", I also collect "Nuisance", which I shouldn't
have.
Correction: Not the property, but the attributes, since they apply to
all for which I have to collect the docs - btw, can attributes be applied to
members, like:
--------------------------------
public class X
{
[MyAttribute("Something")]
private int memberX;
}
--------------------------------
if not, then I'll have to think something for members also. But I think
I will not to - since csdoc (in P.Net) has only one place - at
opt_attributes (Correct me if I am wrong).
Happy Hacking,
Gaurav
http://mastergaurav.virtualave.net/iitk
---------------------------------------
driver.cs
Description: Binary data
