anchor.diff:  /// @nodoc
   const BTH_LINK_KEY_LENGTH = 16;
   
  +/// The BLUETOOTH_AUTHENTICATION_METHOD enumeration defines the supported
  +/// authentication types during device pairing.
  +///
   /// {@category Enum}
   class BLUETOOTH_AUTHENTICATION_METHOD {
     static const BLUETOOTH_AUTHENTICATION_METHOD_LEGACY = 0;
  
positive.code:   static const BLUETOOTH_MITM_ProtectionNotDefined = 6;
  }
  
  /// {@category Enum}
  class BLUETOOTH_IO_CAPABILITY {
    static const BLUETOOTH_IO_CAPABILITY_DISPLAYONLY = 0;
  
negative.code:   static const MC_HEIGHT = 1;
  }
  
  /// Indicates how the activation context is to be deactivated.
  ///
  /// If this value is set and the cookie specified in the ulCookie parameter is
  /// in the top frame of the activation stack, the function returns an
  /// ERROR_INVALID_PARAMETER error code. Call GetLastError to obtain this code.
  ///
  /// If this value is set and the cookie is not on the activation stack, a
  /// STATUS_SXS_INVALID_DEACTIVATION exception will be thrown.
  ///
  /// If this value is set and the cookie is in a lower frame of the activation
  /// stack, all of the frames down to and including the frame the cookie is in is
  /// popped from the stack.
  const DEACTIVATE_ACTCTX_FLAG_FORCE_EARLY_DEACTIVATION = 1;
  
  // *** COM CONSTANTS ***
  
  /// Operation successful
  const S_OK = 0;
  
  /// Operation successful
  ///
  /// Some methods use S_FALSE to mean, roughly, a negative condition that is not
  /// a failure. It can also indicate a "no-op"—the method succeeded, but had no
  /// effect. For example, the CoInitializeEx function returns S_FALSE if you call
  /// it a second time from the same thread. If you need to differentiate between
  /// S_OK and S_FALSE in your code, you should test the value directly, but still
  /// use FAILED or SUCCEEDED to handle the remaining cases.
  const S_FALSE = 1;
  
  /// @nodoc
  