On Wed, Aug 21, 2019 at 12:20 AM Werner LEMBERG <w...@gnu.org> wrote: > > > >> Having a structure certainly reduces possible coding errors, but in > >> the end there is still a cast from one type to another, something > >> that disables type checking on the compiler level. > > > > The hooks are static, aren't they? Otherwise, how do you plan to > > document them? > > Not sure what you mean with `static'.
I would like to see a draft documentation for setting hooks. You will have to offer some constant preset structures, which will be fun to describe to users. They will fly from the finger tips, of course. Perhaps you will then offer predefined macros, which will be a way out of this mess. Then only then you will probably consider my idea of using a string alias, which will also work for in the environment variable, or even reconsider the single-renderer design. So please please please, start drafting documentation to fully appreciate what you have. _______________________________________________ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
