November 2006 - Boost-users - lists.preview.boost.org

Socket and iostream
by Ivan LAURETTE 08 Nov '06

08 Nov '06

Darwin 8.8.0 Boost 1.33.1 gcc 4.0.1 Hello, I want to establish a SMTP connection through a socket, then dialog with the server using a stream. I thought I could to it like this: //-------------------------------------------- #include <boost/iostreams/stream.hpp> #include <boost/iostreams/device/file_descriptor.hpp> using namespace std; using namespace boost::iostreams; ... int theSocket = socket(AF_INET,SOCK_STREAM,0); connect(theSocket, ...); file_descriptor fdDevice(theSocket); stream_buffer<file_descriptor> fdstream(fdDevice); iostream os(&fdstream); string answer; getline(os, answer); cout << answer << endl; os << "HELO xxxxx" << endl; getline(os, answer); cout << answer << endl; os << "MAIL FROM: <xxx.xxx(a)xxx.xxx>" << endl; getline(os, answer); cout << answer << endl; ... //-------------------------------------------- But nothing seems to be written nor readen to/from the socket except for the first getline. What am I doing wrong here ? Thanks in advance for any help.

2 1

[asio] Breaking changes committed to cvs HEAD
by Christopher Kohlhoff 08 Nov '06

08 Nov '06

I have just committed some asio changes to cvs HEAD that will break application code. These changes are part of what's needed to bring the interface into sync with the TR2 proposal. The big change is to the error handling classes, as described below. An async handler of the form: void my_handler(const boost::asio::error& e); becomes: void my_handler(const boost::system::error_code& e); Synchronous error handling like this: boost::asio::error e; sock.connect(ep, boost::asio::assign_error(e)); becomes: boost::system::error_code e; sock.connect(ep, e); And where previously a boost::asio::error exception was thrown, the new exception thrown is boost::system::system_error. Error constants like boost::asio::error::eof stay as they are, i.e.: void my_handler(const boost::system::error_code& e) { if (e == boost::asio::error::eof) { ... } } Programs will now need to link against the boost.system library (which is where boost::system::error_code and boost::system::system_error reside). Once I do a few more TR2-related changes I will post regenerated doxygen documentation to the vault. Stay tuned. Cheers, Chris

1 0

[Threads]Exception-safety of thread_group::add_thread
by Ai Azuma 08 Nov '06

08 Nov '06

Hi, I have questions about `boost::thread_group::add_thread' member function. The documents don't seem to say anything about exception-safety of this function. Therefore, I have questions; 1. Is this no-throw? 2. If the answer to 1. is "no", then how does it treat the ownership of its argument when an exception is thrown? Could anyone help me? Thanks in advance. -- Ai Azuma <ai.azuma(a)gmail.com>

1 0

progress_display+CProgressBar MFC
by Gennady Khokhorin 07 Nov '06

07 Nov '06

I'm wonder what could be a schema to connect boost::progress_timer to MFC CProgressBar (msvc) gui? Thanks in advance. gok

2 1

[Boost.Filesystem] problem to link an executable to boost_filesys tem static library on Windows XP
by Johan.GUIHENEUF＠external.thalesgroup.com 07 Nov '06

07 Nov '06

Hello, I try to build an console executable that uses boost_fileystem library. I have got the file boost_filesystem-vc71-mt-1_33.lib. My IDE is Visual C++ 7.1. I set the preprocessor definition _MT. At build step, I have this error: "could not find boost_filesystem-vc71-mt-s-1_33.lib". I had a look to boost/config/auto_link.hpp to see what "#define" I forgot but I do not understand why it chooses "#define BOOST_LIB_RT_OPT -s". hat preprocessor macro should I define to make it choose "#define BOOST_LIB_RT_OPT" (i.e. empty) ? Is there a blocking problem with Visual C++ 7.1 on Windows XP ? Thank you. Johan GUIHENEUF

2 1

Re: [Boost-users] [lambda] if-then-else construct gets broken bylambda-lib
by Nat Goodspeed 07 Nov '06

07 Nov '06

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org [mailto:boost-users- > bounces(a)lists.boost.org] On Behalf Of Sebastian Weber > Sent: Tuesday, November 07, 2006 12:41 PM > To: boost-users(a)lists.boost.org > Subject: [Boost-users] [lambda] if-then-else construct gets broken > bylambda-lib > > I'm trying to store a reference to a function depending upon a condition > within a function object like this: > > boost::function< double (std::size_t) > wf = (sIndex < m_maxIndex+1) ? > ( boost::lambda::bind(boost::ref(m_cf), sDeg, boost::lambda::_1) ) : > ( boost::ref(*m_wf) ); [Nat] Does it work better if the 'else' clause is something more like: ( boost::lambda::bind(boost::ref(*m_wf)) ) ? This is a wild guess, but boost::ref() isn't by itself a lambda bind expression -- is it? Both halves of the ternary operator are convertible to boost::function -- but they're not the same type. I don't know whether two different boost::lambda::bind expressions are going to be compatible either. You may have to explicitly instantiate boost::function objects on both sides of the : -- which would end up being less terse than writing the if/else statement. But it seems worth a try.

2 1

Serialization with polymorphic_*_archive and BOOST_CLASS_EXPORT
by Anders Wang Kristensen 07 Nov '06

07 Nov '06

Hi, I'm having trouble serializing through the a pointer to the base as shown below. If I manually register class B with template register_type<B>() it works, but I would rather use the BOOST_CLASS_EXPORT macros since that is more convenient. Unfortunately BOOST_CLASS_EXPORT assumes you are using the templated version of serialize, and not polymorphic_iarchive/oarchive, that I'm using. Anyone know how to get around that problem? Thanks! -- wang Example: #include <boost/archive/polymorphic_text_iarchive.hpp> #include <boost/archive/polymorphic_text_oarchive.hpp> #include <boost/archive/polymorphic_xml_iarchive.hpp> #include <boost/archive/polymorphic_xml_oarchive.hpp> #include <boost/serialization/shared_ptr.hpp> #include <boost/serialization/export.hpp> struct A { void serialize(boost::archive::polymorphic_iarchive & ar, const unsigned int file_version); void serialize(boost::archive::polymorphic_oarchive & ar, const unsigned int file_version); int data; bool operator==(const A & rhs) const { return data == rhs.data; } A() : data(0) {} virtual ~A() = 0 {} }; void A::serialize( boost::archive::polymorphic_iarchive & ar, const unsigned int file_version ){ ar & BOOST_SERIALIZATION_NVP(data); } void A::serialize( boost::archive::polymorphic_oarchive & ar, const unsigned int file_version ){ ar & BOOST_SERIALIZATION_NVP(data); } struct B : public A { void serialize(boost::archive::polymorphic_iarchive & ar, const unsigned int file_version); void serialize(boost::archive::polymorphic_oarchive & ar, const unsigned int file_version); int foo; bool operator==(const B & rhs) const { return data==rhs.data && foo==rhs.foo; } B() : foo(2) {} }; void B::serialize( boost::archive::polymorphic_iarchive & ar, const unsigned int file_version ){ ar & BOOST_SERIALIZATION_BASE_OBJECT_NVP(A); ar & BOOST_SERIALIZATION_NVP(foo); } void B::serialize( boost::archive::polymorphic_oarchive & ar, const unsigned int file_version ){ ar & BOOST_SERIALIZATION_BASE_OBJECT_NVP(A); ar & BOOST_SERIALIZATION_NVP(foo); } BOOST_CLASS_EXPORT(B) int main(int argc, const char* argv[]) { boost::shared_ptr<A> a(new B); boost::shared_ptr<A> b; { std::stringstream ss; { boost::archive::polymorphic_text_oarchive oa(ss); //oa.template register_type<B>(); oa << BOOST_SERIALIZATION_NVP(a); } { boost::archive::polymorphic_text_iarchive ia(ss); //ia.template register_type<B>(); ia >> BOOST_SERIALIZATION_NVP(b); } } B* x = dynamic_cast<B*>(a.get()); B* y = dynamic_cast<B*>(b.get()); assert(*x == *y); return 0; }

2 4

Re: [Boost-users] Serialization problem on 64-bit Windows release
by Сергей Филиппов 07 Nov '06

07 Nov '06

Robert Ramey <ramey <at> rrsd.com> writes: > > Is it possible that this might be related to the recently discovered fact > (at least by me) versions of the serialization library are, contrary to > intention, not thread safe? That is, conflict occurs when multiple threads > are using serilization even with different archive instances due to the fact > that they share the same gobal extended_type_info table. This has been > addressed - and hopefully remedied in 1.35. > > Robert Ramey What does it mean that the serialization library is "not thread safe"? Does it mean that the serialization must be used in one thread only or the serialization can be used in different, non-concurrent threads? I'm not familiar with the serialization library internals so it's hard to me to make a guess where it is related to my case. My application is an RPC server that supports only one client connection. The client establishes connection, makes some calls to the server and exits. Each call can generate "events" that are stored on the server in a vector. After a call the client may call the server's function SerializeEvents which serializes the vector into buffer and transmits the buffer to the client. Actual serialization code is straightforward. void CEventLogger::Serialize(std::vector<BYTE>* pBuffer) { std::stringstream stream; boost::archive::text_oarchive ar(stream); ar & m_Events; std::string str(stream.rdbuf()->str()); if(str.length()) { BYTE *pBuf = reinterpret_cast<BYTE*>(const_cast<char*>(str.c_str())); pBuffer->assign(pBuf, pBuf + str.length()); } else pBuffer->clear(); } The client communicates with the server in one thread only. So the functions that are populating m_Events and CEventLogger::Serialize are called in different threads, but these calls are serialized. What you think? Can "not thread safety" be a reason in my case? Thanks, Sergey (Sorry, I forget to mention I'm using boost 1.33.0.)

2 1

fpclassify
by Johan Råde 07 Nov '06

07 Nov '06

Ignore my last message. It was sent by mistake. --Johan

1 0

fpclassify
by Johan Råde 07 Nov '06

07 Nov '06

Olivier, Håkan, Kan ni testa den här? Fungerar den här, så får den bli den slutgiltiga versionen. --Johan

1 0