wire format array contents

2013-09-27 Thread Micah Nordland
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The wire format spec includes an array type: array Starts with 32-bit array size in bytes, followed by the array contents verbatim, and finally padding to a 32-bit boundary. What type are the contents? The protocol description only uses the

[PATCH docs] Clarify the wire format array specification

2013-09-27 Thread Micah Nordland
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Addition to the wire format specification array type definition to say that array contents are defined by whatever is using the array. diff --git a/doc/publican/sources/Protocol.xml b/doc/publican/sources/Protocol.xml index b79b6be..039d875 100644 -

Re: [PATCH docs] Clarify the wire format array specification

2013-09-27 Thread Micah Nordland
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/27/2013 05:02 PM, Bill Spitzak wrote: I think it is confusing to call this an array, rather than perhaps a block or something. When I read the documentation I thought the array consisted of N pieces of data in wire format, not N bytes.

conversion from double to fixed and back fails with certain values

2013-09-26 Thread Micah Nordland
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The value 3568.005 is not correctly converted back from fixed. The following patch to tests/fixed-test.c demonstrates. Is this expected behavior? diff --git a/tests/fixed-test.c b/tests/fixed-test.c index 739a3b1..89ec188 100644 - ---

Re: conversion from double to fixed and back fails with certain values

2013-09-26 Thread Micah Nordland
OK, I are there any parts of the Wayland spec where this might cause problems/make things interesting? -- Sent from my Android device with K-9 Mail. Please excuse my brevity.___ wayland-devel mailing list wayland-devel@lists.freedesktop.org