mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Re: Re: Best bikeshed ever (feature test macros)
Date: Wed, 29 Aug 2012 09:49:39 -0400	[thread overview]
Message-ID: <20120829134939.GS27715@brightrain.aerifal.cx> (raw)
In-Reply-To: <20120829073442.66c72367@gmail.com>

On Wed, Aug 29, 2012 at 07:34:42AM +0200, philomath wrote:
> On Fri, 24 Aug 2012 17:41:38 -0400
> Rich Felker <dalias@aerifal.cx> wrote:
> 
> 
> > 1. Leaving everything as it is.
> 
> > 2. Making the kitchen sink (_GNU_SOURCE) available by default.
> 
> > 3. Making only some limited subset (e.g. POSIX base) available by
> > default.
> 
> The bikeshed should definitely not be colored black.
> 
> I'd lean towards 3, 1 is fine too. but please not 2, musl's
> correctness is one of it's unique features...
> 
> Thanks.

Thanks for the input. What correctness aspect is important to you? I
conceptually like the minimal-by-default namespace, but ISO C does not
specify how to invoke the compiler, so even implementations that
require you to use obscure options to get a clean plain-C namespace
are "correct". In practice, any of the options 1-3 would give the
clean namespace as long as -std=c* is used with no feature test
macros.

With that said, I do tend to agree that option 2 is ugly, mainly since
it exposes not just useful modern extensions but all kinds of ugly
legacy things, like sys/sysmacros.h junk getting pulled in from
standard headers... So far the most reasonable proposals I've seen are
along the lines of "XSI plus some extensions" where the latter would
correspond to _BSD_SOURCE or some analogue of _SVID_SOURCE (which is
not supported by musl at this time).

Rich


  reply	other threads:[~2012-08-29 13:49 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-24 21:41 Rich Felker
2012-08-24 22:24 ` Gregor Richards
2012-08-24 23:59 ` Szabolcs Nagy
2012-08-25  7:35 ` orc
2012-08-25 12:32   ` Rich Felker
2012-08-25 15:29     ` orc
2012-08-25  9:11 ` Luca Barbato
2012-08-27 18:08 ` Isaac Dunham
2012-08-29  5:34 ` philomath
2012-08-29 13:49   ` Rich Felker [this message]
2012-08-29 14:01     ` Gregor Richards
2012-08-29 14:43       ` Rich Felker
2012-08-29 15:08         ` Bobby Bingham
2012-08-29 15:23           ` Rich Felker
2012-08-29 17:17             ` Gregor Richards
2012-08-29 17:59       ` Isaac Dunham
2012-08-29 18:08         ` Rich Felker
2012-09-02  8:48 ` Arvid E. Picciani
2012-09-02 15:19   ` Rich Felker
2012-09-02 15:27     ` Arvid E. Picciani
2012-09-02 15:44       ` Rich Felker
2012-09-02 17:00 ` nwmcsween
2012-09-02 17:06   ` Gregor Richards
2012-09-02 17:13     ` Rich Felker
2012-09-02 17:18       ` Gregor Richards
2012-09-02 17:10   ` Rich Felker

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=20120829134939.GS27715@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).