From: Adrian Bunk <bunk@stusta.de>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Oleg Verych <olecom@flower.upol.cz>
Subject: Re: why test for "__GNUC__"?
Date: Mon, 30 Oct 2006 04:38:34 +0100 [thread overview]
Message-ID: <20061030033834.GJ27968@stusta.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0610291223520.31583@localhost.localdomain>
On Sun, Oct 29, 2006 at 12:37:36PM -0500, Robert P. J. Day wrote:
> On Sun, 29 Oct 2006, Adrian Bunk wrote:
>
> > On Sun, Oct 29, 2006 at 04:17:51PM +0000, Oleg Verych wrote:
> > >...
> > > On 2006-10-29, Robert P. J. Day wrote:
> > >>...
> > > And if you can, please, help with development or bugs, not this.
> >
> > Cleanup of the kernel source is also a valuable task (and as a side
> > effect it even sometimes finds bugs).
>
> on that note, i realize that most of my postings are addressing
> nitpicky/aesthetic issues that don't actually *hurt* anything, but for
> someone who's clawing his way through the kernel code for the first
> time, a lot of it is unnecessarily confusing.
>
> for better or worse, i generally assume that whatever i'm looking at
> is there for a *reason* and i might spend some time puzzling over a
> bit of code until it finally dawns on me that it's just historical
> cruft that has no value. it's not a bug, it just doesn't *do*
> anything anymore.
>
> in my case, it's sometimes easier to spot things like this since i'm
> following along in some book, like r. love's "linux kernel
> development." so when he writes that the linux kernel is wedded to
> gcc, and yet i see tests for "__GNUC__" throughout the code, my little
> antenna stalks perk up a bit.
>...
Looking at it, it seems I might look through them - some of them seem to
be really pointless.
> in any event, i'm most emphatically *not* (yet) at the level where i'm
> going to be able to contribute bleeding-edge code. but i'm certainly
> capable of poring over the *existing* code and pointing out the places
> that might lead someone to mutter, "what the hell...?"
>
> maybe there's a better forum for me to make these observations. i'm
> open to suggestions. i've made a list of these observations and i'd
> be happy to send them to the right person.
There's also the kernelnewbies list.
But your emails are not as bad as you think - the email starting this
thread as well as your earlier emails regarding menu structure etc. have
some value (and they are better than many other questions that hit
this list...).
> rday
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2006-10-30 3:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-29 11:13 Robert P. J. Day
2006-10-29 11:44 ` Jan Engelhardt
2006-10-29 12:44 ` Robert P. J. Day
2006-10-29 12:05 ` Alexey Dobriyan
2006-10-29 15:48 ` Robert P. J. Day
2006-10-29 16:17 ` Oleg Verych
2006-10-29 17:18 ` Adrian Bunk
2006-10-29 17:37 ` Robert P. J. Day
2006-10-29 18:23 ` Oleg Verych
2006-10-30 3:38 ` Adrian Bunk [this message]
2006-10-30 5:08 ` Kyle Moffett
2006-10-29 16:59 ` Valdis.Kletnieks
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=20061030033834.GJ27968@stusta.de \
--to=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=olecom@flower.upol.cz \
--cc=rpjday@mindspring.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
all inboxes | Powered by JetHome®