Web lists-archives.com

Re: [Mingw-users] msvcrt printf bug




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

On 16/01/17 16:51, Earnie wrote:
> On 1/15/2017 4:24 PM, John Brown wrote:
>>
>> You have skillfully avoided addressing the fact that it works as the
>> original poster expects with glibc 2.2.5 (tested on Linux / glibc 2.19).
>>
> 
> Maybe providing a pristine patch could help.  You also make comparisons
> between apples and oranges, the two are just not the same; just like
> Linux and its C runtime is not the same as the Windows C runtime.  We
> have in the past created workarounds for what appeared to be
> deficiencies in the Microsoft C runtime.

And, in this case, we _already_ have a perfectly viable alternative
to the entire family of MSVCRT.DLL printf() functions; (enable it
by defining _XOPEN_SOURCE to any non-zero value, prior to including
_any_ header file ... see <_mingw.h> for the specifically pertinent
values).  It uses David M. Gay's gdtoa floating point formatting
engine, (which, AFAIK is the same as used by glibc, so I'd expect
consistent output).

Regardless, it is a bug to emit more significant digits than the
underlying data format is capable of representing ... a bug by
which both glibc and our implementation are, sadly, afflicted;
that the OP attempts to attribute any significance whatsoever to
those superfluous digits is indicative of an all too common gap
in knowledge ... garbage is garbage, whatever form it may take.

- -- 
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)

iQIcBAEBAgAGBQJYfSpvAAoJEMCtNsY0flo/O8UP/2QdQdKWbWzAPXNlbimZj112
ogyPa1dsibCUDuu/YV2srkyXB6hMfhKl1yvNUz/D4Tb9KYFAUF0kpY5nKQ5plH5F
mow7Rov0vrAgSy4V2nnPV0NK9SnTRLgsdqBXUFDfBTKNxRpNkK/iBaSjmCCj3sVV
ViteHu9An70wzWH6d4Rh+fC8pOomX2/E2ICHd6CWj/C+wozrJjn+zxX1anTNdX/n
Ws5CTW/Ofqxysw5644m6UB0w8kcW3+1PljsJAvemZtKJHNet770qL9OOkTg3l12S
5ExRym/aqRsuFN2tYp6bheaprSF7r2Z+DhLkWoAVxpQr/0y0X3C/R1SzYOg5XjFK
zk82UhaynUlXZmTEB/qcs6mF9vMvWxXJ8LShoUVrhGkOnWaGcRZZah+6hNRUC4Ek
lyfWGZrM2amvFrkZFBrZtEThum1lLGC9mNQvzE8s/K+0Jl8SrjRjbaDuEBsg9cd6
q8lJoVa9IFOt59G6mXLYLar3I81irvmOs+r1tIvoGYS5XAoRpGA8nv7iX7tyWJY8
CQrMHxqlaOwyxzBf7g0Rp//QpDvSASPp/cpynDrPAU3uD8pLwVQpfirtedEb5eIm
7XyXMNRvKHR35xmCKIxpF6+MCLAnXfkConS3Bp8/mHCvZn4+6/W4rRR2zr3TA2W+
bERci/93lta2d3u7zG3N
=3B6Y
-----END PGP SIGNATURE-----

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
MinGW-users mailing list
MinGW-users@xxxxxxxxxxxxxxxxxxxxx

This list observes the Etiquette found at 
http://www.mingw.org/Mailing_Lists.
We ask that you be polite and do the same.  Disregard for the list etiquette may cause your account to be moderated.

_______________________________________________
You may change your MinGW Account Options or unsubscribe at:
https://lists.sourceforge.net/lists/listinfo/mingw-users
Also: mailto:mingw-users-request@xxxxxxxxxxxxxxxxxxxxx?subject=unsubscribe