mirror of
https://github.com/brl/mutter.git
synced 2024-11-13 01:36:10 -05:00
52a78a7220
While this is totally fine (0 in the pointer context will be converted in the right internal NULL representation, which could be a value with some bits to 1), I believe it's clearer to use NULL in the pointer context. It seems that, in most case, it's more an overlook than a deliberate choice to use FALSE/0 as NULL, eg. copying a _COGL_GET_CONTEXT (ctx, 0) or a g_return_val_if_fail (cond, 0) from a function returning a gboolean. |
||
---|---|---|
.. | ||
clutter-backend-x11-private.h | ||
clutter-backend-x11.c | ||
clutter-backend-x11.h | ||
clutter-device-manager-x11.c | ||
clutter-device-manager-x11.h | ||
clutter-event-x11.c | ||
clutter-input-device-x11.c | ||
clutter-input-device-x11.h | ||
clutter-stage-x11.c | ||
clutter-stage-x11.h | ||
clutter-x11-enum-types.c.in | ||
clutter-x11-enum-types.h.in | ||
clutter-x11-texture-pixmap.c | ||
clutter-x11-texture-pixmap.h | ||
clutter-x11.h | ||
clutter-x11.pc.in | ||
Makefile.am |