Emil Velikov emil.l.veli...@gmail.com writes:
Strictly speaking the xcb_connection_has_error() might be sufficient,
yet the documentation does not mention what will happen if NULL is fed
to the function.
Keep things explicit, which will allow us to remove the dri2_dpy-conn
checking with the
On 29 July 2015 at 18:17, Matt Turner matts...@gmail.com wrote:
On Wed, Jul 29, 2015 at 9:19 AM, Emil Velikov emil.l.veli...@gmail.com
wrote:
Strictly speaking the xcb_connection_has_error() might be sufficient,
yet the documentation does not mention what will happen if NULL is fed
to the
On Wed, Jul 29, 2015 at 12:19 PM, Emil Velikov emil.l.veli...@gmail.com wrote:
Strictly speaking the xcb_connection_has_error() might be sufficient,
yet the documentation does not mention what will happen if NULL is fed
to the function.
Keep things explicit, which will allow us to remove the
On Wed, Jul 29, 2015 at 9:19 AM, Emil Velikov emil.l.veli...@gmail.com wrote:
Strictly speaking the xcb_connection_has_error() might be sufficient,
yet the documentation does not mention what will happen if NULL is fed
to the function.
Keep things explicit, which will allow us to remove the
Strictly speaking the xcb_connection_has_error() might be sufficient,
yet the documentation does not mention what will happen if NULL is fed
to the function.
Keep things explicit, which will allow us to remove the dri2_dpy-conn
checking with the next commit.
Signed-off-by: Emil Velikov
