From: Johan Hedberg <johan.hedberg@nokia.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Device Configuration D-Bus services
Date: Tue, 25 Oct 2005 15:06:46 +0300 [thread overview]
Message-ID: <20051025120646.GA26339@localhost.localdomain> (raw)
In-Reply-To: <3013cac80510250452j702622acw98ed9abef758bca1@mail.gmail.com>
On Tue, Oct 25, 2005, Eduardo Rocha wrote:
> The point is, as we have merged the main operations in two functions (set
> and get), so we have to identify the operation by an integer or by a string
> constant. It seems that a string is better for python binding (can anyone
> confirm that?).
At least by using strings it would be much easier to understand what the
client code is doing, e.g. if you compare
SetProperty("page-timeout", 10)
vs.
SetProperty(3, 10)
So, I vote for using strings instead of integers.
Johan
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-10-25 12:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-19 13:06 [Bluez-devel] Device Configuration D-Bus services Claudio Takahasi
2005-10-24 21:00 ` Eduardo Rocha
2005-10-24 21:23 ` Eduardo Rocha
2005-10-24 21:34 ` Marcel Holtmann
2005-10-25 11:52 ` Eduardo Rocha
2005-10-25 12:06 ` Johan Hedberg [this message]
2005-10-25 18:30 ` Eduardo Rocha
2005-10-27 0:33 ` Marcel Holtmann
2005-10-27 0:32 ` Marcel Holtmann
2005-10-25 12:05 ` Claudio Takahasi
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=20051025120646.GA26339@localhost.localdomain \
--to=johan.hedberg@nokia.com \
--cc=bluez-devel@lists.sourceforge.net \
/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