From: Tom Tromey <tromey@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] constify to_attach
Date: Wed, 21 May 2014 22:55:00 -0000 [thread overview]
Message-ID: <87lhtug2sy.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20140521220529.GP22822@adacore.com> (Joel Brobecker's message of "Wed, 21 May 2014 15:05:29 -0700")
Joel> I searched the GDB wiki about C99, and there were no hits. I am
Joel> wondering if we should be starting a list of C99 features we think
Joel> would be worthwhile to allow. This one would definitely be on my list!
I like designated init, "//" comments, varargs macros, "for (int i = ...",
_Bool, and even declaring variables at point of use (but I know others
dislike this one).
I see C99 as a convenience upgrade. None of those things will markedly
improve gdb's quality, they may just make the hacking marginally nicer.
For me of course C99 is the runner-up choice ...
Joel> Perhaps we can also list some of the issues that would prevent us
Joel> from adopting a subset of C99 (Eg: fear if missing checks against
Joel> disallowed features)?
IIRC there was some concern about library issues.
Or maybe that GCC doesn't implement all the IEEE additions?
I don't really remember now. It's in the list archives.
Tom
next prev parent reply other threads:[~2014-05-21 22:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-21 18:21 Tom Tromey
2014-05-21 18:58 ` Tom Tromey
2014-05-21 21:22 ` Joel Brobecker
2014-05-21 21:36 ` Tom Tromey
2014-05-21 22:05 ` Joel Brobecker
2014-05-21 22:55 ` Tom Tromey [this message]
2014-05-21 19:45 ` Pedro Alves
2014-06-04 17:09 ` Tom Tromey
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=87lhtug2sy.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.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