DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:date:from:to:cc:subject:message-id:mime-version:content-type:content-disposition:user-agent;
        b=JEP/0czs5ioQjojc1Z9MdElWVfSZkgXp0FeViQJD8D+faaq3DbLyV2bmsm1FmYDTh2ranetrDQFjOFn+fvKRKDrPQzInPGMsOMi5FsvdcMbHZnalbhaflmGTDBUuxey3D4iL4xS9MdwmFJSi6ozYRwdVbAsvfmLaJzCQchiXB+0=
Date: Tue, 8 Nov 2005 21:35:11 +0300
From: Alexey Dobriyan <adobriyan@gmail.com>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch 1/4] DocBook: allow to mark structure members private
Message-ID: <20051108183511.GA12043@mipter.zuzino.mipt.ru>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.8i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1071
Lines: 37

Randy Dunlap wrote:
> Ahoy.  Excellent.  Compare my personal todo list item:

> 35.for kernel-doc: make some fields :private: so that a description is not
>     expected for them.

Aha! A kernel-doc hacker! Randy, by any chance, do you have "support for
nested structs" in your TODO? And if yes, what's the status? I have
parsing with the following syntax:

 # /**
 #  * struct my_struct - short description
 #  * @a: first member
 #  * @b: second member
+#  * @c: nested struct
+#  * @c.p: first member of nested struct
+#  * @c.q: second member of nested struct
 #  * 
 #  * Longer description
 #  */
 # struct my_struct {
 #     int a;
 #     int b;
+#     struct her_struct {
+#         char **p;
+#         short q;
+#     } c;
 # };

But properly nested displaying is in pretty much nil state since .. uh
crap.. summer.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/