Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Chris Moller <cmoller@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Patch for PR 10728
Date: Wed, 03 Feb 2010 18:23:00 -0000	[thread overview]
Message-ID: <m3y6jarxej.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4B68FD51.9090209@redhat.com> (Chris Moller's message of "Tue, 02 	Feb 2010 23:36:33 -0500")

Chris> Is there a cleanup for stuff that gets done in
Chris> _initialize_cp_valprint()?

There may be, but I wouldn't bother with it.
It is ok to initialize an obstack and then leave it around forever.

Chris> The problem is I don't know which eps are relevant.  Does anything
Chris> other than C/C++ have the statics problem?

Yeah, Java does at least.  I'm not sure about other languages, but I
assume so.

However, Java doesn't call into the code you're modifying, so it
shouldn't matter for this patch.

>> The formatting is weird here; the first statement doesn't appear to have
>> changed, but has gratuitous formatting changes,

Chris> I just thought it made the stmts more readable.

Usually we recommend formatting changes as separate patches.  Personally
I'm more inclined to just leave bad formatting alone, to avoid adding
noise to the history, but that's just me.  Also, the result still has to
conform to the GNU standards.

Tom


  reply	other threads:[~2010-02-03 18:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-02 21:57 Chris Moller
2010-02-02 23:57 ` Tom Tromey
2010-02-03  4:36   ` Chris Moller
2010-02-03 18:23     ` Tom Tromey [this message]
2010-02-03  4:52   ` Chris Moller
  -- strict thread matches above, loose matches on Subject: below --
2010-01-27 19:41 Chris Moller
2010-01-28 18:09 ` Tom Tromey
2010-01-28 18:38   ` Chris Moller
2010-01-28 20:03     ` Tom Tromey
2010-02-03 20:41       ` Chris Moller
2010-02-03 20:50         ` 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=m3y6jarxej.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=cmoller@redhat.com \
    --cc=gdb-patches@sourceware.org \
    /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