4 Oct
2017
4 Oct
'17
4:21 p.m.
Stefan Seefeld wrote:
I'm talking about Boost libraries here, not theirs. Boost library X 1.64.0 is built against Boost library Y 1.64.0. You update Y to 1.65.0, X is now broken.
While this may be true for some (or even many) "core" Boost libraries, I believe there are enough peripheral libraries that could safely be built against multiple Boost "core" versions.
The libraries themselves can safely be built. The problem is with the user code that includes header-only Y 1.65 and links to X 1.64 built against (and containing inline) Y 1.64.