forked from boostorg/fusion
some updates
[SVN r36555]
This commit is contained in:
@ -41,7 +41,8 @@
|
||||
on virtual functions to provide polymorphic behavior since the actual type
|
||||
is erased as soon as you store a pointer to a derived class to a pointer to
|
||||
its base. The held objects must be related: you cannot hold objects of unrelated
|
||||
types such as <tt class="computeroutput"><span class="keyword">char</span></tt>, <tt class="computeroutput"><span class="keyword">int</span></tt>, <tt class="computeroutput"><span class="keyword">class</span><EFBFBD><span class="identifier">X</span></tt>, <tt class="computeroutput"><span class="keyword">float</span></tt>,
|
||||
types such as <tt class="computeroutput"><span class="keyword">char</span></tt>, <tt class="computeroutput"><span class="keyword">int</span></tt>, <tt class="computeroutput"><span class="keyword">class</span>
|
||||
<span class="identifier">X</span></tt>, <tt class="computeroutput"><span class="keyword">float</span></tt>,
|
||||
etc. Oh sure you can use something like <a href="http://boost.org/doc/html/any.html" target="_top">Boost.Any</a>
|
||||
to hold arbitrary types, but then you pay more in terms of runtime costs and
|
||||
due to the fact that you practically erased all type information, you'll have
|
||||
|
Reference in New Issue
Block a user