[libpng16] Minor editing of README

This commit is contained in:
Glenn Randers-Pehrson 2014-10-17 09:31:48 -05:00
parent 8ba743d8d2
commit e557fd7c44

19
README
View File

@ -23,7 +23,7 @@ earlier versions if you are using a shared library. The type of the
png_uint_32, which will affect shared-library applications that use png_uint_32, which will affect shared-library applications that use
this function. this function.
To avoid problems with changes to the internals of png_info_struct, To avoid problems with changes to the internals of png info_struct,
new APIs have been made available in 0.95 to avoid direct application new APIs have been made available in 0.95 to avoid direct application
access to info_ptr. These functions are the png_set_<chunk> and access to info_ptr. These functions are the png_set_<chunk> and
png_get_<chunk> functions. These functions should be used when png_get_<chunk> functions. These functions should be used when
@ -33,14 +33,15 @@ directly, to avoid such problems in the future.
It is important to note that the APIs did not make current programs It is important to note that the APIs did not make current programs
that access the info struct directly incompatible with the new that access the info struct directly incompatible with the new
library, through libpng-1.2.x. In libpng-1.4.x, which was meant to library, through libpng-1.2.x. In libpng-1.4.x, which was meant to
be a transitional release, the png struct and the info struct can still be a transitional release, members of the png_struct and the
be accessed, but the compiler will issue a warning about deprecated info_struct can still be accessed, but the compiler will issue a
usage. Since libpng-1.5.0, direct access to these structs is not warning about deprecated usage. Since libpng-1.5.0, direct access
allowed, and the definitions of the structs reside in private to these structs is not allowed, and the definitions of the structs
pngstruct.h and pnginfo.h header files that are not accessible to reside in private pngstruct.h and pnginfo.h header files that are not
applications. It is strongly suggested that new programs use the new accessible to applications. It is strongly suggested that new
APIs (as shown in example.c and pngtest.c), and older programs be programs use the new APIs (as shown in example.c and pngtest.c), and
converted to the new format, to facilitate upgrades in the future. older programs be converted to the new format, to facilitate upgrades
in the future.
**** ****
Additions since 0.90 include the ability to compile libpng as a Additions since 0.90 include the ability to compile libpng as a