diff options
| author | Simon McVittie <simon.mcvittie@collabora.co.uk> | 2014-10-01 16:11:59 +0100 |
|---|---|---|
| committer | Tom Gundersen <teg@jklm.no> | 2014-10-02 08:25:21 +0200 |
| commit | d20a3daaa79edfa4c8d84d243f2a98c82dddd5c6 (patch) | |
| tree | aa7304483b8a4a4b812bff609f73eacf8a4018bc /src/libsystemd/sd-bus/PORTING-DBUS1 | |
| parent | e1ffdb90d92849a2bb5c27ebc035e7f885ffdafb (diff) | |
sd-bus: use terms from the D-Bus Specification a bit more
D-Bus' type hierarchy as described in the spec is:
\- basic
\- fixed type (u, i, etc.)
\- string-like type (s, o, g)
\- container
Someone seems to have referred to basic types as "simple types" at
some point, but that term isn't defined in the D-Bus Specification,
and seems redundant.
So far I haven't renamed functions that use "trivial" in their names
to mean "fixed type", to avoid confusion about whether a struct of
constant length, like (iu), is a fixed type. The answer is that it is
fixed-length, but is not a "fixed type", so I can see that something
like bus_type_is_fixed() might be ambiguous.
Diffstat (limited to 'src/libsystemd/sd-bus/PORTING-DBUS1')
| -rw-r--r-- | src/libsystemd/sd-bus/PORTING-DBUS1 | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/src/libsystemd/sd-bus/PORTING-DBUS1 b/src/libsystemd/sd-bus/PORTING-DBUS1 index 63c345b11a..81e94132b3 100644 --- a/src/libsystemd/sd-bus/PORTING-DBUS1 +++ b/src/libsystemd/sd-bus/PORTING-DBUS1 @@ -156,11 +156,11 @@ multiple items. Some restrictions apply however: contained in the payload, as well is immediately before framing of a Gvariant, as well after as any padding bytes if there are any. The padding bytes must be wholly contained in the preceding - PAYLOAD_VEC/PAYLOAD_MEMFD item. You may not split up simple types - nor arrays of trivial types. The latter is necessary to allow APIs - to return direct pointers to linear chunks of fixed size trivial - arrays. Examples: The simple types "u", "s", "t" have to be in the - same payload item. The array of simple types "ay", "ai" have to be + PAYLOAD_VEC/PAYLOAD_MEMFD item. You may not split up basic types + nor arrays of fixed types. The latter is necessary to allow APIs + to return direct pointers to linear arrays of numeric + values. Examples: The basic types "u", "s", "t" have to be in the + same payload item. The array of fixed types "ay", "ai" have to be fully in contained in the same payload item. For an array "as" or "a(si)" the only restriction however is to keep each string individually in an uninterrupted item, to keep the framing of each |