Hi, I poked Kaï on IRC about that; here's the log (very slightly reformatted):
> Well, I admit that I know that pid_t is on standard sdk just a 32-bit value. > Nevertheless there is a lot of software in FOSS, which assumes that pid_t has > actually the width of a pointer, and so we decided to make pidt_t on Windows > 64-bit. > Nevertheless assuming that pid_t is an int, is also wrong on Windows. > It is actually a DWORD. See GetThreadId (or something like that is the API of > Win32). > So negative values are nothing to be concerned about at all. > API is GetCurrentThreadId() > I am openminded here, but we might need to expect fallout by this change. > Not sure if this is worth the change. -- Adrien Nader ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
