Date: Sun, 2 Sep 2012 13:13:12 -0400 From: Rich Felker <dalias@...ifal.cx> To: musl@...ts.openwall.com Subject: Re: Best bikeshed ever (feature test macros) On Sun, Sep 02, 2012 at 01:06:25PM -0400, Gregor Richards wrote: > >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). > > The same can be accomplished on any modern libc by using -std=c89 or > -std=c99. You shouldn't have to port to a new libc to find these I'm a bit confused because I suspect the code in question actually wanted POSIX, not just baseline C... > problems, nor should said new libc be designed in such a way that > the majority of software doesn't work on it without additional > complication. Especially when, as I will repeat over and over again, > going through the additional complication to supposedly make your > code more portable WILL INVARIABLY MAKE YOUR CODE LESS PORTABLE. This only applies if you're using extensions. And actually, I'm not sure it's the case. If you add -D_GNU_SOURCE (and no other feature test macros), does that really _hide_ any interfaces on BSD, Darwin, Solaris, or other relevant systems? Rich
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.