Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Thiago Jung Bauermann <bauerman@br.ibm.com>
Cc: gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [rfa] misc fixes and improvements to Python code.
Date: Sat, 21 Mar 2009 03:05:00 -0000	[thread overview]
Message-ID: <m3ocvvelhx.fsf@fleche.redhat.com> (raw)
In-Reply-To: <1237146352.316.23.camel@localhost.localdomain> (Thiago Jung Bauermann's message of "Sun\, 15 Mar 2009 16\:45\:52 -0300")

>>>>> "Thiago" == Thiago Jung Bauermann <bauerman@br.ibm.com> writes:

Thiago> This patch brings some fixes and improvements from the Python
Thiago> branch to code which was already committed in HEAD. The
Thiago> descriptions in the ChangeLog are good enough. I'll only note
Thiago> that "keyword arguments" means calling a function specifying
Thiago> an optional argument by it's name, as in "gdb.some_function
Thiago> (foo, bar=baz)".

Thiago> Ok?

This is ok.

Do you think we should use keyword arguments universally?  I was
thinking we probably should, but I think I noticed a single-argument
function without them, and I was wondering if we should bother with
those.

Thiago> 	(valpy_binop): Use `break' to exit from the TRY_CATCH block.

I've been wishing somebody would write a gcc plugin to check cleanups
and this sort of thing as well :-)

Tom


  reply	other threads:[~2009-03-21  1:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-15 20:08 Thiago Jung Bauermann
2009-03-21  3:05 ` Tom Tromey [this message]
2009-03-21  8:03   ` Thiago Jung Bauermann
2009-03-23 17:38     ` Tom Tromey
2009-03-23 14:45 ` Thiago Jung Bauermann
2009-03-23 18:14   ` Tom Tromey
2009-03-23 20:31   ` Eli Zaretskii

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=m3ocvvelhx.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=bauerman@br.ibm.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