From: Doug Evans <dje@google.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Tom Tromey <tromey@redhat.com>, gdb <gdb@sourceware.org>
Subject: Re: C99
Date: Wed, 17 Jul 2013 17:54:00 -0000 [thread overview]
Message-ID: <CADPb22TzFy=V7kkkTgO3szjbFPYHdpnkcOaF5XeY7BroucX7YQ@mail.gmail.com> (raw)
In-Reply-To: <838v153kyj.fsf@gnu.org>
On Tue, Jul 16, 2013 at 8:48 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Tom Tromey <tromey@redhat.com>
>> Date: Tue, 16 Jul 2013 14:51:36 -0600
>>
>> 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.
>
> I can understand the C99 requirement (although many GNU projects still
> don't) where it allows better programming practices. But the //
> comment style doesn't make anything easier or more efficient, it's
> just different.
Well, yes and no.
It can be what some contributors are used to. Saying // is not
allowed is another quirky imposition one has to remember. To me, it
doesn't get in the way of reading code the way other differences can
(indentation, SymbolSpellingStyle, etc.). Note that we're already
using // in code: While it's in /* ... */ comments in, e.g. queue.h
and gnulib's string.h, for obvious simplicity reasons the code in the
comments isn't less readable. Plus if we import code from elsewhere
we don't want to be in the business of changing // to /**/.
next prev parent reply other threads:[~2013-07-17 17:54 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
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 ` Doug Evans [this message]
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='CADPb22TzFy=V7kkkTgO3szjbFPYHdpnkcOaF5XeY7BroucX7YQ@mail.gmail.com' \
--to=dje@google.com \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
--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