nocode

[ nocode [ , ACF-interface-attributes ] ] interface interface-name
{ 
    [ include filename-list ; ] ...
    [ typedef [type-attribute-list] typename; ] ...

    [ [ nocode [ , ACF-function-attributes ] ] function-name (
        [ ACF-parameter-attributes ] parameter-name ;
        ...
        );
    ]
    ...
}

ACF-interface-attributes

Specifies a list of one or more attributes that apply to the interface as a whole. Valid attributes include either auto_handle or implicit_handle and either code or nocode. When two or more interface attributes are present, they must be separated by commas.

interface-name

Specifies the name of the interface. In DCE-compatibility mode, the interface name must match the name of the interface specified in the IDL file. When you use the MIDL compiler switch /acf, the interface name in the ACF and the interface name in the IDL file can be different.

filename-list

Specifies a list of one or more C-language header filenames, separated by commas. The full filename, including the extension, must be supplied.

type-attribute-list

Specifies a list of one or more attributes, separated by commas, that apply to the specified type. Valid type attributes include allocate.

typename

Specifies a type defined in the IDL file. Type attributes in the ACF can only be applied to types previously defined in the IDL file.

ACF-function-attributes

Specifies attributes that apply to the function as a whole, such as comm_status. Function attributes are enclosed in square brackets. Separate multiple function attributes with commas.

function-name

Specifies the name of the function as defined in the IDL file.

ACF-parameter-attributes

Specifies ACF attributes that apply to a parameter. Note that zero or more attributes can be applied to the parameter. Separate multiple parameter attributes with commas. ACF parameter attributes are enclosed in square brackets.

parameter-name

Specifies a parameter of the function as defined in the IDL file. Each parameter for the function must be specified in the same sequence and using the same name as defined in the IDL file.

Remarks

The nocode attribute can appear in the ACF header, or it can be applied to an individual function.

When the nocode attribute appears in the ACF header, client stub code is not generated for any remote function unless it has the code function attribute. You can override the nocode attribute in the header for an individual function by specifying the code attribute as a function attribute.

When the nocode attribute appears in the function s attribute list, no client stub code is generated for the function.

Client stub code is not generated when:

    The ACF header includes the nocode attribute.

    The nocode attribute is applied to the function.

    The local attribute applies to the function in the interface file.

Either code or nocode can appear in a function s attribute list, and the one you choose can appear exactly once.

The nocode attribute is ignored when server stubs are generated. You cannot apply it when generating server stubs in DCE-compatibility mode.

See Also