diff options
author | Michael Drake <tlsa@netsurf-browser.org> | 2021-11-19 11:55:15 +0000 |
---|---|---|
committer | Michael Drake <tlsa@netsurf-browser.org> | 2021-11-19 12:37:05 +0000 |
commit | c240b835fe6e3774237b6d968ddb405c8085690f (patch) | |
tree | 301142c95943c9a83b0e00778c89e2d0032940c2 /test | |
parent | 15670d3d0e3dcf9db168244428cab8e43460251a (diff) | |
download | libnsgif-c240b835fe6e3774237b6d968ddb405c8085690f.tar.gz libnsgif-c240b835fe6e3774237b6d968ddb405c8085690f.tar.bz2 |
GIF: Unify insufficient data error codes.
There is no difference in what the client needs to do.
If there are displayable frames, they can display them.
Otherwise more data is needed.
Internally only `GIF_INSUFFICIENT_DATA` is used now.
To remove the `GIF_INSUFFICIENT_FRAME_DATA` could make existing
client applications fail to compile, so it is left as an alias
to the same value.
At some point the API will be changed drastically, but for now
I want existing applications to still build.
Diffstat (limited to 'test')
-rw-r--r-- | test/decode_gif.c | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/test/decode_gif.c b/test/decode_gif.c index 64387ef..52d73b6 100644 --- a/test/decode_gif.c +++ b/test/decode_gif.c @@ -113,9 +113,6 @@ static void warning(const char *context, gif_result code) fprintf(stderr, "%s failed: ", context); switch (code) { - case GIF_INSUFFICIENT_FRAME_DATA: - fprintf(stderr, "GIF_INSUFFICIENT_FRAME_DATA"); - break; case GIF_FRAME_DATA_ERROR: fprintf(stderr, "GIF_FRAME_DATA_ERROR"); break; |