From: Kevin Daudt <me@ikke.info>
To: "René Scharfe" <l.s.r@web.de>
Cc: Git List <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>, Jeff King <peff@peff.net>,
"brian m. carlson" <sandals@crustytoothpaste.net>,
Michael Haggerty <mhagger@alum.mit.edu>,
Thomas Gummerer <t.gummerer@gmail.com>
Subject: Re: [PATCH 1/3] notes: move hex_to_bytes() to hex.c and export it
Date: Sun, 5 Nov 2017 20:57:50 +0100 [thread overview]
Message-ID: <20171105195750.GA7647@alpha.vpn.ikke.info> (raw)
In-Reply-To: <71257adb-56c0-2e13-c0b1-a7ee4b084207@web.de>
On Sun, Nov 05, 2017 at 05:47:47PM +0100, René Scharfe wrote:
> Am 05.11.2017 um 03:56 schrieb Kevin Daudt:
> > On Tue, Oct 31, 2017 at 02:46:49PM +0100, René Scharfe wrote:
> >> Make the function for converting pairs of hexadecimal digits to binary
> >> available to other call sites.
> >>
> >> Signed-off-by: Rene Scharfe <l.s.r@web.de>
> >> ---
> >> cache.h | 7 +++++++
> >> hex.c | 12 ++++++++++++
> >> notes.c | 17 -----------------
> >> 3 files changed, 19 insertions(+), 17 deletions(-)
> >>
> >> diff --git a/cache.h b/cache.h
> >> index 6440e2bf21..f06bfbaf32 100644
> >> --- a/cache.h
> >> +++ b/cache.h
> >> @@ -1317,6 +1317,13 @@ extern int set_disambiguate_hint_config(const char *var, const char *value);
> >> extern int get_sha1_hex(const char *hex, unsigned char *sha1);
> >> extern int get_oid_hex(const char *hex, struct object_id *sha1);
> >>
> >> +/*
> >> + * Read `len` pairs of hexadecimal digits from `hex` and write the
> >> + * values to `binary` as `len` bytes. Return 0 on success, or -1 if
> >
> > Is it correct to call the result binary? I would say that it's the value
> > that gets stored. To me, this value does not really have a base.
>
> Here's the full context:
>
> /*
> * Read `len` pairs of hexadecimal digits from `hex` and write the
> * values to `binary` as `len` bytes. Return 0 on success, or -1 if
> * the input does not consist of hex digits).
> */
> extern int hex_to_bytes(unsigned char *binary, const char *hex, size_t len);
>
> The patch moves the comment verbatim. Words in backticks (`binary`,
> `hex`, `len`) are parameter names.
>
> The function converts pairs of hexadecimal digits (base 16, ASCII
> encoded) to bytes (base 256). A byte can be seen as an array of bits;
> thus the output is also binary (base 2) without requiring further
> conversion.
>
> Calling the variable "binary" may seem unspecific, but makes sense in
> the context of this function.
>
> Does any of that help?
>
> Thanks,
> René
Thanks, I have been thinking about it more, and I agree, it does make
sense.
I had a binary representation in mind, but this is refering to binary
data (just like you can have binary files).
Kevin
prev parent reply other threads:[~2017-11-05 19:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-31 13:46 [PATCH 1/3] notes: move hex_to_bytes() to hex.c and export it René Scharfe
2017-10-31 13:49 ` [PATCH 2/3] http-push: use hex_to_bytes() René Scharfe
2017-11-01 19:55 ` Jeff King
2017-11-01 21:59 ` René Scharfe
2017-11-01 22:15 ` Jeff King
2017-11-04 9:05 ` René Scharfe
2017-10-31 13:50 ` [PATCH 3/3] sha1_file: " René Scharfe
2017-11-01 19:58 ` Jeff King
2017-11-05 2:56 ` [PATCH 1/3] notes: move hex_to_bytes() to hex.c and export it Kevin Daudt
2017-11-05 16:47 ` René Scharfe
2017-11-05 19:57 ` Kevin Daudt [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=20171105195750.GA7647@alpha.vpn.ikke.info \
--to=me@ikke.info \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=l.s.r@web.de \
--cc=mhagger@alum.mit.edu \
--cc=peff@peff.net \
--cc=sandals@crustytoothpaste.net \
--cc=t.gummerer@gmail.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.
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).