mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Re: cluts comments
Date: Wed, 3 Aug 2011 13:33:04 -0400	[thread overview]
Message-ID: <20110803173304.GY132@brightrain.aerifal.cx> (raw)
In-Reply-To: <4E398796.7080509@gmail.com>

On Wed, Aug 03, 2011 at 07:38:30PM +0200, Luka Marčetić wrote:
> >alloc.c does not compile with glibc here
> >it seems _POSIX_C_SOURCE is not enough for
> >glibc to have SA_NODEFER in signal.h
> >i guess that's a glibc bug..
> 
> Thanks for the bug, Szabolcs. I'll correct it, and also add the header.
> Not sure why you get an error for SA_NODEFER though. It compiles for
> me just fine with gcc version 4.6.1 (Debian 4.6.1-5) .

I think he must be using an older version of glibc. It looks like they
fixed it to support POSIX 2008 better sometime this year.. Since it's
worthwhile to be able to test and evaluate regressions versus older
glibc versions, please make an effort to support them too if it's not
a big deal. (I thought the SA_NODEFER stuff was going to be removed
anyway, though..??)

> Well it is used more, I don't know about a convention... I do like
> %i better (though I was taught %d - hence the omissions). The reason
> why I like %i is that it implies the integer type. And that's what i
> have in alloc.c.

Yes, but %d makes explicit the base you want it printed in. :)
I'd never thought of %i as being useful in contrase with %f in code
that's mixing int/float and always using decimal, since I'm much more
often using integers only and more interested in the base...

Rich


      reply	other threads:[~2011-08-03 17:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-03 17:04 Szabolcs Nagy
2011-08-03 17:09 ` Solar Designer
2011-08-03 17:13 ` Rich Felker
2011-08-03 17:38 ` Luka Marčetić
2011-08-03 17:33   ` 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=20110803173304.GY132@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).