[devel] Revised manual paragraph about use of 'NO' macros.

This commit is contained in:
Glenn Randers-Pehrson
2011-07-12 10:28:02 -05:00
parent a5e5547679
commit d0797f5b53
2 changed files with 8 additions and 8 deletions

View File

@@ -4214,10 +4214,10 @@ if the feature is supported or:
/*#undef PNG_feature_SUPPORTED*/ /*#undef PNG_feature_SUPPORTED*/
if it is not. Library code consistently checks for the 'SUPPORTED' macro. if it is not. Library code consistently checks for the 'SUPPORTED' macro.
It does not, and should not, check for the 'NO' macro which will not It does not, and libpng applications should not, check for the 'NO' macro
normally be defined even if the feature is not supported. The 'NO' macros which will not normally be defined even if the feature is not supported.
are only used internally for setting the corresponding 'SUPPORTED' macros The 'NO' macros are only used internally for setting or not setting the
or not. corresponding 'SUPPORTED' macros.
Compatibility with the old names is provided as follows: Compatibility with the old names is provided as follows:

View File

@@ -5169,10 +5169,10 @@ if the feature is supported or:
/*#undef PNG_feature_SUPPORTED*/ /*#undef PNG_feature_SUPPORTED*/
if it is not. Library code consistently checks for the 'SUPPORTED' macro. if it is not. Library code consistently checks for the 'SUPPORTED' macro.
It does not, and should not, check for the 'NO' macro which will not It does not, and libpng applications should not, check for the 'NO' macro
normally be defined even if the feature is not supported. The 'NO' macros which will not normally be defined even if the feature is not supported.
are only used internally for setting the corresponding 'SUPPORTED' macros The 'NO' macros are only used internally for setting or not setting the
or not. corresponding 'SUPPORTED' macros.
Compatibility with the old names is provided as follows: Compatibility with the old names is provided as follows: