From: Daniel Jacobowitz <drow@false.org>
To: Pierre Muller <muller@ics.u-strasbg.fr>
Cc: gdb-patches@sourceware.org
Subject: Re: [PING][Patch RFC] ARI changes for p-valprint.c
Date: Fri, 07 Sep 2007 11:58:00 -0000 [thread overview]
Message-ID: <20070907115845.GA19110@caradoc.them.org> (raw)
In-Reply-To: <001601c7f137$937f3070$ba7d9150$@u-strasbg.fr>
On Fri, Sep 07, 2007 at 12:12:20PM +0200, Pierre Muller wrote:
> I could commit these as pascal maintainer, but I would like to have
> feedback,
> especially about how to phrase the ChangeLog entry, I put a minimal here,
> but would like to know if more details are needed.
Yes, more details are needed. It should have a function-level
description of changes, except when you're making huge mechanical
changes.
> - deprecated_print_address_numeric (addr, 1, stream);
> + fputs_filtered (paddress(addr), stream);
Space before parentheses, please.
> @@ -217,7 +217,7 @@ pascal_val_print (struct type *type, con
> int is_this_fld;
>
> if (msymbol != NULL)
> - wsym = lookup_symbol (DEPRECATED_SYMBOL_NAME (msymbol),
> block,
> + wsym = lookup_symbol ((msymbol)->ginfo.name, block,
> VAR_DOMAIN, &is_this_fld, NULL);
>
> if (wsym)
No, please don't use the members directly. Replace this with one of
the other SYMBOL_*_NAME macros. Originally, this used to be
SYMBOL_NAME; then the others were introduced, and this one was
deprecated because it did not make clear what sort of name was
wanted. Since it is being passed to lookup_symbol,
SYMBOL_LINKAGE_NAME is probably best.
> + fputs_filtered (paddress(
Space again.
Looks fine otherwise. Sorry for not getting to it before.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-09-07 11:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-07 10:12 Pierre Muller
2007-09-07 11:58 ` Daniel Jacobowitz [this message]
2007-09-07 12:18 ` Pierre Muller
2007-09-07 12:20 ` 'Daniel Jacobowitz'
2007-09-07 12:36 ` Pierre Muller
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=20070907115845.GA19110@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=muller@ics.u-strasbg.fr \
/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