Web lists-archives.com

Re: [Mingw-users] Problems compiling Gnulib-assisted projects with MinGW runtime 3.22.2




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

On 10/10/16 20:47, Eli Zaretskii wrote:
>> Possibly because they rely on a POSIX non-compliance in glibc;
>> (a non-compliance which is acknowledged within glibc's
>> <strings.h> itself, as a BSD compatibility issue, and we
>> certainly don't claim any level of BSD conformity, so why would
>> we duplicate some other project's associated non-conforming
>> (mis)features?)
> 
> Because it's a (gratuitous) nuisance?
> 
> It makes little sense IMO to claim any strict compatibility to
> some Posix-related standards in MinGW runtime, because MS runtime
> is inherently incompatible with any such standard, so no matter
> what we do, we will always be, like, 95% incompatible.  Someone who
> wants Posix on Windows should use Cygwin, not MinGW.

I don't buy that argument.  If you want to use *POSIX* specific
features in MinGW, such as strcasecmp() and strncasecmp(), which
aren't any part of Windows or C99 in the first place, then it should
at least be done in compliance with applicable standards.  It's
gratuitous kowtowing to the malpractices of broken projects which
allows such malpractices to proliferate.  Whine at the projects which
gratuitously break the rules, not at those which do it right.  (Or,
should we just accept, for example, makefiles which specify library
dependencies out-of-order, just because that's okay for ELF targets?)

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

iQIcBAEBAgAGBQJX+/gbAAoJEMCtNsY0flo/5x4QAJKH5uJq/tFu8+Ft9+uraEUw
4zgiNVQFKReG4DugOy68Z8aHQ2wVpXgwwpOPGInwmrGXFnr2eik/4vd48HEEZ2Fb
dHcuMqMw+3Z7+KoOpRyEQ+d+v2AW13hgrKIvsvswoXlWfli5+lti3vWCRKa/zGvR
r1hWnEV64AK5fBdHcedOw4uEGWb4yVml+R/0vZ36JfXG7DQjKnSYsEAeOwYJpl7s
9aKw0E0/46KE65enWoUCQIa3bLWKlNjyVjYpvCFVYsU/1jzXxQPi8AxVoFsD6Cc8
jgd8GuDjVlLtfehJUSlEoXsH+jgaclRxF5znbX2aslocFd9b3bp1143aN0ux4FNs
AzxhoOgbsaCdMAE9emmAP4ZlDnq6OxHH2jXd3/+s6UyyyVK2c/YxbU0W48XAj7kQ
AK68NHSMMqjn0XG+lxC9BNgXJpouQeF3vwasWGyscGbjD2pwOhqQXnOCtbDMzP94
9a6/ClNCpaczVbaKXqCRCrmnE9ia1SAvH5locniqoUsutqfq9lh3GHvataiYVuPp
YgLeZWFwdPOH5ceRz4EXR7Rddny8ppnOz2IZtPdd1PkTdQJBpm+P2FrSGnXGxBwi
qwYNyoDkIogShsABnfy4ufcFNZpHYsTZmla1IN3U+pfMSY0YvpMBXRB2VddYuXYl
n5CQd4kXq29ejCW3+ZDh
=jCwb
-----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