public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Guenther <rguenther@suse.de>
To: Mark Mitchell <mark@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH][C++/Java] Get rid of the walk_subtrees langhook
Date: Mon, 20 Aug 2007 11:18:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.64.0708201315010.13885@s68.fhfr.qr> (raw)
In-Reply-To: <46B66A3E.8050403@codesourcery.com>

On Sun, 5 Aug 2007, Mark Mitchell wrote:

> Richard Guenther wrote:
> 
> > 2007-07-26  Richard Guenther  <rguenther@suse.de>
> > 
> > 	* tree.c (WALK_SUBTREE): Call walk_tree_1.
> > 	(walk_type_fields): Take lh parameter.
> 
> This is OK, with one change: I don't think "walk_tree_lh" is a mnemonic
> name for the type of the supplemental walker function.  Perhaps
> "walk_subtree_fn", like "walk_tree_fn", is better.  In any case, the
> typedef should have a comment saying what the varios parameters are.

walk_subtree_fn isn't any better I think (walk_tree_lh was supposed to
mean _langhook ;)).  The walk_tree_lh function has the same signature
as the (old) walk_tree function, so walk_tree_fn would be a match, but
that is already used...  Initially I didn't expose the signature with
a typedef, but writing the long prototype everywhere isn't any better.

I added a comment before the typedef and left the name in place
(I volunteer to change it to sth else if anyone has a good idea as
a followup).

> With those changes, the patch is fine, thanks!

Thanks,
Richard.

-- 
Richard Guenther <rguenther@suse.de>
Novell / SUSE Labs
SUSE LINUX Products GmbH - Nuernberg - AG Nuernberg - HRB 16746 - GF: Markus Rex

      reply	other threads:[~2007-08-20 11:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-26 14:32 Richard Guenther
2007-07-26 16:35 ` Andrew Haley
2007-08-06  0:24 ` Mark Mitchell
2007-08-20 11:18   ` Richard Guenther [this message]

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=Pine.LNX.4.64.0708201315010.13885@s68.fhfr.qr \
    --to=rguenther@suse.de \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=mark@codesourcery.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).