Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org,  Tom Tromey <tromey@redhat.com>
Cc: "Pierre Muller" <muller@ics.u-strasbg.fr>,
	 "'Eli Zaretskii'" <eliz@gnu.org>
Subject: Re: replace typedef_print with a language method
Date: Sat, 27 Sep 2008 19:51:00 -0000	[thread overview]
Message-ID: <200809272051.16151.pedro@codesourcery.com> (raw)
In-Reply-To: <m3vdx46ibh.fsf@fleche.redhat.com>

Hi Tom,

This looks good to me except for the minor comment below.

On Wednesday 10 September 2008 18:07:14, Tom Tromey wrote:

> @@ -3312,7 +3312,7 @@ print_symbol_info (domain_enum kind, struct symtab
> *s, struct symbol *sym, /* Typedef that is not a C++ class */
>    if (kind == TYPES_DOMAIN
>        && SYMBOL_DOMAIN (sym) != STRUCT_DOMAIN)
> -    typedef_print (SYMBOL_TYPE (sym), sym, gdb_stdout);
> +    current_language->la_print_typedef (SYMBOL_TYPE (sym), sym, gdb_stdout);

For consistency with the other language print methods, could you please
add a LA_PRINT_TYPEDEF macro to language.h, and use it instead of calling
current_language->la_print_typedef directly?  Okay with that change.

For extra consistency, I'd be mildly inclined to leave typedef_print in
place, similarly to type_print, but I've no strong opinion on that.

As a side note, there's a ada_typedef_print function in
ada-typeprint.c, but it isn't used anywhere, even pre-your
patch.

:REVIEWMAIL:

Thanks,

-- 
Pedro Alves


  reply	other threads:[~2008-09-27 19:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-10 15:15 RFA: " Tom Tromey
2008-09-10 15:41 ` Pierre Muller
2008-09-10 17:09   ` Tom Tromey
2008-09-27 19:51     ` Pedro Alves [this message]
2008-09-27 21:29       ` Tom Tromey
2008-09-27 21:30         ` Tom Tromey

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=200809272051.16151.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=muller@ics.u-strasbg.fr \
    --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