[PATCH wayland 4/4] Make wl_resource opaque

Signed-off-by: Jason Ekstrand --- src/wayland-server.c | 25 + src/wayland-server.h | 40 2 files changed, 33 insertions(+), 32 deletions(-) diff --git a/src/wayland-server.c b/src/wayland-server.c index 13b9dc8..3fe9dea 100644 --

[PATCH wayland 3/4] Add accessor functions for wl_resource and deprecate wl_client_add_resource

This is the first step towards making wl_resource an opaque pointer type. Signed-off-by: Jason Ekstrand --- src/wayland-server.c | 44 ++-- src/wayland-server.h | 29 +++-- src/wayland-shm.c| 35 +++--

[PATCH wayland 2/4] Add support for flags in the wl_map API and add a WL_MAP_ENTRY_LEGACY flag

The implementation in this commit allows for one bit worth of flags. If more flags are desired at a future date, then the wl_map implementation will have to change but the wl_map API will not. Signed-off-by: Jason Ekstrand --- src/wayland-client.c | 12 ++-- src/wayland-private.h | 13

[PATCH wayland 1/4] Add a "side" field and some sanity checks to wl_map.

The original wl_map implementation did no checking to ensures that ids fell on the correct side of the WL_SERVER_ID_START line. This meant that a client could send the server a server ID and it would happily try to use it. Also, there was no distinction between server-side and client-side in wl_m

[PATCH wayland 0/4] Make wl_resource opaque

This commit series provides a path for making the wl_resource structure opaque and special-casing wl_buffer. The first patch in the series is a primarily a bugfix patch for wl_buffer and is a good idea anyway. The last patch in the series should not be applied until all direct wl_resource accesse

Re: [PATCH wayland] Clean up the internals of wl_map

Ignore these. Turns out I was trying to fix the wrong issue. New patches to come -- Jason Ekstrand On Wed, May 29, 2013 at 10:06 PM, Jason Ekstrand wrote: > This commit cleans up the internals of wl_map by splitting it into two > wl_simple_maps. This both makes the internals cleaner and also