[cairo] UserFontFace vs FtFontFace management (cairomm)
Jonathon Jongsma
jonathon at quotidian.org
Wed Dec 3 11:56:14 PST 2008
Behdad Esfahbod wrote:
> I'm not sure whether you are being lazy or the docs are so horribly bad :).
Yes, sorry about that. I was being lazy and realized it just after I had sent the email.
>> Now, regarding the unicode_to_glyph documentation you quoted above, the
>> fact that you overload the 'num_glyphs' parameter with a special
>> negative number sentinel makes it somewhat cumbersome to wrap cleanly in
>> languages that have better support for arrays.
>
> I agree that it's clumsy. It happened to offset for the fact that there is no
> public CAIRO_STATUS_UNIMPLEMENTED. The documentation is only for the C
> version. Your binding layer is free to do otherwise.
right
> The C interface is now written in stone. What we can do is to add a special
> cairo_status_t value for this case that will be interpreted as UNIMPLEMENTED
> only when used in this context. That's possible if you don't find any other
> solutions.
Yes, I had this thought as well. I'm working on a new implementation now, so I'll follow
up on this later if I run into any insurmountable issues with other approaches. Thanks
for your input.
--
jonner
More information about the cairo
mailing list