Well, I would like to have here one define for long, which is then later on used consistently to replace use of 'long' type. I don't see much advantage in adding here a signed and a unsigned variant to _mingw.h header. We want to replace use of 'long' keyword. So by this, the keyword 'long' define isn't the same as the boolean type. So I am a bit opposed against the WIN.... prefix. IMHO it should be a define with two leading underscores, unlikely to be mixed with a destinguished type. So my vote goes all for __32LONG, but I am fine with __WINLONG too. As indeed we want to make sure that type 'long' is 32-bit to satisfy windows ABI.. Jacek is right that we will need additionally a macro, which handles the constant-postfix 'L'.
Regards, Kai ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
