On 09/14/13 08:03, Kai Tietz wrote: > 2013/9/14 JonY <[email protected]>: >> On 9/14/2013 02:45, Ozkan Sezer wrote: >>> On 9/13/13, Kai Tietz wrote: >>>> Well, I consider, if we might want to define _FORCENAMELESSUNION in >>>> _mingw.h for 3.0, and remove it on our trunk. By this we reduce >>>> fallout right now, provide a version check later on for changed >>>> behavior. >>> I don't know the specifics about that fallout, but is it impossible that >>> defining that would cause another fallout? >>> >> Alternative, we postpone dealing with it until v4, branch now and revert >> the changes in v3 so _FORCENAMELESSUNION is not needed. > No, better to define _FORCENAMELESSUNION for v3, and remove this > define later on for trunk. I don't see an advantage to modify this > point, as by defining this macro we actual provide old behavior.
I kind of agree that simply the fact that #if change is less invasive than global #define, so change in oaidl.idl seems a bit safer. In any way, the portable way for dealing with VARIANT type are V_* macros from oleaut.h, like V_VT(). Those need to be compatible with whatever is used to declare VARIANT struct (it is not now). Whatever solution we have, we should make sure that those are doing the right thing. Jacek ------------------------------------------------------------------------------ LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99! 1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint 2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13. http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
