>> # One of my concern (except of the code size) is that APIs like
>> # FT_Get_Path_From_Stream() is a bad idea from the viewpoint of
>> # software design, and it can encourage badly- designed FT2
>> # clients. FT_Get_MemInfo_From_Stream() might not be so bad, but it
>> # could conflict with the philosophy of the encapsulation of
>> # FT_Stream.
>
> I definitely had this concern myself when the Get_Path API was being
> discussed. I think the stream meminfo is different however. And as
> Werne pointed out, seems like getting the path is also something
> people find useful anyway (oh and you have no idea how useful it
> would be for debugging!), so lets add them.
Since Pango & Cairo & HarfBuzz are the main candidate applications
which would use such functions, can you provide your ideas how such an
interface could look like?
Werner
_______________________________________________
Freetype-devel mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/freetype-devel
