On Sun, Feb 25, 2018 at 4:21 PM, Werner LEMBERG <w...@gnu.org> wrote: >>> Certainly, if you are going to dynamically allocate a slot for it. >>> I tried to avoid that. >> >> Totally untested, but why wouldn't this work? >> >> [...] >> >> - if ( FT_List_Find( &loader->composites, >> - FT_UINT_TO_POINTER( glyph_index ) ) ) >> + if ( FT_List_Find( &loader->composites, index ) ) > > How shall this work? You are going to store pointers to integers in a > list. As a consequence, two identical integers can have different > pointers. How will you then find out whether such an integer is > already in the list?
I was thinking about glyph indexes as they appear in the glyf table, which have fixed offsets/pointers. You, however, talk about table reallocations. Does current implementation work for ellipsis …? _______________________________________________ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
