+1 on this case. I haven't read all the Boost documentation, but with
its Uncommitted binding, and reliance upon earlier precedent, combined
with the fact that the library is a popular C++ building block, I think
it would be good for Solaris to have to this integrated.
-- Garrett
On
John Fischer John.Fischer at sun.com writes:
This project proposes to include the BOOST C++ Framework within
a Minor release of Solaris. BOOST allows for Parallel versions
to be installed on a system. This project will install BOOST
into /usr/include/boost/Major.Minor.Micro and /usr/lib
Rainer Orth wrote:
John Fischer John.Fischer at sun.com writes:
This project proposes to include the BOOST C++ Framework within
a Minor release of Solaris. BOOST allows for Parallel versions
to be installed on a system. This project will install BOOST
into
Stefan Teleman wrote:
Given that BOOST has taken considerable care in designing a construction
and delivery mechanism which permits non-conflicting coexistence of
several versions of BOOST, this seems to have been done for the purpose
of avoiding [ mitigating ] incompatibilities between
Rainer Orth wrote:
Garrett D'Amore writes:
If I understand correctly, Stefan's response is that minor/micro
versions are required because there *can* be incompatible changes in the
Boost libraries from upstream. That is to say, Boost doesn't guarantee
binary compatibility, but instead
John Fischer wrote:
PSARC,
I am sponsoring this case for Stefan Teleman from the SWF group
in Menlo Park. The case directory contains this proposal and
the BOOST documentation which can be accessed via:
http://sac.eng/Archives/CaseLog/arc/PSARC/2008/752/materials/boost-doc-1.37.0/
