4 ms·
I've had to remove deprecation warnings because downstream users enabled warnings as errors in their releases. They could fix newer versions of their software,
by slavik81 5y ago
I've had to remove deprecation warnings because downstream users enabled warnings as errors in their releases. They could fix newer versions of their software, but being able to build old versions on new dependencies was a requirement.
The solution was to introduce a deprecation message that wasn't technically a warning, and warn about the upcoming depreciation warning.
- kazinator 5y agoThe solution with a compiler that has a GCC-like interface is to use -Werror=<specific-thing>. Not -Werror globally for all warnings that currently exist and that will exist henceforth.