From: Russell King <rmk@arm.linux.org.uk>
To: aeb@veritas.com (Andries Brouwer)
Cc: rusty@linuxcare.com.au, tigran@veritas.com,
linux-kernel@vger.kernel.org, Andries.Brouwer@cwi.nl
Subject: Re: [PATCH] removal of "static foo = 0"
Date: Sat, 25 Nov 2000 21:07:08 +0000 (GMT) [thread overview]
Message-ID: <200011252107.VAA02744@raistlin.arm.linux.org.uk> (raw)
In-Reply-To: <20001125211939.A6883@veritas.com> from "Andries Brouwer" at Nov 25, 2000 09:19:39 PM
Andries Brouwer writes:
> What a strange reaction. If I write
>
> static int foo;
>
> this means that foo is a variable, local to the present compilation unit,
> whose initial value is irrelevant because it will be assigned to before use.
Wrong. The initial value is well-defined. Go and read any C standard you
choose. Any C standard you care. You will find out something really
interesting. I can guarantee that you will find out that it will be
initialised to zero. Unconditionally. No question. Absolutely.
> It is a bad programming habit to depend on this zero initialization.
Why? Again, it is WELL defined, and is WELL defined in any C standard.
> Indeed, very often, when you have a program that does something
> you need to change it so that it does that thing a number of times.
> Well, put a for- or while-loop around it. But wait! The second time
> through the loop certain variables need to be reinitialized. Which ones?
> The ones that were initialized explicitly in your first program.
> Make the program into a function in a larger one. Same story.
Your point here is as clear as mud.
> If it is your intention to destabilize then you need not read the following.
> But let us assume that you try to make a perfect system.
There is absolutely NO destabilisation going on here. Get a grip, read the
C standards, read the C startup code. Then come back with something more
relevent.
_____
|_____| ------------------------------------------------- ---+---+-
| | Russell King rmk@arm.linux.org.uk --- ---
| | | | http://www.arm.linux.org.uk/personal/aboutme.html / / |
| +-+-+ --- -+-
/ | THE developer of ARM Linux |+| /|\
/ | | | --- |
+-+-+ ------------------------------------------------- /\\\ |
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-25 21:37 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-25 20:19 [PATCH] removal of "static foo = 0" Andries Brouwer
2000-11-25 21:07 ` Russell King [this message]
2000-11-25 21:29 ` Andries Brouwer
2000-11-26 1:19 ` Russell King
2000-11-25 22:11 ` Herbert Xu
2000-11-25 22:46 ` Andries Brouwer
2000-11-25 22:53 ` James A Sutherland
2000-11-25 23:55 ` Tim Waugh
2000-11-26 3:10 ` James A Sutherland
2000-11-26 10:37 ` Tigran Aivazian
2000-11-26 14:52 ` Philipp Rumpf
2000-11-28 0:01 ` Peter Samuelson
2000-11-27 4:00 ` Michael Meissner
2000-11-25 23:02 ` Jeff Garzik
2000-11-26 2:08 ` Andries Brouwer
2000-11-26 9:22 ` Martin Mares
2000-11-25 23:33 ` Herbert Xu
2000-11-27 10:03 ` Helge Hafting
2000-11-27 20:33 ` Albert D. Cahalan
2000-11-27 22:57 ` Russell King
2000-11-29 1:46 ` Albert D. Cahalan
2000-11-29 3:21 ` Peter Samuelson
2000-11-29 7:25 ` Russell King
2000-11-25 22:27 ` Tigran Aivazian
2000-11-26 1:32 ` Andries Brouwer
2000-11-26 2:11 ` Georg Nikodym
2000-11-26 4:25 ` Alan Cox
2000-11-26 5:01 ` John Alvord
2000-11-26 5:10 ` Andre Hedrick
2000-11-26 6:22 ` Keith Owens
2000-11-26 6:28 ` Andre Hedrick
2000-11-26 10:43 ` Tigran Aivazian
2000-11-26 10:52 ` Tigran Aivazian
2000-11-24 7:47 ` Pavel Machek
2000-11-26 14:32 ` bert hubert
2000-11-26 10:52 ` Rogier Wolff
2000-11-26 14:13 ` Philipp Rumpf
2000-11-26 15:19 ` Georg Nikodym
2000-11-26 20:47 ` H. Peter Anvin
2000-11-27 21:12 ` Kai Henningsen
2000-11-26 6:21 ` Werner Almesberger
-- strict thread matches above, loose matches on Subject: below --
2000-11-26 15:15 Adam J. Richter
2000-11-26 17:53 Elmer Joandi
2000-11-26 18:36 ` Alexander Viro
2000-11-26 19:11 ` Elmer Joandi
2000-11-26 22:49 ` Rogier Wolff
2000-11-27 5:56 Adam J. Richter
2000-11-27 8:41 ` Werner Almesberger
2000-11-27 8:39 ` David S. Miller
2000-11-27 9:08 ` Werner Almesberger
2000-11-27 17:21 ` Andrea Arcangeli
2000-11-27 17:36 ` Michael Meissner
2000-11-27 19:06 ` Andrea Arcangeli
2000-11-27 19:34 ` Richard B. Johnson
2000-11-28 0:28 ` Andrea Arcangeli
2000-11-28 11:25 ` Horst von Brand
2000-11-28 3:10 ` kumon
2000-11-28 3:28 ` Andrea Arcangeli
2000-11-28 3:35 ` Alexander Viro
2000-11-28 4:15 ` Michael Meissner
2000-11-28 9:55 ` Andreas Schwab
2000-11-28 15:16 ` Andrea Arcangeli
2000-11-28 16:09 ` Andreas Schwab
2000-11-28 19:29 ` Andrea Arcangeli
2000-11-28 16:44 ` Michael Meissner
2000-11-27 21:27 ` Marcus Sundberg
2000-11-27 18:11 ` Richard B. Johnson
2000-11-27 18:01 ` Michael Meissner
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=200011252107.VAA02744@raistlin.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=Andries.Brouwer@cwi.nl \
--cc=aeb@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@linuxcare.com.au \
--cc=tigran@veritas.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