Web lists-archives.com

Re: [Mingw-users] _XOPEN_SOURCE




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

On 20/04/17 16:32, Bryan Henderson wrote:
>> in _every_ case, the application is _required_ to specify the 
>> _XOPEN_SOURCE value for which conformance is desired.
> 
> Why do you say that?  Common sense, or did you see it written
> somewhere?

I've already cited the reference, for the current POSIX.1 specification;
every version of POSIX.1, which I have ever seen, uses fundamentally the 
same wording (paraphrased):

  A conforming application shall ensure that _XOPEN_SOURCE is defined 
  with the value n00 before including any header.

with 'n' representing the POSIX.1 issue number, and 'shall' indicating 
that the requirement is mandatory.

> And what do you make of the fact that every other X/Open-capable C
> library explicitly recognizes _XOPEN_SOURCE = null string as meaning
> "source code expects C library to conform to the original X/Open
> standard?

They are tolerant of applications which seek to be non-conforming; I 
could, of course, show equal tolerance, but I am loathe to encourage 
such non-conformist behaviour.

I would also emphasize that, in the case of MinGW, an appropriate 
definition of _XOPEN_SOURCE will never achieve _full_ conformance to 
any version of the X/Open standard, since only a small subset of it 
is actually supported; if you expect otherwise, you will surely be 
sadly disappointed.

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

iQIcBAEBAgAGBQJY+hrCAAoJEMCtNsY0flo/tlkP/3vFadVyNVSfN3j4bc64v9g1
YMoOy2fY6+1zr8Wmd5VZyzdPVNS50f9O/DXUdPCjBcFYfhnbxeujVy7vLGCSHeCX
38UOibG0ZSEVAiisXkmSz6GJSyYIVkQv9G1ZyJncSSOHutZ9RLP5U2wyaIAfHL2I
sZkAwrrRMMny0SStsDuip3p56WKAGAs36Feak+gvqAEvr31y7Zer/S6LP+HiBKzz
KN30r701fVC9r03A7MBgHr5HF9JrezfKAHntmRs/ppbqMJE5CUMPopt7CZqbTMe5
g96VTVdRMcuFlpRbL0v4dPhNuuzEIjDYMx+ZABQDtsmizQazPe2IARfSVRmV7enC
O00ztMScnsYPB6yaJYOysvXIxZCWJ40fTj/+T2040MnxSQRY5XMtBt8l5iHJ40Yw
c4O6+cHMftBAWNs3a5HOoy3p5FHaQ7XpZcdJ9o0NuzGFCX4KrmeKjL7wZLZaXObG
oNECLz4OuN2l1qQ7hv5dbqtVVPtnmNcOO45+xyegK5vZlaZ6rZCE3PaAA9SO6845
o8FxD53KpHzHJH7FVuJ4y38PiN+Hzakv5DV/Pd14iY8h+k3MmcaVUHbYZlTCS6j9
pPBgNTa9vozMhr0HXzQCmHZmnMa2q433LINyoZ12gIzf4Nua3Bwce5nzfeUlwgwB
aICT6/tp6zVG2AFbtOH8
=Dk1d
-----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