[cairo] Adding a boolean type
Carl Worth
cworth at cworth.org
Tue Feb 1 09:29:16 PST 2005
On Tue, 01 Feb 2005 12:16:37 -0500, Carl Worth wrote:
> That sounds like consensus to me.
Or not...
> cairoint.h:
> #define CAIRO_FALSE 0
> #define CAIRO_TRUE 1
Owen and I had previously recommended TRUE/FALSE for internal
usage. And I think I still prefer that. [*]
I really don't have much of a problem just using 1/0 to initialize or
return cairo_bool_t values. But if people really want defines,
CAIRO_TRUE/FALSE does look a bit cluttered for something that's hidden
in the implementation.
If the plan is to avoid ever putting cairo_bool_t parameters in the
public API, then we should be able to contain whatever portability
problems arise in using TRUE/FALSE just in the implementation.
And we can decide what to do for exporting cairo_bool_t parameter
values if the need ever arises.
-Carl
[*] I blame my lack of coherence today on a bad cold from which I'm
still recovering.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.freedesktop.org/archives/cairo/attachments/20050201/884fc0f3/attachment.pgp
More information about the cairo
mailing list