From: Tom Tromey <tromey@redhat.com>
To: Iain Buclaw <ibuclaw@gdcproject.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 4/5] Implement D primitive types in GDB
Date: Fri, 10 Jan 2014 21:18:00 -0000 [thread overview]
Message-ID: <87zjn34jtq.fsf@fleche.redhat.com> (raw)
In-Reply-To: <CABOHX+ev=xWQsjh0CavYTP0Bu2F-UkRjvBMjaf+6XyiZG_RFaQ@mail.gmail.com> (Iain Buclaw's message of "Fri, 10 Jan 2014 12:57:53 +0000")
>>>>> "Iain" == Iain Buclaw <ibuclaw@gdcproject.org> writes:
Iain> Comments duly noted and rebased patch. Though I have a feeling you
Iain> may ask to comment non-static functions in their declared headers. :)
That's like the one thing gdb doesn't have a pedantic standard for.
Yet :) At some point Stan will presumably push in his doxygen change
and then we'll start converting to that.
Iain> +/* Mapping of all D basic data types into the language vector. */
Iain> +enum d_primitive_types {
Space between the comment and the definition.
Yeah, that pedantic.
Iain> + d_primitive_type_cent, /* signed 128 bit integer */
Comments have to start with an upper-case letter and end with a period
and two spaces.
Iain> +/* Implements the la_language_arch_info language_defn routine
Iain> + for language D. */
Iain> +static void
Blank line here and elsewhere.
This is ok with those nits fixed.
Tom
next prev parent reply other threads:[~2014-01-10 21:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 13:11 Iain Buclaw
2014-01-09 18:33 ` Tom Tromey
2014-01-09 18:41 ` Iain Buclaw
2014-01-10 12:57 ` Iain Buclaw
2014-01-10 21:18 ` Tom Tromey [this message]
2014-01-11 16:39 ` Iain Buclaw
2014-01-13 20:03 ` Tom Tromey
2014-01-18 18:23 ` Iain Buclaw
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=87zjn34jtq.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=ibuclaw@gdcproject.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 read-only IMAP folder(s) and NNTP newsgroup(s).