From: Lucas De Marchi <lucas.demarchi@profusion.mobi>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [BlueZ v3 00/10] gdbus: Better D-Bus introspection
Date: Mon, 30 Apr 2012 10:37:00 -0300 [thread overview]
Message-ID: <CAMOw1v6O0nsSqx3drJrCtsAFB4Dm5st2ANVyKFdSLejp6m1AUg@mail.gmail.com> (raw)
In-Reply-To: <CABBYNZKNN4Fy4wrnWv45Kg1KdRddv3JdkmKK2ezpOVtXaVZdcQ@mail.gmail.com>
On Mon, Apr 30, 2012 at 7:34 AM, Luiz Augusto von Dentz
<luiz.dentz@gmail.com> wrote:
> Hi Lucas,
>
> On Mon, Apr 30, 2012 at 12:40 AM, Lucas De Marchi
> <lucas.demarchi@profusion.mobi> wrote:
>>
>> Since we are using '[' and ']' only internally. I don't see a problem
>> with that. If D-Bus start using it we can change later. Of course it's
>> better to convince D-Bus guys to reserve that, but IMO this shouldn't
>> be a blocker.
>>
>> From the chars you suggested, only '@' seems reasonable and I can
>> change to this char if we agree on it.
>
> Either way IMO it is ugly to mess around with the signature but
> perhaps it is the only alternative we have.
There are other ways, but they have shortcomings, too -> the other 2
approaches that I sent to this ML have the shortcoming that in C it's
not possible to initialize flexible array members in a nested context.
>
> I wonder how other binding works in this regard, or they always have
> to depend on a xml file that describes the interface? iirc that used
> to be the case for GTK and QT, perhaps python is the only one that can
> really make use of this in runtime as d-feet seems to be able to use
> this information already.
As far as I checked, what glib does is to maintain the arguments in a
separate array (http://developer.gnome.org/gio/stable/gio-D-Bus-Introspection-Data.html#GDBusMethodInfo-struct).
This implies that for each method we need to declare the arguments in
a separate structure, not nested as we are doing now.
Lucas De Marchi
prev parent reply other threads:[~2012-04-30 13:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-27 21:14 [BlueZ v3 00/10] gdbus: Better D-Bus introspection Lucas De Marchi
2012-04-27 21:14 ` [BlueZ v3 01/10] gdbus: return if method signature is malformed Lucas De Marchi
2012-04-27 21:14 ` [BlueZ v3 02/10] gdbus: do not call memset for terminating NUL Lucas De Marchi
2012-04-27 21:14 ` [BlueZ v3 03/10] gdbus: save copy of undecorated signature Lucas De Marchi
2012-04-27 21:14 ` [BlueZ v3 04/10] gdbus: use argument name in method introspection Lucas De Marchi
2012-04-27 21:14 ` [BlueZ v3 05/10] gdbus: add decorated signature to arguments Lucas De Marchi
2012-04-27 21:14 ` [BlueZ v3 06/10] gdbus: add decorated signature to return values Lucas De Marchi
2012-04-27 21:14 ` [BlueZ v3 07/10] gdbus: add Deprecated annotation to introspection Lucas De Marchi
2012-04-27 21:14 ` [BlueZ v3 08/10] gdbus: add Method.NoReply " Lucas De Marchi
2012-04-27 21:14 ` [BlueZ v3 09/10] Constify GDBus method tables Lucas De Marchi
2012-04-27 21:14 ` [BlueZ v3 10/10] Constify GDBus signal tables Lucas De Marchi
2012-04-29 11:52 ` [BlueZ v3 00/10] gdbus: Better D-Bus introspection Luiz Augusto von Dentz
2012-04-29 21:40 ` Lucas De Marchi
2012-04-30 10:34 ` Luiz Augusto von Dentz
2012-04-30 13:37 ` Lucas De Marchi [this message]
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=CAMOw1v6O0nsSqx3drJrCtsAFB4Dm5st2ANVyKFdSLejp6m1AUg@mail.gmail.com \
--to=lucas.demarchi@profusion.mobi \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.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;
as well as URLs for NNTP newsgroup(s).