mewin/libpng
1
0
Fork 0
mirror of https://git.code.sf.net/p/libpng/code.git synced 2025-07-10 18:04:09 +02:00
Code Issues Projects Releases Wiki Activity

[libpng17] Updated documentation about functions deprecated in 1.6.0

Browse Source
This commit is contained in:
Glenn Randers-Pehrson 2012-12-16 16:47:07 -06:00
parent 4b90a8d416
commit 5e07dc6970
2 changed files with 10 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
libpng-manual.txt
View File

@ -4931,8 +4931,10 @@ The following API are now DEPRECATED:
png_info_init_3()
png_convert_to_rfc1123() which has been replaced
with png_convert_to_rfc1123_buffer()
png_data_freer()
png_malloc_default()
png_free_default()
png_reset_zstream()
The following have been removed:
png_get_io_chunk_name(), which has been replaced
@ -4971,7 +4973,9 @@ XIII. Changes to Libpng from version 1.6.x to 1.7.x
Some functions that were deprecated in libpng-1.6.0 were removed:
png_reset_zstream(),
png_info_init_3(),
and png_data_freer() and its associated flags.
png_data_freer() and its associated flags,
png_malloc_default(),
and png_free_default().
The 8-bit compose and rgb_to_grayscale operatons were made more accurate.
While these did not introduce API incompatibility, there may be differences

6
libpng.3
View File

@ -5909,8 +5909,10 @@ The following API are now DEPRECATED:
png_info_init_3()
png_convert_to_rfc1123() which has been replaced
with png_convert_to_rfc1123_buffer()
png_data_freer()
png_malloc_default()
png_free_default()
png_reset_zstream()
The following have been removed:
png_get_io_chunk_name(), which has been replaced
@ -5949,7 +5951,9 @@ it possible to skip IDAT chunks in the sequential reader.
Some functions that were deprecated in libpng-1.6.0 were removed:
png_reset_zstream(),
png_info_init_3(),
and png_data_freer() and its associated flags.
png_data_freer() and its associated flags,
png_malloc_default(),
and png_free_default().
The 8-bit compose and rgb_to_grayscale operatons were made more accurate.
While these did not introduce API incompatibility, there may be differences