June 2011 - Boost-users - lists.preview.boost.org

Re: [Boost-users] [chrono] Can not build with intel-win
by Edward Rankin 14 Jun '11

14 Jun '11

On Mon, Jun 13, 2011 at 3:55 PM, <boost-users-request(a)lists.boost.org>wrote: > Message: 6 > Date: Mon, 13 Jun 2011 08:10:45 +0100 > From: Bo Jensen <jensen.bo(a)gmail.com> > To: boost-users(a)lists.boost.org > Subject: [Boost-users] [chrono] Can not build with intel-win > Message-ID: <BANLkTim7efYQfM=FhFi9m5Q2i0g8L5XG5A(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Newest intel C++ release and vs2010, can not build with chrono from trunk. > > I get : > > pnet.cpp > ..\..\..\external\boost\boost/chrono/duration.hpp(94): error: expected > an expression > && (boost::is_convertible<Rep2, > ^ > > ..\..\..\external\boost\boost/chrono/duration.hpp(124): error: > expected an expression > && (boost::is_convertible<Rep, > ^ > > compilation aborted for ..\network\pnet.cpp (code 2) > > call "C:\Program Files > (x86)\Intel\ComposerXE-2011\bin\intel64//iclvars.bat" > nul > icl @"bin\intel-win\release\threading-multi\pnet.obj.rsp" > > ...failed compile-c-c++ bin\intel-win\release\threading-multi\pnet.obj... > ...failed updating 1 target... > > > Any suggestions welcome. > > Thanks > /Bo > Yes, I get this error too. The latest beta from Intel still exhibits this problem, but I currently do not have any insight on how to fix this. Perhaps you could create a bug report. Edward

1 0

does composite_key_compare support an interface that enables comparsion of the whole tuple
by brijesh.sharma＠thomsonreuters.com 14 Jun '11

14 Jun '11

Hi, Here is what I am trying to do typedef DWORD DSIid; enum DSType { DSTypeNone = 0, DSTypeBegin, DSTypeRoot } struct SDSIOwnedByKey { SDSIOwnedByKey(DSType DSTypeOwned, DSIid DSIidOwned, DSType DSTypeOwner, DSIid DSIidOwner) : m_DSTypeOwned(DSTypeOwned), m_DSIidOwned(DSIidOwned), m_DSTypeOwner(DSTypeOwner), m_DSIidOwner(DSIidOwner) { } bool operator == (const SDSIOwnedByKey &rcComp) const { return m_DSTypeOwned == rcComp.m_DSTypeOwned && m_DSIidOwned == rcComp.m_DSIidOwned && m_DSTypeOwner == rcComp.m_DSTypeOwner && m_DSIidOwner == rcComp.m_DSIidOwner; } DSType m_DSTypeOwned; DSIid m_DSIidOwned; DSType m_DSTypeOwner; DSIid m_DSIidOwner; }; class DataStore { typedef boost::multi_index_container< SDSIOwnedByKey, boost::multi_index::indexed_by< boost::multi_index::ordered_unique<boost::multi_index::tag<ByOwnedTypeOw nerTypeOwnerIdOwnedId>, boost::multi_index::composite_key<SDSIOwnedByKey, boost::multi_index::member<SDSIOwnedByKey, DSType, &SDSIOwnedByKey::m_DSTypeOwned>, boost::multi_index::member<SDSIOwnedByKey, DSType, &SDSIOwnedByKey::m_DSTypeOwner>, boost::multi_index::member<SDSIOwnedByKey, DSIid, &SDSIOwnedByKey::m_DSIidOwner>, boost::multi_index::member<SDSIOwnedByKey, DSIid, &SDSIOwnedByKey::m_DSIidOwned> >, boost::multi_index::composite_key_compare<std::less<DSType>,std::less<DS Type>, std::less<DSIid>, std::greater<DSIid>> > > > TOwnedBySort; typedef typename TOwnedBySort::index<ByOwnedTypeOwnerTypeOwnerIdOwnedId>::type OwnedBySort_ByOwnedTypeOwnerTypeOwnerId; TOwnedBySort m_oOwnedBySort; }; Instead of >, boost::multi_index::composite_key_compare<std::less<DSType>,std::less<DS Type>, std::less<DSIid>, std::greater<DSIid>> I want to write a compare function that compared all the values in one function, like a complete record comparison something like >, boost::multi_index::composite_key_compare<SDSIOwnedByKey> And have an appropriate function which would get the whole record to compare Thanks Brijesh

2 1

[Boost Serialization] Problem serializing derived class declared in DLL
by kmdarkmaster 13 Jun '11

13 Jun '11

Dear Boost community, My problem is simple : I need to serialize a derived class (named Plugin) of a c++ class (named Base) in my main program. The derived class Plugin is declared in a DLL which is load explicitely during execution. I tried to use the macro BOOST_CLASS_EXPORT_GUID (as in the doc), this works perfectly if the derived class is in the main execution, but will give me an exception if the derived class is in the plugin DLL. Forgive me if the problem is too obvious, this is my first time using Boost and I'm still a big noob in c++. Here is my code : IN THE MAIN EXECUTION : Class Base (parent class) : Base.h : #pragma once; #include "boost\serialization\access.hpp" #include <boost\serialization\nvp.hpp> class Base { private: friend class boost::serialization::access; template void serialize(Archive & ar, const unsigned int version){} public: int a, b; Base(); virtual ~Base() { } virtual void func()= 0; // this is an abstract base class } Base.cpp: #include "StdAfx.h" #include "Base.h" Base::Base(){ a=0; b=0; } IN THE DLL (loaded explicitely) Class Plugin (Child Class) : Plugin.h: #pragma once #include "boost\serialization\access.hpp" #include <boost\serialization\nvp.hpp> #include "boost\serialization\export.hpp" #include "Base.h" class Plugin: public Base { private: friend class boost::serialization::access; template void serialize(Archive & ar, const unsigned int version){ ar & BOOST_SERIALIZATION_BASE_OBJECT_NVP(Base); ar & BOOST_SERIALIZATION_NVP(a); ar & BOOST_SERIALIZATION_NVP(b); } public: virtual void func(); }; BOOST_CLASS_EXPORT_GUID(Plugin, "Plugin") Plugin.cpp: #include "StdAfx.h" #include "Plugin.h" void Plugin::func(){ a= 5; b= 6; } THE MAIN FUNCTION (IN THE MAIN EXECUTION): ....................................... HINSTANCE hinst= LoadLibrary(L"monDLLdynamique.dll"); if (hinst) { CreatePlugin ctor= (CreatePlugin)GetProcAddress(hinst, "CreatePlugin"); Base *test= ctor(); std::ofstream ofs3("FichierPointeursDerivedDLL.xml"); { boost::archive::xml_oarchive oa(ofs3); oa << BOOST_SERIALIZATION_NVP(test); } ofs3.close(); delete test; // calls Plugin's dtor FreeLibrary(hinst); } ............................................ Any help will be very very appreciated !!! Thanks -- View this message in context: http://boost.2283326.n4.nabble.com/Boost-Serialization-Problem-serializing-… Sent from the Boost - Users mailing list archive at Nabble.com.

5 10

OSCON 2011
by Robert Ramey 13 Jun '11

13 Jun '11

http://www.oscon.com/oscon2011 I wonder if in the interest of evangilizing C++/etc. anyone would be interested in exhibiting on behalf of boost here? Robert Ramey

1 0

[chrono] Can not build with intel-win
by Bo Jensen 13 Jun '11

13 Jun '11

Newest intel C++ release and vs2010, can not build with chrono from trunk. I get : pnet.cpp ..\..\..\external\boost\boost/chrono/duration.hpp(94): error: expected an expression && (boost::is_convertible<Rep2, ^ ..\..\..\external\boost\boost/chrono/duration.hpp(124): error: expected an expression && (boost::is_convertible<Rep, ^ compilation aborted for ..\network\pnet.cpp (code 2) call "C:\Program Files (x86)\Intel\ComposerXE-2011\bin\intel64//iclvars.bat" > nul icl @"bin\intel-win\release\threading-multi\pnet.obj.rsp" ...failed compile-c-c++ bin\intel-win\release\threading-multi\pnet.obj... ...failed updating 1 target... Any suggestions welcome. Thanks /Bo

2 1

[Smart Pointers] enable_shared_from_this::shared_from_this() behaviour query
by eddyaod＠gmail.com 13 Jun '11

13 Jun '11

shared_from_this() throws bad_weak_ptr if it's called in a derived destructor even if the object is heap allocated, does anyone know if this is intended? And if so, why? Example: class DestructorCheck : public std::tr1::enable_shared_from_this <DestructorCheck> { public: DestructorCheck() { } ~DestructorCheck() { shared_from_this(); } }; BOOST_AUTO_TEST_CASE(enable_weakTests) { BOOST_CHECK_THROW( { DestructorCheck d; } , std::tr1::bad_weak_ptr ) BOOST_CHECK_NO_THROW( { std::tr1::shared_ptr<DestructorCheck> d = boost::make_shared<DestructorCheck>(); } ) }

2 2

intrusive_ptr and multi-threading
by Andrej van der Zee 13 Jun '11

13 Jun '11

Hi, I am looking for an efficient way to use boost::intrusive_ptr in a multi-threaded application. In the source-tree I encountered the macro BOOST_INTERLOCKED_INCREMENT/DECREMENT. Should I use these too and how are these implemented in Linux? Where can I find documentation on these macros? Thank you, Andrej

2 4

Boost.Phoenix Exception Handling
by Stuart Dootson 13 Jun '11

13 Jun '11

I've been using Phoenix (the one that came with 1.44 - that's Phoenix v2?) for a bit, as a Boost.Lambda replacement, mostly happily. But I've come across a scenario I don't think Phoenix caters for, namely accessing an exception from a catch_ body, something like this: std::vector<std::string> errors; using namespace boost::phoenix; using namespace boost::phoenix::arg_names; std::for_each(changes.begin(), changes.end(), try_ [ bind(&SomeClass::AddChange, this, arg1, std::string()) ] .catch_<std::runtime_error>() [ push_back(ref(errors), bind(&std::runtime_error::what, /* Can I access the exceptin that's been thrown? */)) ]); I want to aggregate any error information thrown by SomeClass::AddChange in the 'errors' vector, to be rethrown after the for_each. In Boost.Lambda, I'd be able to use the '_e' placeholder to access the exception object, but there seems to be no way of doing so in Phoenix? So, I'm just wondering if a) I've missed something, and b) is there any likelihood of this being added into Phoenix v3 at some point? Stuart Dootson

2 3

Boost configuration - particularly no wchar
by Pace, Antony [Harman Pro Group UK] 13 Jun '11

13 Jun '11

Hi, Our compiler does not support wchar. I have found that #defining BOOST_NO_STD_WSTRING and BOOST_NO_INTRINSIC_WCHAR_T helps the compilation but I suspect there is a correct place or method of defining this. Could someone point me at the documentation for this please? Many thanks Ant

2 2

exception, filesystem, system_error and consistency
by Michael Schuerig 13 Jun '11

13 Jun '11

I haven't used C++ for several years and it's only a few weeks since I've looked at boost for the first time. Thus it's likely that my understanding of things isn't quite up to scratch. In my first C++ project for years, I'm already using boost::filesystem and I'm using boost::system::system_error to wrap error codes returned by Linux API functions. For the latter purpose, I intend to use boost::exception for its ability to add diagnostic information to exceptions. At the top-level of my own code, I implement plain C interfaces and therefore need to convert all exceptions back to their original error codes. Poring over docs and headers, I noticed that neither boost::system::system_error nor boost::filesystem::filesystem_error are derived from boost::exception. Instead they implement an independent exception hierarchy. I found this disconcerting. For one thing, I have to catch and handle the respective exceptions separately. Far more importantly, though, I was expecting consistency among boost libraries and now see that this is not the case apparently. When there is more than one way to do something, this automatically raises the question which one is the right way. Regarding boost, I'm wondering whether all libraries are created equal or whether there is an undocumented gradation from "stable, recommended" to "experimental, beware". Michael -- Michael Schuerig mailto:michael@schuerig.de http://www.schuerig.de/michael/

4 10