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: Mon, 23 Mar 2009 17:38:00 -0000 [thread overview]
Message-ID: <m3fxh49m5w.fsf@fleche.redhat.com> (raw)
In-Reply-To: <1237605392.6897.27.camel@localhost.localdomain> (Thiago Jung Bauermann's message of "Sat\, 21 Mar 2009 00\:16\:32 -0300")
>>>>> "Thiago" == Thiago Jung Bauermann <bauerman@br.ibm.com> writes:
Tom> Do you think we should use keyword arguments universally? I was
Tom> thinking we probably should, but I think I noticed a single-argument
Tom> function without them, and I was wondering if we should bother with
Tom> those.
[...]
Thiago> We could add keyword arguments to other functions as well, but I don't
Thiago> know of a practical advantage there, it would be only for simmetry, I
Thiago> suppose.
Yeah.
I have thought about it a bit more. I think there are two possible
benefits to applying this to all functions. One is that it makes the
documentation simpler -- we can simply document that the argument
names in the docs are always part of the API. The other is that it
may make some code future-proof.
Neither of these seem all that strong to me. I think we can leave it
as-is for now. This is the more conservative approach, anyway, in
that we can always add keyword arguments later.
Thiago> Can someone write a gcc plugin adding exceptions as a syntax add-on to
Thiago> the C language? :-)
:)
Tom
next prev parent reply other threads:[~2009-03-23 17:36 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
2009-03-23 17:38 ` Tom Tromey [this message]
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=m3fxh49m5w.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