disable_consistency_check Attribute

  • Article

Directs RPC to not enforce correlation consistency checking.

interface interface-name
{
  return-type function-name(
        [[attribute-list,] disable_consistency_check] param-type param-name
}

For correlated parameters, RPC will enforce that a non-null buffer is passed when the correlation count variable is non-null.

Example

HRESULT PassString( [in] DWORD Length, [in, unique, string, 
    size_is( Length )]LPWSTR MyString );

If MyString is NULL, RPC will reject the call unless Length is set to 0. Note that RPC will allow Length to be 0 while MyString is non-NULL, and RPC will treat MyString as a 0-length buffer allocation.

Remarks

To disable this checking, the IDL can contain the [disable_consistency_check] attribute on a parameter, typedef, or pointer type. This will direct RPC to not enforce the consistency between the buffer pointer and the correlation variable for the buffer pointed to by the parameter or pointer.

To disable consistency checking for an entire MIDL compilation (and disable enforcement of the checking in all cases), the MIDL command line switch /backward_compat maybenull_sizeis can be used. This requires that the target of the MIDL compilation be at least –target NT60.