analysis: FALSE/0 used in pointer context
authorDamien Lespiau <damien.lespiau@intel.com>
Thu, 27 May 2010 07:28:29 +0000 (08:28 +0100)
committerDamien Lespiau <damien.lespiau@intel.com>
Tue, 1 Jun 2010 11:08:18 +0000 (12:08 +0100)
commit52a78a7220650f4d8b1da75ff942cfede1248d20
treef220dba61d920dd71f2583cb26054e3d52cba108
parent9d428278f7b073f4221113026a18aaf4a6e25420
analysis: FALSE/0 used in pointer context

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.
13 files changed:
clutter/clutter-actor.c
clutter/clutter-backend.c
clutter/clutter-path.c
clutter/clutter-script-parser.c
clutter/clutter-script.c
clutter/clutter-shader-types.c
clutter/cogl/cogl/cogl-buffer.c
clutter/cogl/cogl/cogl-journal.c
clutter/cogl/cogl/cogl-path.c
clutter/cogl/cogl/cogl-texture-2d-sliced.c
clutter/cogl/cogl/cogl-vertex-buffer.c
clutter/cogl/cogl/driver/gl/cogl-program.c
clutter/x11/clutter-x11-texture-pixmap.c