mailing list of musl libc
 help / color / mirror / code / Atom feed
From: "Luka Marčetić" <paxcoder@gmail.com>
To: musl@lists.openwall.com
Subject: Re: cluts review
Date: Wed, 13 Jul 2011 14:02:44 +0200	[thread overview]
Message-ID: <4E1D8964.3020502@gmail.com> (raw)
In-Reply-To: <20110713110723.GA22153@openwall.com>

On 07/13/2011 01:07 PM, Solar Designer wrote [...]

Hmm, hope you won't mind me saying: Diff output for multiple files 
replacing 1-2 non-subsequent lines is not very readable. Anyway, I'll 
add _POSIX_SOURCE for sigaction and replace SA_NODEFER with 0 (I'm sure 
it served its purpose *somewhere* :-/). Not sure why _BSD_SOURCE is 
needed for alphasort, but I see from the man it is (I usually look up 
functions from SUSv4), so I'll add that too. Instead of <sys/param.h> 
for PATH_MAX, will limits.h do (that's what i usually include)?

> As it is, this patch is a hack.  I think that extensive cleanups to the
> code being patched are needed.

As I've announced, alloc.c is going to be rewritten: As Rich suggested 
to me, it'll use arrays instead of lists which will speed up things and 
make them prettier.. actually I think it's in alloc.c's TODO. String.c 
will also be rewritten, because, as I've said, it's impractical to write 
so much code for a few tests (not sure yet how exactly). If there are 
any other critiques, I would like to hear them.

> I have other observations as well (such as from actually running the
> tests), which I hope to post separately.

Ok. I only hope it's understood that I've made the tests report failures 
alone. It would serve no purpose to output success messages (eg. 
numeric.c would report a *lot* of things). If that's not what you meant, 
shoot, I'm listening.
Thanks
Luka.


  reply	other threads:[~2011-07-13 12:02 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-13 11:07 Solar Designer
2011-07-13 12:02 ` Luka Marčetić [this message]
2011-07-13 12:21   ` Solar Designer
2011-07-13 12:57     ` Luka Marčetić
2011-07-13 13:42       ` Rich Felker
2011-07-13 14:21         ` Solar Designer
2011-07-13 13:54       ` Solar Designer
2011-07-13 14:00         ` Rich Felker
2011-07-13 14:31           ` Solar Designer
2011-07-13 14:03     ` Rich Felker
2011-07-13 14:37       ` Solar Designer
2011-07-13 16:03   ` Solar Designer
2011-07-13 16:55     ` Luka Marčetić
2011-07-13 17:05       ` Solar Designer
2011-07-13 17:25         ` Luka Marčetić
2011-07-13 17:52           ` Solar Designer
2011-07-13 19:29             ` Luka Marčetić
2011-07-13 19:55               ` Rich Felker
2011-07-13 20:39               ` Solar Designer
2011-07-13 21:44                 ` Solar Designer
2011-07-13 19:52             ` Rich Felker
2011-07-13 20:03       ` Rich Felker
2011-07-14 18:56       ` Rich Felker
2011-07-13 13:38 ` Rich Felker
2011-07-13 14:12   ` Solar Designer
2011-07-13 14:26     ` Rich Felker
2011-07-13 14:46       ` Solar Designer
2011-07-13 16:25   ` Luka Marčetić
2011-07-13 17:03     ` Solar Designer

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=4E1D8964.3020502@gmail.com \
    --to=paxcoder@gmail.com \
    --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).