<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel about="http://permalink.gmane.org/gmane.comp.lib.boost.user">
    <title>gmane.comp.lib.boost.user</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.boost.user</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.boost.user/39171"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.boost.user/39170"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.boost.user/39169"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.boost.user/39168"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.boost.user/39167"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.boost.user/39166"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.boost.user/39165"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.boost.user/39164"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.boost.user/39163"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.boost.user/39162"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.boost.user/39161"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.boost.user/39160"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.boost.user/39159"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.boost.user/39158"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.boost.user/39157"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.boost.user/39156"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.boost.user/39155"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.boost.user/39154"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.boost.user/39153"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.boost.user/39152"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.boost.user/39171">
    <title>transform_view: question about boilerplate code</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.boost.user/39171</link>
    <description>I have succeeded in writing the following transform functor:

typedef bf::map&lt;bf::pair&lt;net, unsigned&gt;, bf::pair&lt;pin, unsigned&gt; &gt; Map;
typedef bf::vector&lt;unsigned, unsigned&gt; Pair;

struct Map2Pair
{
    template&lt;typename Sig&gt;
    struct result;

    template&lt;typename U&gt;
    struct result&lt;Map2Pair(U)&gt;
    : remove_reference&lt;T::second_type&gt;
    { };

    template&lt;typename T&gt;
    typename T::second_type operator()(T t) const
    {
        return t.second;
    }
};

I have tested it, it works.  The result magic has been copied from the
transform_view example in the documentation and adjusted for the proper return
type.  Where can I read a bit more about result conventions?  In particular,
how does the

    template&lt;typename U&gt;
    struct result&lt;Map2Pair(U)&gt;
    : remove_reference&lt;T::second_type&gt;
    { };

specialization work when Map2Pair is a struct, and it doesn't even have a 
constructor!   Even worse, why does it work at all when T is not in the
scope of the template (.. because it's never used?)  Yes, it is </description>
    <dc:creator>Zeljko Vrba</dc:creator>
    <dc:date>2008-08-21T17:21:49</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.boost.user/39170">
    <title>Re: Serialization of derived classes with boost 1.34.1</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.boost.user/39170</link>
    <description>Probably something else needs to be explicitly instantiated.  Perhaps

template void A::serialize(boost::archive::polymorphic_iarchive&amp; ar,
const  unsigned int file_version);
template void A::serialize(boost::archive::polymorphic_oarchive&amp; ar,
const unsigned int file_version);

Look at the demos. One of them addresses this problem - though
not through shared_ptr.

Robert Ramey

Hansi wrote:



_______________________________________________
Boost-users mailing list
Boost-users&lt; at &gt;lists.boost.org
http://lists.boost.org/mailman/listinfo.cgi/boost-users</description>
    <dc:creator>Robert Ramey</dc:creator>
    <dc:date>2008-08-21T17:08:07</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.boost.user/39169">
    <title>Re: how to make fusion::pair less-than-comparable?</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.boost.user/39169</link>
    <description>
Hmm, an inverted email: first rationale, then conclusion.  I asked whether

typedef map&lt;pair&lt;pin, unsigned&gt;, pair&lt;net, unsigned&gt; &gt; Map1;
typedef map&lt;pair&lt;net, unsigned&gt;, pair&lt;pin, unsigned&gt; &gt; Map2;

were different because either way makes sense, depending on whether you view
the template list as an unordered set or as an ordered list.  My "intuition",
coming from the run-time case of std::map would lead me to believe that types
Map1 and Map2 were the same.  Namely, std::map  is an unordered set of (K,V)
pairs.  So, { (a, 1), (b, 2), (c, 3) } and { (c, 3), (a, 1), (b, 2) } have
different layout, but for the purpose of asking "which number the letter 'a'
is mapped to", they are the same mapping.  This coincides with the
mathematical definition of function equality: f1 == f2 if domain(f1) ==
domain(f2), codomain(f1) == codomain(f2), and pointwise equality, f1(x) ==
f2(x) for each x from the domain.  Mathematicians also sometimes say map
instead of function:

http://mathworld.wolfram.com/Map.html

In the light </description>
    <dc:creator>Zeljko Vrba</dc:creator>
    <dc:date>2008-08-21T15:56:23</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.boost.user/39168">
    <title>Wrapping a library</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.boost.user/39168</link>
    <description>I have this library (one class with 700 methods) I want to wrap all the calls, so I can log the calls and do other stuff.  Using emacs macros and stuff, I can create a proxy class which has the same signature, but each method calls a C macro which calls the original class method, and does other stuff.

For example:
  void logfunc(char *func) const
  { 
    OutputDebugStringA(func); 
  }
  void logarg(int a) // overload for each type of parameter
  {
    CString x;
    x.Format(L"%d", a);
    OutputDebugString(x);
  }

  ULONG GetID(const CKSEntity &amp;pEntity) const { return  proxy1(GetID, pEntity); }  // repeat for all 700 methods.

// Repeat these macros for every count of arg between 0 and 24.
#define proxy10(Func, Arg1,Arg2,Arg3,Arg4,Arg5,Arg6,Arg7,Arg8,Arg9,Arg10) \
  (      log10(#Func, Arg1,Arg2,Arg3,Arg4,Arg5,Arg6,Arg7,Arg8,Arg9,Arg10), \
        thePart.Func( Arg1,Arg2,Arg3,Arg4,Arg5,Arg6,Arg7,Arg8,Arg9,Arg10))
#define log10(Func, Arg1,Arg2,Arg3,Arg4,Arg5,Arg6,Arg7,Arg8,Arg9,Arg10) \
         log9(Func</description>
    <dc:creator>Alan Baljeu</dc:creator>
    <dc:date>2008-08-21T13:10:41</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.boost.user/39167">
    <title>Sample code for boost::thread - Timed Lockable mutex ?</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.boost.user/39167</link>
    <description>Hello,

I want to use timed lockable mutex in boost::thread, but the usage is
not so obvious for a beginner.

Would there be anywhere a sample code with this kind og mutex ?

I have a code which works with a boost::mutex in a consumer/producer
queue (code below).
The purpose is to have a maximum waiting delay for waitForNotEmpty().

Thanks.

-------------------------------------------------------------------------

template &lt;typename T&gt;
class MTBornedQueue
{
public:
    ....
    bool waitForNotEmpty()
    {
        if (!m_container.empty())
            return true;

        boost::mutex::scoped_lock lock(m_accessMutex);
        m_notEmpty.wait(lock,
boost::bind(&amp;MTBornedQueue&lt;value_type&gt;::isNotEmpty, this));
        return true;
    }
    ...

private:
    bool isNotEmpty() const { return m_unread &gt; 0; };
    size_type            m_unread;
    container_type     m_container;
    boost::mutex        m_accessMutex;
    boost::condition    m_notEmpty;
}
</description>
    <dc:creator>Stéphane Vandenbogaerde</dc:creator>
    <dc:date>2008-08-21T15:09:38</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.boost.user/39166">
    <title>[shared_ptr] Implicit cast shared_ptr&lt;derived&gt; toshared_ptr&lt;base&gt;</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.boost.user/39166</link>
    <description>Hi there,

after making what I then thought was a bad mistake, I discovered that the
code below actually works (gcc 4.3.1, OpenSUSE 11 64bit, Boost 1.36). I.e.,
there is an implicit cast from shared_ptr&lt;derived&gt; to shared_ptr&lt;base&gt; to
make it fit the function argument, although both represent different types.

Is this intended behaviour (i.e. portable) ? I did not find a corresponding
description in the docu.

Thanks and Best Regards,

Ruediger

/**************************************************************************/

#include &lt;iostream&gt;
#include &lt;boost/shared_ptr.hpp&gt;

class base{
public:
  virtual ~base(){}
  virtual void print() const {
    std::cout &lt;&lt; "Hello world from base" &lt;&lt; std::endl;
  }
};

class derived
  :public base
{
public:
  void print() const {
    std::cout &lt;&lt; "Hello world from derived" &lt;&lt; std::endl;
  }
};

void executeBasePrint(const boost::shared_ptr&lt;base&gt;&amp; base_ptr){
  base_ptr-&gt;print();
}

main(){
  boost::shared_ptr&lt;derived&gt; derived_ptr(new derived());
  // Results in "Hello worl</description>
    <dc:creator>Ruediger Berlich</dc:creator>
    <dc:date>2008-08-21T12:47:07</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.boost.user/39165">
    <title>Re: [filesystem] Bugs in path::append ?</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.boost.user/39165</link>
    <description>
Yes, the 'uncomplete' you suggest would be a much cleaner way. IMHO
advance() would be needed just to complete the iterator
implementation.


Yes, 7 was just suggested as an example here. It comes from counting
the number of elements in input_base_path.


The use case here is creating complete output paths for "copy-pasting
a sub-tree from input_base_path to output_base_path" (ofcourse with
some transformations along the way).

For now, I am using

  fs::wpath output_path=output_base_path;
  int k=0; for(fs::wpath::iterator
i=input_path.begin();i!=input_path.end();i++,k++) if(k&gt;=7)
output_path/=(*i);

Again, 7 is the number of elements in input_base_path. advance() would
make it atleast slightly cleaner (remove k, and the if on k),
uncomplete would be ideal.

Sachin Garg
</description>
    <dc:creator>Sachin Garg</dc:creator>
    <dc:date>2008-08-21T15:37:46</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.boost.user/39164">
    <title>Re: Fusion: some concrete questions about maps andvectors</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.boost.user/39164</link>
    <description>
Yes.


Yes: transform_view. It won't be a fusion vector, but the effect
is what you want.


Sounds good. One step at a time. Tell us if you need some help/advice
on various issues.

Regards,
</description>
    <dc:creator>Joel de Guzman</dc:creator>
    <dc:date>2008-08-21T14:44:00</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.boost.user/39163">
    <title>Re: how to make fusion::pair less-than-comparable?</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.boost.user/39163</link>
    <description>
The reason is I don't know (yet) how to do 1 :-) If there are some
suggestions, I see no reason why it can't be added to the library.
So... how do you compare a half-static-half-runtime pair? Compare
just the value part? How about pairs with different static parts
but comparable runtime parts, how do they compare? Simply disallow?
Comments, suggestions welcome.

Regards,
</description>
    <dc:creator>Joel de Guzman</dc:creator>
    <dc:date>2008-08-21T14:35:22</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.boost.user/39162">
    <title>Re: Serialization of derived classes with boost 1.34.1</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.boost.user/39162</link>
    <description>_______________________________________________
Boost-users mailing list
Boost-users&lt; at &gt;lists.boost.org
http://lists.boost.org/mailman/listinfo.cgi/boost-users</description>
    <dc:creator>Tim St. Clair</dc:creator>
    <dc:date>2008-08-21T14:32:12</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.boost.user/39161">
    <title>how to make fusion::pair less-than-comparable?</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.boost.user/39161</link>
    <description>Related to my previous question: fusion::map is a sequence and instances of it
could be directly compared with operator &lt; , thus vectors of instances also 
sorted if fusion::pair supported relational operators other than == and !=
(which it doesn't).

So, two questions:

1. What is the recommended way of defining operator&lt; for particular pair
   instances (e.g. for pair&lt;net, int&gt;) ?

2. An explanation of why doesn't fusion::pair define at least operator&lt; would
   be welcome. 

Thanks.

(Yes, I know, I can pass an explicit predicate to std::sort..  )
</description>
    <dc:creator>Zeljko Vrba</dc:creator>
    <dc:date>2008-08-21T14:27:35</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.boost.user/39160">
    <title>Re: boost::graph issues.</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.boost.user/39160</link>
    <description>_______________________________________________
Boost-users mailing list
Boost-users&lt; at &gt;lists.boost.org
http://lists.boost.org/mailman/listinfo.cgi/boost-users</description>
    <dc:creator>Robert Jones</dc:creator>
    <dc:date>2008-08-21T12:51:12</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.boost.user/39159">
    <title>Re: [filesystem] Bugs in path::append ?</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.boost.user/39159</link>
    <description>
I suspect it's simply that it wasn't included in the TR proposal,
wanting to leave open different options for implementations.

I have a feature request for an "uncomplete" function in; Would you be
happy with something like this instead?

    complete( uncomplete(i, input_base_path), output_path);

Where input_base_path would be the first 7 components of your
input_path.  (I'm guessing that the 7 comes from some other path,
rather than being hard-coded somehow.)

Hoping to find a new use case,
~ Scott
</description>
    <dc:creator>Scott McMurray</dc:creator>
    <dc:date>2008-08-21T12:30:48</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.boost.user/39158">
    <title>Re: cross-platfrom binary serialization?</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.boost.user/39158</link>
    <description>Hi Roman and Akos!

boost-users-bounces&lt; at &gt;lists.boost.org on :


And gcc-4, which also supports the #pragma once. The use of this construct and the warnings is simply a result from my strive to minimalize code length. What I express in code is the algorithmical idea in the shortest possible way I can think of. Let the compiler complain about it, I don't care because I _know_ what I'm doing and the warnings are vain. They issue from using one metafunction for all integral types, be them signed or unsigned. Of course you could separate those but only by introducing verboseness. Originally I even let the integral function treat the bool case resulting in even more warnings. The zero bool tweak in mind I decided to write an extra overload for bool. However if you have suggestions that fix the warnings and come close to a minimal solution I'll be happy to look into it.

I include enough boost headers which implicitly include version.hpp and the like so I need not bother making this explicit.


We do. Using the arch</description>
    <dc:creator>Pfligersdorffer, Christian</dc:creator>
    <dc:date>2008-08-21T11:42:15</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.boost.user/39157">
    <title>Re: AIX 5.3 xlC error on ptr_list.hpp</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.boost.user/39157</link>
    <description>

[...]

The trunk is tested against XL C/C++ V9.0.0.3, see 
http://beta.boost.org/development/tests/trunk/developer/summary.html for 
reference.

The release branch is not tested for this compiler, but I don't see any 
specific reason why the results should differ much from the current trunk 
results. Especially 
http://beta.boost.org/development/tests/trunk/developer/ptr_container.html 
shows that at least ptr_list should work with this compiler.

Which version of the compiler are you using? You probably need to update 
your compiler.

HTH, Markus
</description>
    <dc:creator>Markus Schöpflin</dc:creator>
    <dc:date>2008-08-21T11:33:59</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.boost.user/39156">
    <title>Fusion: some concrete questions about maps and vectors</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.boost.user/39156</link>
    <description>I'm operating on two vectors of pairs of numbers, currently represented by
std::pair&lt;unsigned, unsigned&gt;.  The first vector is a list of (net,pin) pairs,
while the second vector is a list of (pin, net) pairs.

In order to raise a bit the understandability / abstraction level of my code, I
think that it'd be nice to be able to write at_key&lt;pin&gt;(x) and at_key&lt;net&gt;(x)
instead of x.first or using tie().

Looking at fusion manual, it seems that of all the containers, map suits the
purpose:

struct pin;
struct net;

First question: are Map1 and Map2 different types?

typedef map&lt;pair&lt;pin, unsigned&gt;, pair&lt;net, unsigned&gt; &gt; Map1;
typedef map&lt;pair&lt;net, unsigned&gt;, pair&lt;pin, unsigned&gt; &gt; Map2;

According to a simple test program that I wrote, which basically boils down to
Map m1; Map m2; m1 = m2; they, are different because the compilation fails.
Hmm, so far, so good. 

Second question: some algorithms are common both for both types, e.g. sort,
where I want to have lexicographical comparison between the elements.  Is it
</description>
    <dc:creator>Zeljko Vrba</dc:creator>
    <dc:date>2008-08-21T11:16:44</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.boost.user/39155">
    <title>Compiling with a different version of a compiler</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.boost.user/39155</link>
    <description>Hi: 
Is there a way of compiling with a different version of a compiler. I.e
specifying a path on the command line or two command-line in the .jam
file.
Chers
Sean.
 

__________ Information from ESET NOD32 Antivirus, version of virus
signature database 3374 (20080821) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com
</description>
    <dc:creator>Sean Farrow</dc:creator>
    <dc:date>2008-08-21T11:16:39</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.boost.user/39154">
    <title>Re: AIX 5.3 xlC error on ptr_list.hpp</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.boost.user/39154</link>
    <description>Gary Fu skrev:

Well, I don't think AIX x1C was one of the officially supported 
compilers for 1.36, was it? Maybe it's time to complain to your compiler 
  vendor that it does not compile some of the Boost libraries ...

-Thorsten
</description>
    <dc:creator>Thorsten Ottosen</dc:creator>
    <dc:date>2008-08-21T10:56:48</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.boost.user/39153">
    <title>Re: How to find a sorting permutation</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.boost.user/39153</link>
    <description>





If you haven't looked already, I would always suggest citeseer if for nothing else
than benchmarks and tests of whatever you decide to do. A quick naive keyword
search is as follows,

http://citeseerx.ist.psu.edu/search?q=sort+permutation+order&amp;sort=rel

I think all of the papers are available free full text.

_________________________________________________________________
Get ideas on sharing photos from people like you.  Find new ways to share.
http://www.windowslive.com/explore/photogallery/posts?ocid=TXT_TAGLM_WL_Photo_Gallery_082008
</description>
    <dc:creator>Mike Marchywka</dc:creator>
    <dc:date>2008-08-21T10:49:28</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.boost.user/39152">
    <title>Re: Implementation question aboutboost::circular_buffer and allocator</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.boost.user/39152</link>
    <description>


--- On Wed, 20/8/08, Daryle Walker &lt;darylew&lt; at &gt;hotmail.com&gt; wrote:


Daryle,

Thank you very much - That was driving me crazy!
</description>
    <dc:creator>Peter Barker</dc:creator>
    <dc:date>2008-08-21T10:02:30</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.boost.user/39151">
    <title>Serialization of derived classes with boost 1.34.1</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.boost.user/39151</link>
    <description>Hello,

I have a problem to serialize a derived class.
In some classes I use a shared_ptr&lt;A&gt; which acts as a interface for some 
other classes.

Til now I had the implementation in the header and it worked fine with the
BOOST_CLASS_EXPORT(B)
declaration after at the end of the header file where B was defined.

For performance reason (compile time) I have moved the serialization 
code from the header file (there is only the declaration) to the .cpp 
file (now I use also only the polymorphic_binary_archive). There I have 
also the declaration for the polymorphic_binary_archive

template void B::serialize(boost::archive::polymorphic_iarchive&amp; ar, 
const  unsigned int file_version);
template void B::serialize(boost::archive::polymorphic_oarchive&amp; ar, 
const unsigned int file_version);

After linking I have now some linker errors. First for the class B which 
is derived from A and for the class A. All linker errors use the 
binary_archive.

If I declare the "BOOST_CLASS_EXPORT(B)" at the end in the .cpp file I 
g</description>
    <dc:creator>Hansi</dc:creator>
    <dc:date>2008-08-21T10:01:44</dc:date>
  </item>
  <textinput about="http://search.gmane.org/?group=$group=gmane.comp.lib.boost.user">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.lib.boost.user</link>
  </textinput>
</rdf:RDF>
