From: Aleksey Gurtovoy (agurtovoy_at_[hidden])
Date: 2003-06-25 22:49:16
Drazen DOTLIC wrote:
> My company is using boost and we would very much like to use variant
> library immediately and not wait for the next official release of
> boost. Now, we know that this might not be sensible, but we are ready
> to take the risk. At the same time, we don't want to break anything
> else in the boost (and by chain reaction in our code). It seems that
> variant lib is dependent on (branch of?) mpl,
The version of the Variant library in the CVS' main trunk depends
(naturally) only on the main trunk components - MPL not being an
exception. The question is which parts of the main trunk you need/can
get without breaking things.
> so what I would like to
> know is: what is the most sane branch/snapshot we should take from the
> cvs to get reasonably stable boost (overall) with variant in whatever
> state it is ATM?
As far as MPL goes, I would say you can safely update it from the main
trunk - that is, if you are currently using 1.30.0 release.
To determine the status of other Variant dependencies you can use our
experimental status reports which employ automatically collected
1.30.0-snapshot's failures to highlight the differences between now and
Basically, 'unexp.' there signals a new failure (or a new library/test
case). Of course, you would have to use your own judgment to determine
how critical are those to you.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk