DEPRECATED: wl_resource as a transparent structure

[Jason Ekstrand]

Wayland Devs,
After digging further into what this would actually imply, it looks
like the cascade of changes that would be required isn't worth it.
While this may happen in the distant future, we're not going to take
away wl_resource just yet.  Specifically, EGL relies on it and
changing it right now would be bad.  I'm sorry for any confusion,
--Jason Ekstrand

On Tue, Mar 19, 2013 at 1:15 PM, Jason Ekstrand <jason at jlekstrand.net> wrote:
> Devs,
> This is to let you know that we are going to try and depreciate
> wl_resource.  I talked with Kristian about it this morning on IRC.
> This does not mean that wl_resource will be completely gone, just that
> it will become an opaque pointer like wl_proxy; you will not be able
> to directly access any of its members like you could before.  I am
> alerting everyone to this so that you can prepare for the change.  The
> wl_resource structure will still be available in libwayland version
> 1.1.
>
> From now on, you should avoid using wl_resource directly.  I just sent
> a patch to the ML that adds accessors for all the important parts of
> wl_resource which should be used instead of accessing fields directly.
>  I'm going to be working on patching the current code-base but would
> appreciate it if you did not write new code that I have to patch.
>
> My next Wayland project will be to begin removing direct uses of
> wl_resource from weston to prepare it for the change. I hope to have
> this done so that wl_resource can be removed from the public API in
> time for 1.2.  That said, the exact timeline is up in the air.
>
> Thanks,
> --Jason Ekstrand