This is the mail archive of the
libc-alpha@sourceware.cygnus.com
mailing list for the glibc project.
Re: [Various] Digested Articles
- To: Andreas Jaeger <aj at suse dot de>
- Subject: Re: [Various] Digested Articles
- From: Thorsten Kukuk <kukuk at suse dot de>
- Date: Mon, 15 May 2000 13:54:33 +0200
- Cc: libc-alpha Mailinglist <libc-alpha at sourceware dot cygnus dot com>,Svein Olav Bjerkeset <svein dot olav dot bjerkeset at oslo dot online dot no>
- References: <u8ya5cum2b.fsf@gromit.rhein-neckar.de>
On Mon, May 15, Andreas Jaeger wrote:
>
> Hi,
>
> we've received the appended bug report together with a patch. I don't
> know enough about the code to say whether it's correct.
>
I think not.
[...]
> >Description:
> rpcgen -N myrpc.x will generate a prototype (in myrpc.h) that does not
> match
> the function definition (in myrpc_xdr.c) when using RPC functions with
> multiple
> arguments. The second argument to the XDR function should be a pointer,
> like
> it is the myrpc_xdr.c file.
>
> >How-To-Repeat:
> Given the file myrpc.x:
>
> /* myrpc.x */
> program MYRPC {
> version MYRPCV1 {
> bool MYRPCPROC (string, int) = 1;
^^^^^^^^^^^^
> } = 1;
> } = 0x3FFFFFF;
I don't think that 2 parameters are allowed by the RPC/XDR definition.
How should it work ? All RPC functions have only a parameter for
the result and one function parameter, not two.
If you look at the XDR language (Power Programming with RPC, page 72),
only one parameter is allowed in the language definition:
procedure:
type-ident procedure-ident "("type-ident")" "=" value
2 Arguments are not possible with this/
I think the bug report is wrong, because myrpc.x conflicts with
the XDR language definition.
Thorsten
--
Thorsten Kukuk http://www.suse.de/~kukuk/ kukuk@suse.de
SuSE GmbH Schanzaeckerstr. 10 90443 Nuernberg
Linux is like a Vorlon. It is incredibly powerful, gives terse,
cryptic answers and has a lot of things going on in the background.