From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Pavel Roskin <proski@gnu.org>
Cc: Shawn Pearce <spearce@spearce.org>,
Junio C Hamano <junkio@cox.net>,
git@vger.kernel.org
Subject: Re: [PATCH] Remove more gcc extension usage.
Date: Mon, 10 Jul 2006 09:35:32 +0200 [thread overview]
Message-ID: <20060710073532.GA22573@lug-owl.de> (raw)
In-Reply-To: <1152514328.3504.58.camel@dv>
[-- Attachment #1: Type: text/plain, Size: 1176 bytes --]
On Mon, 2006-07-10 02:52:08 -0400, Pavel Roskin <proski@gnu.org> wrote:
> On Mon, 2006-07-10 at 08:25 +0200, Jan-Benedict Glaw wrote:
> > On Mon, 2006-07-10 02:22:03 -0400, Pavel Roskin <proski@gnu.org> wrote:
> > > This means that the Sun compiler has almost all c99 features used by git
> > > with just a little exception (initializers). I think it's fair that we
> > > fix this incompatibility. It's very very minor compared to what "gcc
> > > -std=c89 -pedantic" would have required.
> > ^^^^^^^^
> > You're kidding, aren't you?
[...]
> We can satisfy the Sun's compiler and yet retain flexible arrays and
> other c99 goodies.
>
> Maybe I'm missing your point (or you joke).
Why should we jump through the hoops to support an obsolete standard
because proprietary compilers don't stand today's standards?
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481 _ O _
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg _ _ O
für einen Freien Staat voll Freier Bürger" | im Internet! | im Irak! O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-07-10 7:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-08 18:34 [PATCH] Remove more gcc extension usage Shawn Pearce
2006-07-08 18:51 ` Junio C Hamano
2006-07-08 19:03 ` Shawn Pearce
2006-07-09 7:31 ` Jan-Benedict Glaw
2006-07-10 5:22 ` Shawn Pearce
2006-07-10 6:14 ` Jan-Benedict Glaw
2006-07-10 6:22 ` Pavel Roskin
2006-07-10 6:25 ` Jan-Benedict Glaw
2006-07-10 6:52 ` Pavel Roskin
2006-07-10 7:35 ` Jan-Benedict Glaw [this message]
2006-07-10 8:07 ` Pavel Roskin
2006-07-10 8:10 ` Junio C Hamano
2006-07-10 8:18 ` Jan-Benedict Glaw
2006-07-10 7:47 ` Junio C Hamano
2006-07-12 13:46 ` Paul Jakma
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=20060710073532.GA22573@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=proski@gnu.org \
--cc=spearce@spearce.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;
as well as URLs for NNTP newsgroup(s).