Re: [boost] improve <boost/config.hpp>
Am 07.03.2023 um 19:43 schrieb Peter Dimov via Boost:
Daniela Engert wrote:
Am 07.03.2023 um 19:19 schrieb Andrey Semashev via Boost:
On 3/7/23 21:11, John Maddock via Boost wrote:
Not every compiler defines these macros. Let alone, not every compiler properly implements what it advertises. I think it depends on the compiler - the current crop of the latest are pretty good at getting these right. Have MSVC started defining these macros yet? I see them in VS2017, but I don't know how complete they are. This complete:
https://www.boost.org/development/tests/develop/developer/output/teeks99-09-...
Cool, thanks Peter! BTW, this is the reason why we build (and use) Boost with our own build flags to enforce and announce maximum possible language conformance in msvc. The list reveals that the tests are done with non-conformance compiler settings that cater to old customers. -- PGP/GPG: 2CCB 3ECB 0954 5CD3 B0DB 6AA0 BA03 56A1 2C4638C5
Daniela Engert wrote:
BTW, this is the reason why we build (and use) Boost with our own build flags to enforce and announce maximum possible language conformance in msvc. The list reveals that the tests are done with non-conformance compiler settings that cater to old customers.
Also known as "default settings". :-) I suppose a case can be made for b2 to default to /permissive- nowadays, though (as the VS IDE does for new projects).
participants (2)
-
Daniela Engert -
Peter Dimov