Andreas Mohr wrote:
This should have gone into a comment right there because it's
a very normal reaction to immediately question code like that,
so the code should properly defend itself by default ;)
IOW just the usual "do coding as obvious as possible, then properly comment
everything else that isn't obvious".
Maybe something like
/* called in a loop, but missing glyph shouldn't happen often
so we don't want to call it outside the loop, always */
Andreas Mohr
Makes sense now that you mention it.
Jeff Latimer
