>>> Also, I just ran into the issue of `FT_Stream_OpenGzip' requiring
>>> the stream to having a valid `memory' field, which is not provided
>>> by `FT_Stream_OpenMemory' (for obvious reasons).
>>
>> This looks like a bug, both in documentation (which doesn't mention
>> it) and implementation (which doesn't correctly check for a valid
>> `memory' field).
After some thinking I now believe that we have to solve this issue in
a different way. A stream should always be created with
`FT_Stream_New'; among other things it ensures that there is a valid
`stream->memory' field. If you encounter a situation where `memory'
is NULL it seems that either `FT_Stream_New' wasn't properly called,
or `stream' wasn't set up correctly. Can you investigate that?
So please commit the `memory' checks but not the documenation fix,
which is an internal detail Joe User shouldn't take care of (as Alexei
correctly states).
Werner
_______________________________________________
Freetype-devel mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/freetype-devel
