[cairo] Should we expose cairo_toy_font_face_create?

[Carl Worth]

On Fri, 24 Feb 2006 19:07:11 -0500 (EST), Behdad Esfahbod wrote:
> 
> How about "simple"?

I've actually been _wanting_ to squeeze "toy" into the API
sometime. We often talk about the toy API and I've imagined users
overhearing that talk and going to look for it and not finding it.

In fact, "simple" is what the internal name was before I renamed it to
"toy" last August.

> By not having the enum however, you can have private types ;).

Heh.

Well, we could just not put it in the public enum either. But the user
can easily get this value by legitimate calls so it seems we should
advertise something rather than just handing out a mystic value.

> Also, for forward compatibility, please note in docs for all
> these enums that new values may be added in later versions...
> We had a similar problem when adding new values to an enum in
> glib, Pango would assert_not_reached, simply not expecting
> anything to be added in the future...

Good point. Will do.

-Carl



-------------- 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/20060224/38f9073d/attachment.pgp