On Wed, Jan 16, 2019 at 3:03 PM JonY via Mingw-w64-public < mingw-w64-public@lists.sourceforge.net> wrote:
> On 1/16/19 11:46 AM, Nikolay Sivov wrote: > > On Wed, Jan 16, 2019 at 2:42 PM JonY via Mingw-w64-public < > > mingw-w64-public@lists.sourceforge.net> wrote: > > > >> On 1/16/19 7:18 AM, Nikolay Sivov wrote: > >>> I don't see a reason in keeping this compatibility code, It already > won't > >>> work for C because of IDWriteFactory2 overloaded methods. Another > reason > >>> is DWRITE_FONT_METRICS1 definition from dwrite_1.h, included from > >>> dwrite_2.h, which is also incompatible. > >>> > >>> P.S. what's a deal with WINBOOL, should it be used everywhere? I see > it's > >>> used inconsistently, at least in dwrite*.h headers. > >>> > >> > >> WINBOOL is used to get around type conflicts when Objective C/C++ is > >> used. So, preferably WINBOOL is used. > >> > > > > Right, I gathered that much from the way it's defined. But why does it > > matter for headers that are not meant to be used with Obj-C compiler? > > > > > > Are you sure they're not meant to be used for Objc? > I'm not, but I don't see how "struct a: public struct b" would work in objc, same for overloaded methods. > _______________________________________________ > Mingw-w64-public mailing list > Mingw-w64-public@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mingw-w64-public > _______________________________________________ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
