version 1.7, 2000/11/09 17:52:33 |
version 1.8, 2000/11/10 05:10:39 |
|
|
and |
and |
.Fl T |
.Fl T |
are global and can be used with the other options. |
are global and can be used with the other options. |
.Sh NOTES |
|
The |
|
.Tn RPC |
|
Language does not support nesting of structures. |
|
As a work-around, |
|
structures can be declared at the top-level, |
|
and their name used inside other structures in |
|
order to achieve the same effect. |
|
.Pp |
|
Name clashes can occur when using program definitions, |
|
since the apparent scoping does not really apply. |
|
Most of these can be avoided by giving |
|
unique names for programs, |
|
versions, |
|
procedures and types. |
|
.Pp |
|
The server code generated with |
|
.Fl n |
|
option refers to the transport indicated by |
|
.Em netid |
|
and hence is very site specific. |
|
.Sh EXAMPLES |
.Sh EXAMPLES |
The command |
The command |
.Pp |
.Pp |
|
|
.Bd -literal -offset indent |
.Bd -literal -offset indent |
$ rpcgen -n tcp -o prot_svc.c prot.x |
$ rpcgen -n tcp -o prot_svc.c prot.x |
.Ed |
.Ed |
|
.Sh NOTES |
|
The |
|
.Tn RPC |
|
Language does not support nesting of structures. |
|
As a workaround, structures can be declared at the top-level, and their |
|
name used inside other structures in order to achieve the same effect. |
|
.Pp |
|
Name clashes can occur when using program definitions, since the apparent |
|
scoping does not really apply. |
|
Most of these can be avoided by giving unique names for programs, |
|
versions, procedures, and types. |
|
.Pp |
|
The server code generated with |
|
.Fl n |
|
option refers to the transport indicated by |
|
.Em netid |
|
and hence is very site specific. |
.Sh SEE ALSO |
.Sh SEE ALSO |
.Xr cpp 1 |
.Xr cpp 1 |