RE: Typedef inconsistency for gsize and gssize

["Banginwar, Rajesh" <rajesh banginwar intel com>]

> 
> What we try to do is to to match the type of size_t on the system;
> for 64-bit platforms, that isn't really a problem ... size_t will
> be 'unsigned long', but on 32-bit platforms it could either by
> 'unsigned int' or 'unsigned long'.
> 

So, on 32 bit platforms, why not typedef it as 'unsigned long'? Should
LSB do that (as it applies only to Linux systems so far)?

> (Matching the type prevents certain warnings when passing a size_t
> to a function expecting a gsize or vice-versa.)
> 
> So, the most accurate definition you could give is
> 'typedef gsize size_t', except that glib.h does *not* include
> stddef.h so it's not literally that in the header files.

Is that an option then? What was the reason for not including stddef
explicitely?

> 
> Regards,
> 					Owen