On 10/17/2017 8:10 AM, Beman Dawes via Boost wrote:
I find it very irritating that VC++ does not support #warning, and have opened a feature request:
https://visualstudio.uservoice.com/forums/121579-visual-studio?query=Add%20C...
The last time #warning was suggested it was rejected because not enough people voted for it. So please consider upvoting it on the above link.
The lack of #warning affects Boost libraries in that developers avoid otherwise useful warnings because of the hassle for using an extension not supported by VC++.
Maybe someone could promote #warning as an official addition to the C++ standard ? I realize doing anything further with the C++ preprocessor may be seen as negative because C++ usually attempts de-emphasize the preprocessor, but adding #warning officially could hardly be controversial or complicated ( famous last words ). As for vc++ I find it a little amusing that we should ask them to add #warning to their preprocessor when their preprocessor is not standard conforming to begin with. Maybe, like congressman, we could tie the #warning "appropriations" to the general "bill" for creating a conformant preprocessor and submit it to Microsoft as a "congressional" demand <g>.
--Beman