From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Re: [PATCH 2/4] Add basic sys/cdefs.h found on most unix
Date: Sat, 20 Oct 2012 19:44:22 -0400 [thread overview]
Message-ID: <20121020234422.GT254@brightrain.aerifal.cx> (raw)
In-Reply-To: <20121020165013.c849d997.idunham@lavabit.com>
On Sat, Oct 20, 2012 at 04:50:13PM -0700, Isaac Dunham wrote:
> On Sun, 21 Oct 2012 01:38:52 +0200
> Abdoulaye Walsimou GAYE <awg@embtoolkit.org> wrote:
>
> > On 10/21/2012 01:18 AM, Isaac Dunham wrote:
> > > On Sat, 20 Oct 2012 22:15:43 +0200
> > > Abdoulaye Walsimou Gaye <awg@embtoolkit.org> wrote:
> > >
> > >> Signed-off-by: Abdoulaye Walsimou Gaye <awg@embtoolkit.org>
> > >> ---
> > >> include/sys/cdefs.h | 22 ++++++++++++++++++++++
> > >> 1 file changed, 22 insertions(+)
> > >> create mode 100644 include/sys/cdefs.h
> > > I'm pretty sure that the last three times sys/cdefs.h was proposed, it was rejected.
>
> > Unfortunately many packages (wrongly?) use to rely on macros defined there,
> > sometimes indirectly via <features.h>.
> Yes, but that wasn't enough of a reason the last three times.
>
> It isn't standard (-> not universal/portable), is very easily
> replaced, and even if it is added for compatability, it should not
> be used internally.
Not only that; all its macros are explicitly in the namespace reserved
for the implementation, because it's designed to be an internal part
of the implementation of libc's headers, not a public interface.
> I would say that the last point is the most important.
Yes. Even if we eventually do find a compelling reason to offer this
header, there's no reason it should be used internally. Using it is
just more expensive and obfuscated than writing things out explicitly.
Rich
next prev parent reply other threads:[~2012-10-20 23:44 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-20 20:15 [PATCH 0/4] Import <netinet/ether.h> features from NetBSD Abdoulaye Walsimou Gaye
2012-10-20 20:15 ` [PATCH 1/4] Build system: give ability to install lib/crt*.o files separately Abdoulaye Walsimou Gaye
2012-10-20 23:49 ` Rich Felker
2012-10-20 20:15 ` [PATCH 2/4] Add basic sys/cdefs.h found on most unix Abdoulaye Walsimou Gaye
2012-10-20 23:18 ` Isaac Dunham
2012-10-20 23:38 ` Abdoulaye Walsimou GAYE
2012-10-20 23:38 ` Rich Felker
2012-10-21 0:13 ` Abdoulaye Walsimou GAYE
2012-10-21 0:11 ` Rich Felker
2012-10-21 0:38 ` Abdoulaye Walsimou GAYE
2012-10-21 0:39 ` John Spencer
2012-10-21 1:21 ` John Spencer
2012-10-20 23:50 ` Isaac Dunham
2012-10-20 23:44 ` Rich Felker [this message]
2012-10-20 20:15 ` [PATCH 3/4] Import BSD functions defined in <netinet/ether.h> from NetBSD Abdoulaye Walsimou Gaye
2012-10-20 23:37 ` idunham
2012-10-21 0:40 ` Abdoulaye Walsimou GAYE
2012-10-21 0:42 ` John Spencer
2012-10-21 0:41 ` Rich Felker
2012-10-21 0:52 ` Abdoulaye Walsimou GAYE
2012-10-21 0:48 ` Rich Felker
2012-10-21 0:57 ` John Spencer
2012-10-21 0:53 ` Rich Felker
2012-10-20 20:15 ` [PATCH 4/4] <netinet/ether.h>: Add GNU extensions ether_ntoa_r() and ether_aton_r() Abdoulaye Walsimou Gaye
2012-10-20 23:53 ` Rich Felker
2012-10-21 0:43 ` Abdoulaye Walsimou GAYE
2012-10-21 0:46 ` John Spencer
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=20121020234422.GT254@brightrain.aerifal.cx \
--to=dalias@aerifal.cx \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).