From: Doug Evans <dje@google.com>
To: John Gilmore <gnu@toad.com>
Cc: Mark Kettenis <mark.kettenis@xs4all.nl>,
Tom Tromey <tromey@redhat.com>, gdb <gdb@sourceware.org>
Subject: Re: C99? No, portability.
Date: Wed, 17 Jul 2013 22:38:00 -0000 [thread overview]
Message-ID: <CADPb22RucqKtyGhFG6z50ycaoYepwa+9HG_ejbK0Yg1OQTFtfg@mail.gmail.com> (raw)
In-Reply-To: <201307170811.r6H8BagN018382@new.toad.com>
On Wed, Jul 17, 2013 at 1:11 AM, John Gilmore <gnu@toad.com> wrote:
>> > So, I'd like to propose we allow the use of C99 in gdb. In particular I
>> > think we ought to require a C99 preprocessor -- enabling this particular
>> > patch to go in and also allowing the use of "//" comments.
>>
>> Perhaps it is time to move on and start requiring a C99 compiler for GDB.
>
> Mark said it correctly. This change would "require" a C99 compiler.
> Not just "allow the use of C99 in GDB".
>
> I recommend that you NOT break compatability with older compilers for
> gratuitous reasons. For example, I still run systems based on Red Hat
> 7.3, which use gcc-2.96. I can still compile modern GDB's on that
> system. (With the few portability patches below :-).)
gdb successfully moved from K&R to C89, so it's not like we haven't
been through this before.
C99 is 14 years old. How many people still require C89 vs how many
have long since moved on?
next prev parent reply other threads:[~2013-07-17 22:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 20:51 C99 Tom Tromey
2013-07-16 21:23 ` C99 Mark Kettenis
2013-07-16 21:40 ` C99 Doug Evans
2013-07-17 20:48 ` C99 Mark Kettenis
2013-07-17 21:12 ` C99 Doug Evans
2013-07-17 8:11 ` C99? No, portability John Gilmore
2013-07-17 22:38 ` Doug Evans [this message]
2013-07-18 15:27 ` John Kearney
2013-07-19 17:39 ` Doug Evans
2013-07-18 6:54 ` C99 Yao Qi
2013-07-17 3:49 ` C99 Eli Zaretskii
2013-07-17 17:54 ` C99 Doug Evans
2013-07-18 2:47 ` C99 Yao Qi
2013-07-18 6:46 ` C99 Doug Evans
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=CADPb22RucqKtyGhFG6z50ycaoYepwa+9HG_ejbK0Yg1OQTFtfg@mail.gmail.com \
--to=dje@google.com \
--cc=gdb@sourceware.org \
--cc=gnu@toad.com \
--cc=mark.kettenis@xs4all.nl \
--cc=tromey@redhat.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