From: R.E.Wolff@BitWizard.nl (Rogier Wolff)
To: John Alvord <jalvo@mbay.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] removal of "static foo = 0"
Date: Sun, 26 Nov 2000 11:52:37 +0100 (MET) [thread overview]
Message-ID: <200011261052.LAA03592@cave.bitwizard.nl> (raw)
In-Reply-To: <3a219890.57346310@mail.mbay.net> from John Alvord at "Nov 26, 2000 05:01:03 am"
John Alvord wrote:
> On Sun, 26 Nov 2000 04:25:05 +0000 (GMT), Alan Cox
> <alan@lxorguk.ukuu.org.uk> wrote:
>
> >> AB> of changes that yield a negligable advantage and reduce stability
> >> AB> a tiny little bit. That is pushing Linux in the direction of this
> >> AB> abyss. You notice that the view gets better, and I get nervous.
> >>
> >> Can somebody stop this train load of bunk?
> >>
> >> Uninitialized global variables always have a initial value of
> >> zero. Static or otherwise. Period.
> >
> >That isnt what Andries is arguing about. Read harder. Its semantic differences
> >rather than code differences.
> >
> > static int a=0;
> >
> >says 'I thought about this. I want it to start at zero. I've written it this
> >way to remind of the fact'
> >
> >Sure it generates the same code
>
> It also says "I do not know much about the details of the kernel C
> environment. In particular I do not know that all static variables are
> initialized to 0 in the kernel startup. I have not read setup.S."
Nope. It doesn't say that. Maybe if you wrote the code. But if Andries
or I had written that line, it just says that when written the
programmer thought about the initial value, and that the initial value
matters on this variable.
It is a concise form of documentation. As Andries explained, this can
also be done with comments or with
static int a /* = 0 */;
However, I like the "=0" variant much better.
If you're worried about the inefficiency of the compiler, take it up
with the compiler guys. Or write an extra preprocessor step or
something like that.
Roger.
--
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2137555 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
* There are old pilots, and there are bold pilots.
* There are also old, bald pilots.
-
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-26 11:24 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
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 [this message]
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=200011261052.LAA03592@cave.bitwizard.nl \
--to=r.e.wolff@bitwizard.nl \
--cc=jalvo@mbay.net \
--cc=linux-kernel@vger.kernel.org \
/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