OSF DCE Application Development Guide--Core Components

Attribute Configuration Language
18.3 Structure
The structure of the ACF is as follows:
interface_header
{
interface_body
}
Follow these structural rules when creating an ACF:
• The basename of the ACF must be the same as the basename of the IDL file although
the extensions are different.
• The interface name in the ACF must be the same as the interface name in the
corresponding IDL file.
• With a few exceptions, any type, parameter, or operation names in the ACF must be
declared in the IDL file, or defined in files included by use of the include statement,
as the same class of name.
• Except for additional status parameters, any parameter name that occurs within an
operation in the ACF must also occur within that operation in the IDL file.
18.3.1 ACF Interface Header
The ACF interface header has the following structure:
[[acf_attribute_list]] interface idl_interface_name
The acf_attribute_list is optional. The interface header attributes can include one or
more of the following attributes, entered within brackets. If you use more than one
attribute, separate them with commas and include the list within a single pair of brackets.
(Note that some of these attributes can be used in the ACF body also. See Section 18.3.2
for more information.)
• code
• nocode
• implicit_handle(handle_type handle_name)
• auto_handle
• explicit_handle
• encode
• decode
• binding_callout(routine_name)
124245 Tandem Computers Incorporated 18−3