Skip to content

Commit 1d0655c

Browse files
peffgitster
authored andcommitted
config_buf_ungetc: warn when pushing back a random character
Our config code simulates a stdio stream around a buffer, but our fake ungetc() does not behave quite like the real one. In particular, we only rewind the position by one character, but do _not_ actually put the character from the caller into position. It turns out that this does not matter, because we only ever push back the character we just read. In other words, such an assignment would be a noop. But because the function is called ungetc, and because it takes a character parameter, it is a mistake waiting to happen. Actually assigning the character into the buffer would be ideal, but our pointer is actually a "const" copy of the buffer. We do not know who the real owner of the buffer is in this code, and would not want to munge their contents. Instead, we can simply add an assertion that matches what the current caller does, and will let us know if new callers are added that violate the contract. Signed-off-by: Jeff King <[email protected]> Signed-off-by: Junio C Hamano <[email protected]>
1 parent 5e0be13 commit 1d0655c

File tree

1 file changed

+6
-2
lines changed

1 file changed

+6
-2
lines changed

config.c

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -63,8 +63,12 @@ static int config_buf_fgetc(struct config_source *conf)
6363

6464
static int config_buf_ungetc(int c, struct config_source *conf)
6565
{
66-
if (conf->u.buf.pos > 0)
67-
return conf->u.buf.buf[--conf->u.buf.pos];
66+
if (conf->u.buf.pos > 0) {
67+
conf->u.buf.pos--;
68+
if (conf->u.buf.buf[conf->u.buf.pos] != c)
69+
die("BUG: config_buf can only ungetc the same character");
70+
return c;
71+
}
6872

6973
return EOF;
7074
}

0 commit comments

Comments
 (0)