On Sat, 29 Jun 2019 at 08:41, Robert Ramey via Boost
In fact I always test with std=C++03 flag to ensure exactly that.
Yes, you do, and that also fixes the C++17 issue of course, but you did that at the time with VS2010 (or even VS2008) and it succeeded. Boost-1.47 must include a ton of work-arounds to fix the non-compliance of both the pre-processor, the compiler and its STL. Compiling those with VS2017/19 will certainly break some of those (I **am** guessing here), coz the Boost-1.47 code has no knowledge of the now much better compliance of VS. degski -- @realdegski https://edition.cnn.com/interactive/2019/06/middleeast/saudi-teen-death-pena... "Anyone who believes that exponential growth can go on forever in a finite world is either a madman or an economist" - Kenneth E. Boulding