This is the mail archive of the
docbook-apps@lists.oasis-open.org
mailing list .
How to make <funcprototype/> produce ANSI prototypes
- To: Docbook Apps Mailing list <docbook-apps at lists dot oasis-open dot org>
- Subject: DOCBOOK-APPS: How to make <funcprototype/> produce ANSI prototypes
- From: "Rafael R. Sevilla" <sevillar at team dot ph dot inter dot net>
- Date: Wed, 06 Jun 2001 18:59:10 +0800 (PHT)
I just noticed that <funcprototype/> produces K&R (old-style C) prototypes
as opposed to ANSI. Is there a way to make it produce ANSI prototypes
instead, or at least fix things up so that each parameter appears on a
separate line? I hate the way it does things at the moment. This
fragment:
<funcsynopsis>
<funcprototype>
<funcdef>void <function>rijndael_setup</function></funcdef>
<paramdef>RIJNDAEL_context
<parameter>*ctx</parameter></paramdef>
<paramdef>size_t <parameter>keysize</parameter></paramdef>
<paramdef>const UINT8 <parameter>*key</parameter></paramdef>
</funcprototype>
</funcsynopsis>
renders to:
void rijndael_setup(ctx, keysize, key) RIJNDAEL_context *ctx; size_t
keysize; const UINT8 *key;
when I would rather have it produce:
void rijndael_setup(RIJNDAEL_context *ctx, size_t keysize, const UINT8
*key);
or at the very least something like:
void rijndael_setup(ctx, keysize, key)
RIJNDAEL_context *ctx;
size_t keysize;
const UINT8 *key;
with each individual parameter on a line by itself. By the way, I'm using
version 1.39 of the DocBook XSL stylesheets, Saxon 6.3, and FOP 0.19.0
(CVS).
--
Rafael R. Sevilla <sevillar@team.ph.inter.net> +63(2) 8177746 ext. 8311
Programmer, InterdotNet Philippines +63(917) 4458925