* [PATCH 2/2] Fix variable initialization in insert_packed_refs().
@ 2010-01-14 23:29 Richard Weinberger
2010-01-15 7:34 ` Johannes Sixt
0 siblings, 1 reply; 3+ messages in thread
From: Richard Weinberger @ 2010-01-14 23:29 UTC (permalink / raw)
To: git; +Cc: gitster
Signed-off-by: Richard Weinberger <richard@nod.at>
---
transport.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/transport.c b/transport.c
index 3b489b3..ecc20a1 100644
--- a/transport.c
+++ b/transport.c
@@ -102,7 +102,7 @@ static void insert_packed_refs(const char *packed_refs,
struct ref **list)
return;
for (;;) {
- int cmp = cmp, len;
+ int cmp, len;
if (!fgets(buffer, sizeof(buffer), f)) {
fclose(f);
--
1.6.5.7
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [PATCH 2/2] Fix variable initialization in insert_packed_refs().
2010-01-14 23:29 [PATCH 2/2] Fix variable initialization in insert_packed_refs() Richard Weinberger
@ 2010-01-15 7:34 ` Johannes Sixt
2010-01-15 11:02 ` Richard Weinberger
0 siblings, 1 reply; 3+ messages in thread
From: Johannes Sixt @ 2010-01-15 7:34 UTC (permalink / raw)
To: Richard Weinberger; +Cc: git, gitster
Richard Weinberger schrieb:
> - int cmp = cmp, len;
> + int cmp, len;
If you look around in the code, you'll find more *cough* initializations
*cough* like this. They are written this way for a reason: they avoid
unwarranted compiler warnings "'foo' may be used uninitialized". Are you
saying that this warning is not triggered anymore after your change?
-- Hannes
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH 2/2] Fix variable initialization in insert_packed_refs().
2010-01-15 7:34 ` Johannes Sixt
@ 2010-01-15 11:02 ` Richard Weinberger
0 siblings, 0 replies; 3+ messages in thread
From: Richard Weinberger @ 2010-01-15 11:02 UTC (permalink / raw)
To: Johannes Sixt; +Cc: git, gitster
Am Freitag 15 Januar 2010 08:34:53 schrieb Johannes Sixt:
> If you look around in the code, you'll find more *cough* initializations
> *cough* like this. They are written this way for a reason: they avoid
> unwarranted compiler warnings "'foo' may be used uninitialized". Are you
> saying that this warning is not triggered anymore after your change?
>
I don't get a warning after my change.
But I'm using on this system a quite old gcc (4.3.1).
I'll recompile git with a more recent gcc and see what happens.
Just for clarification:
"int cmp = cmp;"
*suppresses* only the warning but "cmp" is still uninitialized?
(I did'nt know this trick before.)
//richard
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2010-01-15 11:02 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-01-14 23:29 [PATCH 2/2] Fix variable initialization in insert_packed_refs() Richard Weinberger
2010-01-15 7:34 ` Johannes Sixt
2010-01-15 11:02 ` Richard Weinberger
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).