diff options
author | Robin Watts <robin.watts@artifex.com> | 2014-03-11 19:04:17 +0000 |
---|---|---|
committer | Robin Watts <robin.watts@artifex.com> | 2014-03-17 19:38:40 +0000 |
commit | 551de42088c58dc69fba06fb53e36c2ddb12367f (patch) | |
tree | f073b5ac7d3dee2de2f5609a13fd9c47e605d3d8 /scripts/glyphlist.txt | |
parent | 8fdcb140930c3027841af28a4632ce6d23aa44b6 (diff) | |
download | mupdf-551de42088c58dc69fba06fb53e36c2ddb12367f.tar.xz |
Rework fz_streams.
Currently fz_streams have a 4K buffer within their header. The call
to read from a stream fills this buffer, resulting in more data being
pulled from any underlying stream than we might like. This causes
problems with the forthcoming 'leech' filter.
Here we simplify the fields available in the public stream header.
No specific buffer is given; simply the read and write pointers.
The underlying 'read' function is replaced by a 'next' function
that makes the next block of data available and returns the first
character of it (or EOF).
A caller to the 'next' function should supply the maximum number of
bytes that it knows it will need (possibly not now, but eventually).
This enables the underlying stream to efficiently decode just enough.
The underlying stream is free to return fewer, or a greater number
if it wants to.
The exact size of the 'block' of data returned will depend on the
filter in use and (possibly) the data therein.
Callers can get the currently available amount of data by calling
fz_available (but again should pass the maximum amount of data they know
they will need). The only time this will ever return 0 is if we have
hit EOF.
Diffstat (limited to 'scripts/glyphlist.txt')
0 files changed, 0 insertions, 0 deletions