This is the mail archive of the
docbook@lists.oasis-open.org
mailing list for the DocBook project.
Re: Re: RFE #582822: VARARG and FUNCDEF together
- From: John Himpel <jwhimpel at tseinc dot com>
- To: Norman Walsh <ndw at nwalsh dot com>
- Cc: docbook at lists dot oasis-open dot org
- Date: Tue, 01 Oct 2002 20:42:47 -0500
- Subject: Re: DOCBOOK: Re: RFE #582822: VARARG and FUNCDEF together
- References: <8765x4d0n8.fsf@nwalsh.com> <87n0qg8n12.fsf@nwalsh.com>
On Tue, 2002-09-17 at 13:54, Norman Walsh wrote:
> / Norman Walsh <ndw@nwalsh.com> was heard to say:
> | The TC proposes to solve RFE #582822 by changing the funcprototype
> | in the following backwards-compatible way:
> |
> | funcprototype ::=
> | (funcdef,
> | (void|(paramdef*, varargs?)))
>
> Make that
>
> funcprototype ::=
> (funcdef,
> (void|varargs|(paramdef+, varargs?)))
>
> To avoid a funcprototype containing only a funcdef.
>
<snip>
Since I am the submitter of the RFE, I suppose I ought to at least be
publicly on the record as supporting this change.
Currently, I am documenting a rather large "C" api and am unable to
represent the concept of repetitive optional arguments in a calling
sequence. It seems unnatural to use &hellip inside <paramdef> to get
the printed output correct when with the proper enhancement to
<funcdef>, one could specify <varargs>. Additionally, <varargs> needs
to appear at any point in the <funcdef> as the argument list can be in
any arbitrary sequence according to the needs of the api.
Thanks.
John