From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Re: Best bikeshed ever (feature test macros)
Date: Sun, 2 Sep 2012 13:10:33 -0400 [thread overview]
Message-ID: <20120902171033.GE27715@brightrain.aerifal.cx> (raw)
In-Reply-To: <AA4F2BC9-EC8F-40D0-8955-F90CD1C7C8F0@gmail.com>
On Sun, Sep 02, 2012 at 10:00:27AM -0700, nwmcsween@gmail.com wrote:
> > Much like the last thread I created to assess opinion (the license
> > one), this is all fairly open-ended and not necessarily going to lead
> > to any short- or long-term change in direction, but then again it
> > could... Replies don't have to be of the form 1/2/3; alternative ideas
> > are welcome, as are replies that just address which goals/criteria are
> > most important to you.
>
> Leave it as is, this actually helps find bugs in software. A real
> world example is accidentally utilizing gnu extensions in mruby (see
> github mruby bug page for more info).
I'm glad to hear of a real-world example where somebody was actually
happy about catching bugs like this. However I don't see how the
current default contributes to finding such bugs. If you're compiling
an app that's targetting POSIX or POSIX+XSI portability, the current
default will not handle that; you need to add feature test macros like
-D_POSIX_C_SOURCE=200809L, and that would work just as well if we
changed the default. Or do you mean to say that the fact that it broke
by default prompted you to add -D_POSIX_C_SOURCE=200809L manually, and
then when you tried compiling again and got an error message, you
realized the issue was a GNU extension that was being used?
Can you clarify? As I'm reading the situation, it sounds to me like
providing POSIX or POSIX+XSI by default would be just as likely to
catch such bugs (if nor moreso, since it would eliminate the case
where somebody adds -D_GNU_SOURCE "just to be safe").
Rich
prev parent reply other threads:[~2012-09-02 17:10 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
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 [this message]
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=20120902171033.GE27715@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).