public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: "Carlos O'Donell" <carlos@redhat.com>,
	GNU C Library <libc-alpha@sourceware.org>
Subject: Re: Consensus on unit tests?
Date: Fri, 01 Jul 2016 06:43:00 -0000	[thread overview]
Message-ID: <d5d220f3-2eb0-f5b7-bb11-8638b4d116d2@redhat.com> (raw)
In-Reply-To: <92609f90-7a53-a455-ca72-b9baae224a38@redhat.com>

On 06/25/2016 01:59 AM, Carlos O'Donell wrote:

> I would like to remove the superfluous condition and add a
> unit test for all the cases that define the way the interface
> should behave.
>
> Since Florian asked for pretty diagrams, I have included them.

I can't quote your patch due to the way it is included in the message 
(inline text after the signature).

What's unclear based on the documentation if the address has to fall in 
the range covered by the link map (i.e., if there are indeed only three 
cases, or five).  If there is indeed a precondition that the address is 
in some special range, you should add it to the comment.

There is also a stray comment in the function itself.

> Should we allow unit tests for the dynamic loader?

I expect unit tests which look like this to be noncontroversial.

Things are more interesting if you have to add testing hooks to the 
code, or export additional symbols.

Thanks,
Florian

  reply	other threads:[~2016-07-01  6:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-24 23:59 Carlos O'Donell
2016-07-01  6:43 ` Florian Weimer [this message]
2016-07-04 14:27   ` Carlos O'Donell
2016-07-04 19:07     ` Florian Weimer
2016-07-04 20:44       ` Carlos O'Donell
2016-08-15 14:23         ` Florian Weimer
2016-09-03  0:32 ` Roland McGrath

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=d5d220f3-2eb0-f5b7-bb11-8638b4d116d2@redhat.com \
    --to=fweimer@redhat.com \
    --cc=carlos@redhat.com \
    --cc=libc-alpha@sourceware.org \
    /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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).