How does boost::spirit::hold_any work?

Question

Evidently hold_any has better performance than boost::any. How does it manage to do this?

Edit: Thanks to Mat's comment, I found an answer by hkaiser about hold_any at another question but it lacks details. A more detailed answer would be welcome.

Did you read the Stack Overflow post linked from that article? — Mat, Nov 10 '12 at 10:19
Have you heard of "the small object optimization idiom" in the context of value semantic pseudo pointer classes, like std string? — Yakk - Adam Nevraumont, Nov 10 '12 at 11:31

Hugo Corrá · Answer 1 · 2012-11-10T12:36:13.230

I think one of the reasons is because boost::hold_any uses a template metaprogramming approach whilst boost::any uses an inheritance approach.

Internally, boost::spirit::hold_any stores the "value" using a void* and uses another object to keep track of the data type info:

>> boost/spirit/home/support/detail/hold_any.hpp
template <typename Char>
class basic_hold_any
{
    ....
    spirit::detail::fxn_ptr_table<Char>* table;
    void* object;
    ...
}

boost::any stores the "value" using an holder, and it doesn't need another object to keep track of the data type info. The holder is inherited from placeholder and consequently have the inheritance drawbacks.

>> boost/any.hpp
class any
{
    ...
    placeholder * content;
    ...
}


class placeholder
template<typename ValueType>
class holder : public placeholder
{
    ...
    ValueType held;
    ...
}

...the perfomance difference is much more about calling constructors and destructors, but even for casting, boost::spirit::hold_any should be faster.

score 1 · Answer 2 · answered Jul 03 '13 at 04:07

1

hold_any does two optimization: 1. For small objects it does't allocate memory for object holder but stores it directly in pointer memory; 2. It doesn't use RTTI type comparison (which is slow) but use its own type table

answered Jul 03 '13 at 04:07

AlexT

1,413
11
11

How does boost::spirit::hold_any work?

2 Answers2