The stb_image library is written in highly compact C code for compability with different projects, which is great for beginners to quickly throw it into a project. After writing my own functions for saving and loading wave sounds however, I began thinking about how many nice settings and features this minimal connection to a replacable image library has costed. Improving code readability and getting rid of deprecation warnings from compilers might also be a good idea for long term maintenance.
This is not urgent, because stb_image will probably work for many years without problems, but a memory-safe high-level implementation with good documentation would be a easier to maintain for future generations and allow a tighter coupling to take full advantage of the features offered in the file formats.
The stb_image library is written in highly compact C code for compability with different projects, which is great for beginners to quickly throw it into a project. After writing my own functions for saving and loading wave sounds however, I began thinking about how many nice settings and features this minimal connection to a replacable image library has costed. Improving code readability and getting rid of deprecation warnings from compilers might also be a good idea for long term maintenance.
This is not urgent, because stb_image will probably work for many years without problems, but a memory-safe high-level implementation with good documentation would be a easier to maintain for future generations and allow a tighter coupling to take full advantage of the features offered in the file formats.