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

El vie, 20-03-2009 a las 19:02 -0600, Tom Tromey escribió:
> >>>>> "Thiago" == Thiago Jung Bauermann <bauerman@br.ibm.com> writes:
> Thiago> Ok?
> 
> This is ok.

Thanks, committed.

> 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.

Well, I added keyword arguments only to functions which have two or more
optional arguments, so that you can use the last optional argument
without having to fill the earlier ones.

We could add keyword arguments to other functions as well, but I don't
know of a practical advantage there, it would be only for simmetry, I
suppose.

> 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 :-)

Can someone write a gcc plugin adding exceptions as a syntax add-on to
the C language? :-)
-- 
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center


  reply	other threads:[~2009-03-21  3:16 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
2009-03-21  8:03   ` Thiago Jung Bauermann [this message]
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=1237605392.6897.27.camel@localhost.localdomain \
    --to=bauerman@br.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --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