Boost.Any vs. Boost.Variant

Question

I'm having trouble choosing between Boost.Any and Boost.Variant.
When should I use each one?

What are the advantages and disadvantages of each?

I am basically looking to store some states from external sources.

If you know all the possible types that data can have at compile time, then use Boost.Variant: the number of types that your data can have is finite and types are verified at compilation. If those types can be anything, then use Boost.Any. — user1284631, Oct 21 '14 at 11:17

score 46 · Accepted Answer · edited Jul 24 '13 at 17:41

46

Have you looked at the comparison in the variant library already?

(Not sure what states from external sources are, so it's kind of hard to say what's more appropriate for you.)

edited Jul 24 '13 at 17:41

jxh

answered Sep 02 '09 at 08:54

drby

Actually I haven't seen that before. But what is the right question to ask to help me choose? – the_drow Sep 02 '09 at 08:57
1

You would have to answer that yourself - which of the features is critical for you? – 1800 INFORMATION Sep 02 '09 at 09:05
Ease of use, no maintainability headaches, the least overhead possible. I can estimate what my types are going to be but what if I need to add yet another one tomorrow? – the_drow Sep 03 '09 at 07:32
@Hackingwords: Assume it's some kind of Driver. – the_drow Sep 03 '09 at 07:33

1 Answers1