On 7/17/06, Dave Pawson <[EMAIL PROTECTED]> wrote:
On 17/07/06, Kyle Hamilton <[EMAIL PROTECTED]> wrote:
> Basically, when you're passing a pointer to a function as a parameter
> to another function for callbacks and such.
>
> > http://www.docbook.org/tdg/en/html/funcparams.html
>
> There's an example for qsort in there, but there's a problem: it loses
> information between the XML and the output. Specifically, what's
> printed is:
>
> void qsort( dataptr,
> dataptr,
> left,
> right,
> (* comp));
> dataptr;
> left;
> right;
> int (* comp) (void *, void *);
>
> i.e., it loses type information for dataptr, left, and right.
>
> > Is that any help?
>
> It's a great help for exposition of what the problem is! :)
Yes, very clear. I've asked the guru's.
Only parameterization is to use K&R or ANSI format (do you understand
the difference?)
/* K&R */
int somefunc(x, y)
char *x, int *y
{ ... return 1; }
/* ANSI */
int somefunc(char *x, int *y)
{ ... return 1; }
Either way, the results of the DocBook conversion lose the type
information for the parameters, so it's not K&R format either. Since
OpenSSL makes fairly extensive use of callbacks, the need for the
functions that get and set them to be well-documented is extremely
important.
WhenI find out how to get them back I'll let you know.
It may be deliberate, but I can't see why.
Neither can I. The official docs really can't be put into DocBook
until this oversight is corrected -- but there's no reason why initial
work can't be done pending the bugfix.
-Kyle H
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [email protected]
Automated List Manager [EMAIL PROTECTED]
