On Fri, 1 Dec 2017 17:08:15 +0000 Daniel Stone <dan...@fooishbar.org> wrote:
> Hi, > > On 10 July 2017 at 19:28, Emmanuel Gil Peyrot > <emmanuel.pey...@collabora.com> wrote: > > The current behaviour when WAYLAND_DEBUG is set is to print “array”, > > which is quite unhelpful. > > > > This patch prints a list of the bytes present in the array. It doesn’t > > try to interpret it as uint32_t or anything, leaving that to the reader > > because this information isn’t present in the protocol description. > > To be honest, I'm not really wild about this one. All the array users > I know of (key/button, xdg surface states) are uint32_t. I'd prefer to > add a pretty-printing hint to the protocol - this could specify how to > interpret arrays, and also scratch my long-standing itch of printing > uints with %x rather than %u when it makes sense to ... Hi, just a side note, if you start working on that, do also think of bindings for (strongly) typed languages. ISTR requests to add type information so that better bindings could be generated, and the problem was where to stop defining the type system. I'm pretty sure if printing hints are added, people will use them for bindings, whether we wanted or not. Thanks, pq
pgpsDmJfJbwAS.pgp
Description: OpenPGP digital signature
_______________________________________________ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
