From: Dodji Seketeli <dodji@redhat.com>
To: "Manuel López-Ibáñez" <lopezibanez@gmail.com>
Cc: Gcc Patch List <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH diagnostics/fortran] Handle two locations for the same diagnostic. Convert all gfc_warning_1 and gfc_notify_std_1 calls
Date: Mon, 18 May 2015 07:35:00 -0000 [thread overview]
Message-ID: <874mnaz6b0.fsf@redhat.com> (raw)
In-Reply-To: <CAESRpQDshYAF6tJ1uoHBL=4ZRR028+yGcWcZY_XJY_o0XzUJ+w@mail.gmail.com> ("Manuel \=\?utf-8\?B\?TMOzcGV6LUliw6HDsWV6Iidz\?\= message of "Fri, 15 May 2015 13:47:24 +0200")
Manuel López-Ibáñez <lopezibanez@gmail.com> writes:
> On 15 May 2015 at 10:39, Dodji Seketeli <dodji@redhat.com> wrote:
>> Manuel López-Ibáñez <lopezibanez@gmail.com> writes:
>>> -/* Expand the location of this diagnostic. Use this function for consistency. */
>>> +/* Return the location associated to this diagnostic. WHICH specifies
>>
>> Here, I think only the 'W' (in WHICH) should be uppercase.
>
> I'm following the convention that parameter names are uppercase in the
> description of functions.
Oh, okay then. My bad. Sorry.
>>> /* The type of a text to be formatted according a format specification
>>> along with a list of things. */
>>> struct text_info
>>> {
>>> +public:
>>
>> As this is a struct, the 'public' here is not necessary, as the members
>> are public by default.
>
> I have a very poor memory for such details ;), since we are using
> 'private:' already, does it really hurt to be explicit and use
> 'public:' here?
It doesn't hurt, per se. But I think it's a very common style to avoid
specifying the 'public' in this case, so I'd rather just remove it, yes.
[...]
OK to commit with this change then.
Cheers,
--
Dodji
next prev parent reply other threads:[~2015-05-18 7:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-20 20:01 Manuel López-Ibáñez
2015-05-03 22:31 ` Manuel López-Ibáñez
2015-05-07 20:16 ` Dodji Seketeli
2015-05-08 22:13 ` Manuel López-Ibáñez
2015-05-15 8:41 ` Dodji Seketeli
2015-05-15 12:23 ` Manuel López-Ibáñez
2015-05-18 7:35 ` Dodji Seketeli [this message]
2015-05-06 7:21 Tobias Burnus
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=874mnaz6b0.fsf@redhat.com \
--to=dodji@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=lopezibanez@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).