RFC: Dealing with MSDN errors.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

How should we best deal with reports of probable erroneous MSDN content 
such as: https://sourceforge.net/p/mingw/bugs/2248/ ?

Here, the poster provides an acceptable test case, which demonstrates 
that the MSDN information is most likely incorrect, but can refer us 
only to known sources of plagiarised Microsoft header file content, to 
support his proposed correction.  Obviously, we cannot examine those 
plagiarised sources, but should we just take his word for it, and 
correct our headers, as he suggests?

Opinions?

- -- 
Regards,
Keith.

Public key available from keys.gnupg.net
Key fingerprint: C19E C018 1547 DE50 E1D4 8F53 C0AD 36C6 347E 5A3F
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)

iQIcBAEBAgAGBQJYxRnaAAoJEMCtNsY0flo/hRIP/A0OtdIVuXnfQHVV4xytt5Ud
gChm3rRiO3NsqvpXn0ym27Ul8mYk1kdkKuykw9iiCCCHSKJVTKZzbhYIxzAuWUxp
+//39fTEIdqUj2iGiWAW0BdPvNPvIv+1w4Y1q8Qcul2FuyWmdnbg5Siqv2kk4r/K
nsLTrUt/iCMIb2PUAkrvrWHoeVG9T7r9k1mhY7+p1EiRm/tdL3xG5LZI8CWgx+t5
syVSzpvDOt4vGUKlQ7UND6VX7piEoIRDms71gI9Udr1uwXtCbrRsHDVyA7uiyzcB
JpW2oVkumTpTkerfBGiYqlJNu4dlYx9jFmYInRJcRrCOb2tVkal0Oie6EOvpkGvA
e+3kuQezPMpuQz/JmmTJ6fyj8ucWBeHzFxW2KJhlpxUMzDjPrGK/hYr9HATtCPwF
B55g9+8fH4VWDONUKNWfL8YmAIERUSXVzz5mQQfuusIN+lid9GoYiXNARn/axqU6
Yz/CX4xODF3VJvmD2A1Mepvwh7Fi6BHYQCXdybrT+mXt4u72DW3CawQ86QLboWnd
rQLD9wh4O85cwNOIyMV2rai3pKWDURecGNTGUi2o/LpVWgwP6jxU6PsgiIIovpzU
Vw204NP6341Nhfy+4nErZDCWHoBhL602/JRm93g600DY6iaoNiRKWfhE5uAnXceE
pApqrZS1CZih3eVoIaU7
=+nCd
-----END PGP SIGNATURE-----

------------------------------------------------------------------------------
Announcing the Oxford Dictionaries API! The API offers world-renowned
dictionary content that is easy and intuitive to access. Sign up for an
account today to start using our lexical data to power your apps and
projects. Get started today and enter our developer competition.
http://sdm.link/oxford