A repository that has original sources for patches used in the Arch User Repository package called "mutter-performance".
https://aur.archlinux.org/packages/mutter-performance
58b0028b52
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. |
||
|---|---|---|
| cogl | ||
| doc | ||
| pango | ||
| Makefile.am | ||