From 23c9bbf77f49aec7d61590d399d0423fe44dd3b3 Mon Sep 17 00:00:00 2001 From: Havoc Pennington Date: Tue, 1 Jul 2003 20:21:35 +0000 Subject: 2003-07-01 Havoc Pennington * doc/dbus-specification.sgml: clarify the format of a type code, change suggested by Jim Blandy --- doc/dbus-specification.sgml | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) (limited to 'doc') diff --git a/doc/dbus-specification.sgml b/doc/dbus-specification.sgml index 8b3a1d36..68a71cec 100644 --- a/doc/dbus-specification.sgml +++ b/doc/dbus-specification.sgml @@ -218,13 +218,12 @@ Header field names MUST consist of 4 non-nul bytes. The field name is - NOT nul terminated; it occupies exactly 4 bytes. Following the name, - the field MUST have a type code, and then a properly-aligned value - of that type. - See for a description - of how each type is encoded. If an implementation sees a header - field name that it does not understand, it MUST ignore - that field. + NOT nul terminated; it occupies exactly 4 bytes. Following the name, the + field MUST have a type code represented as a single unsigned byte, and + then a properly-aligned value of that type. See for a description of how each type + is encoded. If an implementation sees a header field name that it does + not understand, it MUST ignore that field. @@ -288,9 +287,10 @@ Message Arguments - The message body is made up of arguments. Each argument - is a type code, followed by the value of the argument - in a type-dependent format. + The message body is made up of arguments. Each argument is a type code, + represented by a single unsigned byte, followed by the aligned value of + the argument in a type-dependent format. Alignment padding between the + typecode and the value is initialized to zero. -- cgit