Re: [ft-devel] Fwd: buiding ttfautohint with cmake?

[Martin Gieseking]

I also vote for TTF_autohint_done. :-) Currently, I don't see the need
to expose the internal memory management through the API.

Martin


Am 13.12.2017 um 15:57 schrieb Cosimo Lupo:
> IMO, what matters is not which specific memory allocator/deallocator is
> used (whether the defaults, or user provided ones), but that they match
> with one another (they are defined by the same library).
> 
> That’s why I like the simplicity of a TTF_autohint_done function.
> 
> That’s just a one liner.
> 
> 
> --
> 
> 
> Cosimo
> 
> 
> Il 13 dic 2017, 13:44 +0000, Werner LEMBERG , ha scritto:
>>
>> Hello Tom!
>>
>>
>>> Have you considered CFFI? [1]
>>>
>>> This might make things a little easier, but I am not sure since I
>>> don't have as much experience with that as I do ctypes. Or are you
>>> more or less married to ctypes?
>>
>> Well, I guess this doesn't make a difference on the ttfautohint
>> library side... So I still have to decide whether to add pointers to
>> allocation and deallocation functions, or to add an explicit
>> `TTF_autohint_done' function.
>>
>>
>> Werner
> 
> 
> _______________________________________________
> Freetype-devel mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/freetype-devel
>