From: Junio C Hamano <gitster@pobox.com>
To: "Geoffrey Irving" <irving@naml.us>
Cc: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
"git@vger.kernel.org" <git@vger.kernel.org>,
"Junio C Hamano" <gitster@pobox.com>
Subject: Re: [PATCH 2/3] cached-sha1-map: refactoring hash traversal code
Date: Tue, 08 Jul 2008 22:27:46 -0700 [thread overview]
Message-ID: <7vabgrmxt9.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <7f9d599f0807082056o666fced9nf87cc81447e16e05@mail.gmail.com> (Geoffrey Irving's message of "Tue, 8 Jul 2008 20:56:06 -0700")
"Geoffrey Irving" <irving@naml.us> writes:
> From c4e60c28fe66985ac8224da832589c982010744e Mon Sep 17 00:00:00 2001
> From: Geoffrey Irving <irving@naml.us>
> Date: Tue, 8 Jul 2008 19:47:22 -0700
> Subject: [PATCH 2/3] cached-sha1-map: refactoring hash traversal code
>
> Pulling common code from get_cached_sha1_entry and set_cached_sha1_entry
> into static find_helper function.
> ---
Sign-off?
> cached-sha1-map.c | 68 +++++++++++++++++++++++++++++-----------------------
> 1 files changed, 38 insertions(+), 30 deletions(-)
The refactoring is good, and it should have been that way from the
beginning. Please don't send in "introduce foo.c [1/N]", "oops, initial
version of foo.c was crap, here is a fixup [2/N]".
> diff --git a/cached-sha1-map.c b/cached-sha1-map.c
> index e363745..147c7a2 100644
> --- a/cached-sha1-map.c
> +++ b/cached-sha1-map.c
> @@ -140,43 +144,47 @@ int get_cached_sha1_entry(struct cached_sha1_map *cache,
> mask = cache->size - 1;
>
> for (i = get_hash_index(key) & mask; ; i = (i+1) & mask) {
> - if (!hashcmp(key, cache->entries[i].key)) {
> - hashcpy(value, cache->entries[i].value);
> - return 0;
> - } else if (is_null_sha1(cache->entries[i].key))
> - return -1;
> + if (!hashcmp(key, cache->entries[i].key))
> + return i;
> + else if (is_null_sha1(cache->entries[i].key))
> + return ~i;
> }
> }
>
> +int get_cached_sha1_entry(struct cached_sha1_map *cache,
> + const unsigned char *key, unsigned char *value)
> +{
> + long i = find_helper(cache, key);
> + if(i < 0)
> + return -1;
Does this have to be extern?
If you are designing an API from scratch, and if you want a long, use it
consistently. Do not demote an int to shorter int in a callchain
unnecessarily.
prev parent reply other threads:[~2008-07-09 5:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-09 3:56 [PATCH 2/3] cached-sha1-map: refactoring hash traversal code Geoffrey Irving
2008-07-09 5:27 ` Junio C Hamano [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=7vabgrmxt9.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=irving@naml.us \
/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 NNTP newsgroup(s).