multiple @syntax

[Guido Draheim]

I do have currently the impression that your parsers prefer to use
multiple @syntax lines when adding multiple items. For the @category
I was using a comma-seperated list which was working out quite well
since the category section targets are not that long and apart form
one general category the extra categories are short.

So, what do you think, adding a comma-seperated list for your parsers,
and/or breaking the @cats into multiple lines in the (very rare)
occasions where there are multiple category attributions?

Next question, how about the "obsoletion" mark - we had that a few
days ago - the gnu ac-archive oes currently contains 16 macros with
my old style of "dnl obsoleted" attribution. Do we use "@obsoleted"
next (as is my preference), keep with the in-document syntax, or
add it to the list of @category attributions (adding up to the
main category)

Next question, how about an "experimental" mark - so these macros
can be displayed as secondary on the website - just add to the
@category listing? I might prefer another @experimental [hint]
notion here which has a freeform hint even that it is usually
pointing to the source - author or project most of the times.

Next question, how to handle extra @syntax lines - is it ensured
that they end up in the main documentation body? If so then I can
just start switching to whatever @experimental line being
obvious. Is the main documentation body required to occur in
one block or is it allowed to put extra @syntax lines anywhere
in the main documentation block?


cheers,
-- guido                  http://google.de/search?q=guidod
GCS/E/S/P C++/++++$ ULHS L++w- N++@ s+:a d(+-) r+@>+++ y++