From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Marius Groeger <mgroeger@sysgo.com>
Cc: "Sébastien Couret" <sebastiencouret@aol.com>,
linux-mtd@lists.infradead.org
Subject: Re: Silent GCC4.0 warning
Date: Wed, 14 Sep 2005 15:06:57 +0200 [thread overview]
Message-ID: <20050914130657.GA26387@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <Pine.LNX.4.63.0509141426340.26040@mag.sysgo.com>
On Wed, 14 September 2005 14:34:47 +0200, Marius Groeger wrote:
> On Wed, 14 Sep 2005, Jörn Engel wrote:
>
> >"if your write it portable in the first place" sounds nice, but noone
> >really knows what that means, before the acid test happens.
>
> I think this is a weak argument in this context. Sticking to the
> standards should always be a prime directive for any programmer.
> Moreover, /if/ I follow your argument: it's very unlikely something
> happens to the semantics of (char*)buf + i, compared to the likelihood
> of a future GCC discovering honour and making the extensions harder to
> access.
Yeah, ok. But then again, void* arithmetic is likely the single best
gcc extension. We should spread this feature into more compilers and
into the next C standard instead of crippling ourselves.
Commercial companies with paying customers may have a different view
on this subject. But since I don't receive a monthly cheque to worry
about such problems, please understand my ignorance. ;)
Jörn
--
You can take my soul, but not my lack of enthusiasm.
-- Wally
prev parent reply other threads:[~2005-09-14 13:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-13 16:45 Silent GCC4.0 warning Sébastien Couret
2005-09-13 23:06 ` Jörn Engel
2005-09-14 7:05 ` Marius Groeger
2005-09-14 9:26 ` Jörn Engel
2005-09-14 10:04 ` Marius Groeger
2005-09-14 12:03 ` Jörn Engel
2005-09-14 12:34 ` Marius Groeger
2005-09-14 13:06 ` Jörn Engel [this message]
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=20050914130657.GA26387@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=linux-mtd@lists.infradead.org \
--cc=mgroeger@sysgo.com \
--cc=sebastiencouret@aol.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