OSF DCE Application Development Guide--Core Components

OSF DCE Application Development Guide—Core Components
double multiply (double a,
double b,
error_status_t * c_sts,
error_status_t * f_sts)
{
/*
* c_sts and f_sts appear in the acf, but do not appear
* in the idl definition. In this case, c_sts and f_sts
* are placed at the end of the parameter list generated
* by the idl compiler. To conform to the prototype
* generated by idl, your server code must also declare
* these parameters.
*
* In the successful case, c_sts and f_sts are
* automatically returned to the client as
* error_status_ok. Even though c_sts and f_sts are
* parameters to the function, the server code must not
* modify these parameters or store through them.
*/
...
return answer;
}
18.3.8 The code and nocode Attributes
The code and nocode attributes allow you to control which operations in the IDL file
have client stub code generated for them by the compiler. These attributes affect only
the generation of a client stub; they have no effect when generating the server stub.
The code and nocode attributes have the following syntax. (See the example at the end
of this section.)
For an interface—
[code | nocode] interface interface_name
For an operation—
[code | nocode ] operation_name ([parameter_list]);
When you specify nocode as an attribute on an ACF interface, stub code is not
generated for the operations in the corresponding IDL interface unless you also specify
code for the particular operation(s) for which you want stub code generated. Similarly,
when you specify code (the default) as an attribute on an ACF interface, stub code is
generated for the operations in the corresponding IDL interface unless you also specify
nocode for the particular operations for which you do not want stub code generated.
18 − 12 Tandem Computers Incorporated 124245