On Fri, Aug 8, 2014 at 12:31 PM, Nils Chr. Brause
wrote:
> Up until now, newly created wl_proxys (with proxy_create or
> wl_proxy_create_for_id) are not initialized properly after memory
> allocation. The wl_display object in contrast is. To prevent giving
> uninitialized data to the user (e.g. u
On Fri, 08 Aug 2014 18:31:25 +0200
"Nils Chr. Brause" wrote:
> Up until now, newly created wl_proxys (with proxy_create or
> wl_proxy_create_for_id) are not initialized properly after memory
> allocation. The wl_display object in contrast is. To prevent giving
> uninitialized data to the user (e.
On Fri, 8 Aug 2014 14:55:43 -0700
Jason Ekstrand wrote:
> I think this is ok. To my knowledge, no one is re-binding wl_display or
> even relying on that global being exposed.
I cannot imagine any reason to advertize wl_display as a global
either. Personally I have always thought the version of
On Fri, 08 Aug 2014 16:06:04 -0700
Bill Spitzak wrote:
> This is my understanding. And this is one of the big confusing points
> when trying to figure out the Wayland api, but I think there are good
> reasons for it. The only real problem is that the auto-generated
> documentation is not handl
On Fri, 8 Aug 2014 12:59:49 -0700
Bill Spitzak wrote:
> These are a series of changes, you can pick and choose from them if you don't
> like them all.
>
> There are fixes to the parser so that "x=5mm" and "bool=false" and other
> constucts are errors
> rather than doing unintuitive things.
>
