Date: Tue, 8 Nov 2005 10:27:01 -0800 (PST)
From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Alexey Dobriyan <adobriyan@gmail.com>
cc: "Randy.Dunlap" <rdunlap@xenotime.net>, linux-kernel@vger.kernel.org
Subject: Re: [patch 1/4] DocBook: allow to mark structure members private
In-Reply-To: <20051108183511.GA12043@mipter.zuzino.mipt.ru>
Message-ID: <Pine.LNX.4.58.0511081025420.15288@shark.he.net>
References: <20051108183511.GA12043@mipter.zuzino.mipt.ru>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1272
Lines: 46

On Tue, 8 Nov 2005, Alexey Dobriyan wrote:

> 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:

Hi,
Nope, haven't seen that one yet.

>  # /**
>  #  * 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.

Is this something that used to work?  If so, when?

-- 
~Randy
-
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/