> You have to implement (and maintain) hooks instead of maintaining
> renderer modules. You are asking secondary libraries to implement
> hooks instead of the renderer module. There is nothing absolutely
> nothing easier, or more logical, or simpler. It buys you absolutely
> nothing!!!
I disagree.
> Given that hooks do not exist and have to be implemented, my
> question remains. Why hooks are better than modules? Werner, why?
Just imagine that a user wants to use the brand-new `foosvg' library
with FreeType. Using hooks, he can quickly write a few lines of code
to implement the hook callback functions, then registering them.
Done.
On the other hand, writing a new renderer module needs FreeType's
internal header files – which no user code should ever rely on.
I honestly don't know whether it works at all to load a user-compiled
module into FreeType. AFAICS, the library was not set up to manage
externally compiled modules.
Werner
_______________________________________________
Freetype-devel mailing list
Freetype-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/freetype-devel
