On Fri, 1 Oct 2004, Dmitry Timoshkov wrote:
[...]
> > Why would it break compilation with the SDK and Mingw headers?
>
> I wrongly formulated the problem: it will Wine internal COM interfaces
> not follow the standard practice, be contradict and confuse the Wine code.
That's the thing, the standar
"Francois Gouget" <[EMAIL PROTECTED]> wrote:
> > But that change makes Wine code not compilable with SDK and Mingw headers,
> > I don't think it's an acceptable change.
>
> Do you mean this change in particular (i.e. not using COBJMACROS for
> protecting internal Wine structures) or the COBJMACRO
On Fri, 1 Oct 2004, Dmitry Timoshkov wrote:
> "Francois Gouget" <[EMAIL PROTECTED]> wrote:
>
> > COBJMACROS is very C unfriendly as it requires the caller to define it
> > if it wants to use COM objects. The following check is much better as
> > it does the right thing automagically:
> >
> > #if !
"Francois Gouget" <[EMAIL PROTECTED]> wrote:
> COBJMACROS is very C unfriendly as it requires the caller to define it
> if it wants to use COM objects. The following check is much better as
> it does the right thing automagically:
>
> #if !defined (__cplusplus) || defined(CINTERFACE)
>
> So for
