ceb327789b
As per the const correctness rules, top-level const-ness of data in automatic scopes does not propagate outside of these scopes (unlike const-ness at lower levels, such as pointers to const data). Previously, const was used liberally, but inconsistently across the libpng codebase. Using const wherever applicable is not incorrect. However, _consistent_ use of const is difficult to maintain in such conditions. In conclusion, we shall continue to use const only where doing so is strictly necessary: 1. If a function guarantees that it will not modify an argument passed by pointer, the corresponding function parameter should be a pointer-to-const (const T *). 2. Static data should not be modified, therefore it should be const. Reference: Google C++ Style Guide https://google.github.io/styleguide/cppguide.html#Use_of_const |
||
|---|---|---|
| .. | ||
| arm-neon | ||
| conftest | ||
| examples | ||
| gregbook | ||
| libtests | ||
| mips-msa | ||
| oss-fuzz | ||
| pngminim | ||
| pngminus | ||
| pngsuite | ||
| powerpc-vsx | ||
| testpngs | ||
| tools | ||
| visupng | ||
| README.txt | ||
This "contrib" directory contains contributions which are not necessarily under the libpng license, although all are open source. They are not part of libpng proper and are not used for building the library, although some are used for testing the library via "make check".