This RFE points out that:
Currently <FUNCPROTOTYPE> does not allow both <PARAMDEF> and
<VARARG> in the same instance. This limitation is documented in
DocBook TDG in <FUNSYNOPSIS>. This makes it quite awkward to markup
certain types of C function calls.
The current definition of funcprototype
funcprototype ::=
(funcdef,
(void|varargs|paramdef+))
is an historical legacy (bound up in the way C compilers worked a
decade ago) more than a designed constraint.
The TC proposes to solve RFE #582822 by changing the funcprototype
in the following backwards-compatible way:
funcprototype ::=
(funcdef,
(void|(paramdef*, varargs?)))
Comments?
Be seeing you,
norm
--
Norman Walsh <[EMAIL PROTECTED]> | Mankind are always happy for
http://www.oasis-open.org/docbook/ | having been happy; so that if you
Chair, DocBook Technical Committee | make them happy now, you make them
| happy twenty years hence by the
| memory of it.--Sydney Smith
