mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Solar Designer <solar@openwall.com>
To: musl@lists.openwall.com
Subject: Re: cluts review
Date: Wed, 13 Jul 2011 16:21:28 +0400	[thread overview]
Message-ID: <20110713122128.GA22658@openwall.com> (raw)
In-Reply-To: <4E1D8964.3020502@gmail.com>

Luka,

On Wed, Jul 13, 2011 at 02:02:44PM +0200, Luka Mar??eti?? wrote:
> Hmm, hope you won't mind me saying: Diff output for multiple files 
> replacing 1-2 non-subsequent lines is not very readable.

I don't mind, but I also don't understand what you're trying to say.

It is a patch that you can directly apply to your code, with patch(1) -
or you can indeed just read it and see what has changed where, then
decide which of the changes to merge or what else to do about them.

What would be more readable than that, yet just as specific?

> Instead of <sys/param.h> 
> for PATH_MAX, will limits.h do (that's what i usually include)?

No, it doesn't get PATH_MAX defined for me.

What you could actually want to do is get rid of the dependency on
PATH_MAX and FILENAME_MAX.  The system does not guarantee that actual
pathnames fit in PATH_MAX anyway.  So you may want to replace those
strcat()'s with dynamic memory allocation or add a check for potential
buffer overflow there (then report the error and skip the test).

For dynamic memory allocation, you may use asprintf(3), but it is not
very portable, or you may use my concat() function:

http://openwall.info/wiki/people/solar/software/public-domain-source-code/concat

(put it in a common source file).

> 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.

I definitely did not intend to complain about the lack of micro-test
success reports.  I do intend to post more stuff.

Thanks,

Alexander


  reply	other threads:[~2011-07-13 12:21 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ć
2011-07-13 12:21   ` Solar Designer [this message]
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=20110713122128.GA22658@openwall.com \
    --to=solar@openwall.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).