![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to rosy.1 CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [CSRG BSD Unix] / 43BSDReno / contrib / isode-beta / rosy|
Return to rosy.1 CVS log | Up to [CSRG BSD Unix] / 43BSDReno / contrib / isode-beta / rosy |
1.1 root 1: .TH ROSY 1 "07 Sep 1987"
2: .\" $Header: /f/osi/rosy/RCS/rosy.1,v 7.1 90/07/01 21:06:19 mrose Exp $
3: .\"
4: .\"
5: .\" $Log: rosy.1,v $
6: .\" Revision 7.1 90/07/01 21:06:19 mrose
7: .\" pepsy
8: .\"
9: .\" Revision 7.0 89/11/23 22:21:50 mrose
10: .\" Release 6.0
11: .\"
12: .SH NAME
13: rosy \- RO stub\-generator (yacc\-based)
14: .SH SYNOPSIS
15: .in +.5i
16: .ti -.5i
17: .B rosy
18: \%[\-defs]
19: \%[\-pepsy]
20: \%[\-b\0prefix]
21: \%[\-d]
22: \%[\-o\0module.py]
23: \%[\-s]
24: \%[-T\0tablename]
25: \%[-O\0operationlist]
26: \fImodule.ry\fR
27: .in -.5i
28: .SH DESCRIPTION
29: The \fIrosy\fR program reads a description of a \fIremote operations\fR
30: module and produces \fIC\fR routines and definitions suitable for use with
31: the \fIlibrosy\fR\0(3n) library.
32: .PP
33: The `\-pepsy' switch tells \fIrosy\fR that it's output will be
34: processed by \fIpepsy\fR not \fIposy\fR.
35: .PP
36: The `\-defs' switch tells \fIrosy\fR to provide function names for \fIpepsy\fR.
37: .PP
38: The `\-b' switch sets the prefix used for the output file.
39: If this option is not given,
40: the ASN.1 module name is used.
41: .PP
42: The `\-d' switch directs \fIrosy\fR to ignore most \fIpepy\fR\-style
43: augmentations.
44: .PP
45: The `\-o' switch sets the name of the output file,
46: which is normally derived from the name of the input file.
47: The distinguished file \*(lq\-\*(rq can be used to force the use of the
48: standard output.
49: .PP
50: Normally, \fIrosy\fR prints the name of each operation, error, or type
51: as it works.
52: The `\-s' switch disables this behavior.
53: .PP
54: It is sometimes useful to produce subsets of the full lists of the
55: operations to reduce code sizes. The following switches can be used
56: together with the `\-o' switch to achieve this affect.
57: .PP
58: The `\-T' option specifies a different table name to be used. This is
59: used to build a separate list of operations - usually a subset of the
60: full list.
61: .PP
62: The `\-O' option takes a comma separated list of operation names. If
63: this argument is present, only those operations listed here will be
64: processed. All other operations will be ignored and will not be placed
65: in the table. Currently all errors are output however.
66: .SH FILES
67: .nf
68: .ta \w'\fIprefix\fR-stubs.c 'u
69: \fIprefix\fR-ops.h operation definitions
70: \fIprefix\fR-ops.c operation tables
71: \fIprefix\fR-stubs.c operation stubs
72: .re
73: .fi
74: .SH "SEE ALSO"
75: pepsy(1), pepy(1),
76: .br
77: \fIThe ISO Development Environment: User's Manual\fR,
78: .br
79: ISO DIS 9072/1:
80: \fIInformation Processing \-\- Text Communication \-\- MOTIS \-\- Remote
81: Operations Part 1: Model, Notation and Service Definition\fR,
82: .br
83: CCITT Draft Recommendation X.410:
84: \fIRemote Operations: Model, Notation and Service Definition\fR,
85: .br
86: ECMA Technical Report 31:
87: \fIRemote Operations: Concepts, Notation and Connection\-Oriented Mappings\fR,
88: .br
89: CCITT Recommendation X.410:
90: \fIMessage Handling Systems:
91: Remote Operations and Reliable Transfer Server\fR
92: .SH AUTHORS
93: Julian P. Onions,
94: Nottingham University
95: .br
96: Marshall T. Rose
97: .SH BUGS
98: The \fBBIND\fR and \fBUNBIND\fR macros are currently unrecognized,
99: along with the newer (\fBOBJECT\fR \fBIDENTIFIER\fR) notation for operation
100: codes.
101: .PP
102: The \fBLINKED\fR clause is currently unrecognized for the \fBOPERATION\fR
103: macro.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.