TO_UINT() will be
defined in the most obvious way possible, and on any reasonable
platform this will give you GPOINTER_TO_UINT(NULL) => 0.
(See the C FAQ for information about NULL and unreasonable platforms;
GTK+ basically requires a reasonable platform.)
I suspect that the GTK+ code depen
y in the hash table returns NULL if the key
isn't found, it's basically impossible to store a NULL
value. It makes life a lot simpler if that corresponds
to a ref count of 0, which I don't need to store.
> [EMAIL PROTECTED] wrote:
>
> > Is it possible to assume
I think so
glibconfig.h:
#define GPOINTER_TO_UINT(p) ((guint) (p))
#define GPOINTER_TO_INT(p) ((gint) (p))
but why would you need to make such an assumption?
Jim
[EMAIL PROTECTED] wrote:
> Is it possible to assume that
>
> GPOINTER_TO_UINT(NULL) == 0
>
> acros
Is it possible to assume that
GPOINTER_TO_UINT(NULL) == 0
across all platforms? Whether this is true or false, it
might also be a good thing to mention in the docs.
Ron Steinke
___
gtk-list mailing list
[EMAIL PROTECTED]
http://mail.gnome.org
