> If I was managing this project, I would certainly consider this an
> unacceptable approach / sequence of events.
Usually, I'm quite conservative, and Graham has provided a lot of
useful additions to the FreeType code. I trust him to fix that in due
course.
> Better to keep the inefficiency than (a) break the functionality,
> and (b) end up with code that is not obviously correct.
Uh, oh, you are extremely exaggerating. This is not helpful. Until
the bug report we weren't aware of problems, and Graham's change is in
since two months already, and the code is probably run by millions of
people...
It's easy to revert if no satisfying solution can be found.
Thanks for offering help, though.
Werner
_______________________________________________
Freetype-devel mailing list
Freetype-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype-devel
