This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [C++ Patch] Improve delete_sanity locations

From: Paolo Carlini <paolo dot carlini at oracle dot com>
To: David Malcolm <dmalcolm at redhat dot com>, Jason Merrill <jason at redhat dot com>, "gcc-patches at gcc dot gnu dot org" <gcc-patches at gcc dot gnu dot org>
Date: Fri, 2 Aug 2019 14:02:45 +0200
Subject: Re: [C++ Patch] Improve delete_sanity locations
References: <5b89d4fe-88b7-b51b-fc0e-11833bde2c34@oracle.com> <4d895279-d74e-7437-7d7c-30c2bd0927b6@redhat.com> <1564601975.9730.30.camel@redhat.com>

Hi,

On 31/07/19 21:39, David Malcolm wrote:

[snip]

I don't care for "cp_expr_loc_or_loc".

By "_or_here" do you mean "or input_location"?

Calling it "cp_expr_loc_or_input_location" would spell out what it
does, but would be rather long.

Thanks for your feedback. At this point I don't feel very strongly aboutthe issue, and, well, hopefully it's just temporary material, but Itested the below which proposes the name cp_expr_loc_or_input_loc. Seemsa good balance to me. What do you think?


Cheers, Paolo.

/////////////////

Attachment: patch_cp_expr_loc_or_input_loc
Description: Text document

Follow-Ups:
- Re: [C++ Patch] Improve delete_sanity locations
  - From: David Malcolm

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]