Damien Lespiau 58b0028b52 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.

2010-06-01 12:08:18 +01:00

..

cogl-context-driver.c

Remove mentions of the FSF address

2010-03-01 12:56:10 +00:00

cogl-context-driver.h

Remove mentions of the FSF address

2010-03-01 12:56:10 +00:00

cogl-defines.h.in

Remove mentions of the FSF address

2010-03-01 12:56:10 +00:00

cogl-feature-functions.h

Remove mentions of the FSF address

2010-03-01 12:56:10 +00:00

cogl-program.c

analysis: FALSE/0 used in pointer context

2010-06-01 12:08:18 +01:00

cogl-program.h

Remove mentions of the FSF address

2010-03-01 12:56:10 +00:00

cogl-shader-private.h

Remove mentions of the FSF address

2010-03-01 12:56:10 +00:00

cogl-shader.c

Remove mentions of the FSF address

2010-03-01 12:56:10 +00:00

cogl-texture-driver.c

Remove mentions of the FSF address

2010-03-01 12:56:10 +00:00

cogl.c

Remove mentions of the FSF address

2010-03-01 12:56:10 +00:00

Makefile.am

build: Add cogl-feature-functions.h to the dist

2009-11-18 14:43:46 +00:00