From: "Robert P. J. Day" <rpjday-L09J2beyid0N/H6P543EQg@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: is _ISOC95_SOURCE a valid feature test macro or not?
Date: Wed, 19 Mar 2014 08:30:12 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.11.1403190818350.5322@localhost> (raw)
another possibly silly observation -- /usr/include/features.h makes
no mention of _ISOC95_SOURCE in the early comment listing all(?) of
the possible feature test macros:
... snip ...
__STRICT_ANSI__ ISO Standard C.
_ISOC99_SOURCE Extensions to ISO C89 from ISO C99.
_ISOC11_SOURCE Extensions to ISO C99 from ISO C11.
_POSIX_SOURCE IEEE Std 1003.1.
... snip ...
despite its "USE" macro being mentioned further down in the same
comment:
... snip ...
__USE_ISOC11 Define ISO C11 things.
__USE_ISOC99 Define ISO C99 things.
__USE_ISOC95 Define ISO C90 AMD1 (C95) things.
... snip ...
as well as even further down:
#undef __USE_ISOC95
...
#ifdef _GNU_SOURCE
# undef _ISOC95_SOURCE
# define _ISOC95_SOURCE 1
...
/* This is to enable the ISO C90 Amendment 1:1995 extension. */
#if (defined _ISOC99_SOURCE || defined _ISOC11_SOURCE \
|| (defined __STDC_VERSION__ && __STDC_VERSION__ >= 199409L))
# define __USE_ISOC95 1
#endif
...
i notice in the man pages Changes file the reference that
_ISOC95_SOURCE is now allegedly bogus:
feature_test_macros.7
Michael Kerrisk [Joseph S. Myers]
Remove mention of bogus _ISOC95_SOURCE macro
The _ISOC95_SOURCE macro is defined in <features.h>, but it
does nothing. So remove discussion of it, and move some of
the discussion of C95 under the ISOC99_SOURCE subhead.
but there appear to still be a couple checks for it:
man3/fwide.3:_ISOC95_SOURCE /* Since glibc 2.12 */ ||
man3/wprintf.3:_ISOC95_SOURCE /* Since glibc 2.12 */ ||
thoughts?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2014-03-19 12:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 12:30 Robert P. J. Day [this message]
2014-03-19 13:23 ` is _ISOC95_SOURCE a valid feature test macro or not? Michael Kerrisk (man-pages)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.2.11.1403190818350.5322@localhost \
--to=rpjday-l09j2beyid0n/h6p543eqg@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).