From: "Brian Foster" <brian.foster@innova-card.com>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
"Tommy Thorn" <tommy-git@thorn.ws>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] mailsplit and mailinfo: gracefully handle NUL characters
Date: Fri, 16 May 2008 16:07:32 +0200 [thread overview]
Message-ID: <a537dd660805160707y3830b164td0605a15e6ae05a5@mail.gmail.com> (raw)
In-Reply-To: <200805161539.29259.brian.foster@innova-card.com>
two quibbles of no great importance ...
Johannes Schindelin suggested:
> The function fgets() has a big problem with NUL characters: it reads
> them, but nobody will know if the NUL comes from the file stream, or
> was appended at the end of the line.
>
> So implement a custom read_line() function.
^^^^^^^^^^^
read_line_with_nul()
meaning read part or all of one line which may contain NULs.
>[ ... ]
> diff --git a/builtin-mailsplit.c b/builtin-mailsplit.c
> index 46b27cd..021dc16 100644
> --- a/builtin-mailsplit.c
> +++ b/builtin-mailsplit.c
> @@ -45,6 +45,25 @@ static int is_from_line(const char *line, int len)
> /* Could be as small as 64, enough to hold a Unix "From " line. */
> static char buf[4096];
>
> +/* We cannot use fgets() because our lines can contain NULs */
> +int read_line_with_nul(char *buf, int size, FILE *in)
> +{
> + int len = 0, c;
> +
> + for (;;) {
> + c = fgetc(in);
> + buf[len++] = c;
> + if (c == EOF || c == '\n' || len + 1 >= size)
> + break;
> + }
> +
> + if (c == EOF)
> + len--;
> + buf[len] = '\0';
> +
> + return len;
when fgetc(3) — why not use getc(3)? — returns EOF
it is pointlessly stored in buf[] (as a 'char'!),
len's advanced, and then the storage and advancing
are undone. isn't that a bit silly? untested:
assert(2 <= size);
do {
if ((c = getc(in)) == EOF)
break;
} while (((buf[len++] = c) != '\n' && len+1 < size);
buf[len] = '\0'
return len;
I'd tend to write this in terms of pointers,
something along the lines (untested):
char *p, *endp;
assert(1 <= size);
p = buf;
endp = p + (size-1);
while (p < endp) {
if ((c = getc(in)) == EOF || (*p++ = c) == '\n')
break;
}
*p = '\0';
return p - buf;
> +
> +}
--
"How many surrealists does it take to | Brian Foster
change a lightbulb? Three. One calms | somewhere in south of France
the warthog, and two fill the bathtub | Stop E$$o (ExxonMobil)!
with brightly-coloured machine tools." | http://www.stopesso.com
next prev parent reply other threads:[~2008-05-16 14:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-15 7:27 git bug: rebase fatal failure Tommy Thorn
2008-05-16 10:41 ` Johannes Schindelin
2008-05-16 11:01 ` Johannes Schindelin
2008-05-16 13:03 ` [PATCH] mailsplit and mailinfo: gracefully handle NUL characters Johannes Schindelin
2008-05-16 14:03 ` Avery Pennarun
2008-05-16 14:05 ` David Kastrup
2008-05-16 14:32 ` Johannes Schindelin
2008-05-16 14:56 ` Avery Pennarun
2008-05-16 23:59 ` Johannes Schindelin
2008-05-17 0:06 ` Tommy Thorn
2008-05-17 0:26 ` Johannes Schindelin
2008-05-17 10:07 ` Stephen R. van den Berg
2008-05-17 10:18 ` Johannes Schindelin
[not found] ` <200805161539.29259.brian.foster@innova-card.com>
2008-05-16 14:07 ` Brian Foster [this message]
2008-05-16 14:14 ` David Kastrup
2008-05-16 14:29 ` Johannes Schindelin
2008-05-16 14:33 ` David Kastrup
2008-05-21 18:08 ` Junio C Hamano
2008-05-22 10:38 ` Johannes Schindelin
2008-05-22 17:44 ` Junio C Hamano
2008-05-23 11:21 ` Johannes Schindelin
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=a537dd660805160707y3830b164td0605a15e6ae05a5@mail.gmail.com \
--to=brian.foster@innova-card.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=tommy-git@thorn.ws \
/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).