- Boost-users - lists.boost.org

[asio] socket::read_some() splits data into two parts.
by Slav 12 May '11

12 May '11

Hello. I sent 8004 bytes to server through TCP connection and successfully read it like this: int readBytes; const int BUFFER_SIZE = 128; char charBuf[BUFFER_SIZE]; do { readBytes = socket.read_some(boost::asio::buffer(charBuf, BUFFER_SIZE)); } while(readBytes >= BUFFER_SIZE); But sometimes this code reads just 3752 (precisely) bytes and returns. After that it handles another async_read and reads 4525 bytes (which in sum gives 8004 bytes). Do I use "read_some()" function in the right way?

8 22

Re: [Boost-users] [msm] EUML in a header file
by Christophe Henry 12 May '11

12 May '11

> A couple more questions. I think you may be missing some more const specifiers in the trunk code. In common.hpp for instance, I think the following > > #define BOOST_MSM_EUML_EVENT(instance_name) \ > struct instance_name ## _helper : msm::front::euml::euml_event<instance_name ## _helper>{ \ > instance_name ## _helper(){} \ > instance_name ## _helper const& operator()(){return *this;} }; \ > instance_name ## _helper const instance_name = instance_name ## _helper(); > > should be > > #define BOOST_MSM_EUML_EVENT(instance_name) \ > struct instance_name ## _helper : msm::front::euml::euml_event<instance_name ## _helper>{ \ > instance_name ## _helper(){} \ > instance_name ## _helper const& operator()() const {return *this;} }; \ > instance_name ## _helper const instance_name = instance_name ## _helper(); > > If the operator() is not const then it can't be called on the defined instance. I forgot why I need this, to be frank, I need to have a look at it. > Also, the addition of "= instance_name ## _helper();" makes the macros unusable in class definitions since instance_name is not static. Ouch. How could I miss that one? This leaves me with as only choice your first solution with static and extra macros for the name. Thanks, Christophe

1 0

[boost.asio] Is it safe to call write() and async_read at the same time?
by Frank 12 May '11

12 May '11

Is it safe to do the following in boost.asio? If it matters, I am using a serial port at the moment, but the code will be used for sockets as well. If not, what is the proper way to implement this to get full duplex communication? Thread 1: write(conn, buffer1) Thread 2: async_read(conn, buffer2)

3 5

logic operation in boost polygon
by HxH 12 May '11

12 May '11

Help! I wrote this function to load the data point to a boost polygon. typedef vector<polygon_data<int> > LayoutSet; static void addPolygonData(LayoutSet &sets,int* points,int size){ polygon_data<int> poly_data; vector<point_data<int> > poly_points(size); for(int i=0;i<size;i++) { int x=i*2; int y=x+1; poly_points[i]=point_data<int>(points[x],points[y]); } poly_data.set(poly_points.begin(),poly_points.end()); sets.push_back(poly_data); } Then I load two sets of points int p1[8]={1200 2400 1200 3600 4000 3600 4000 2400}; int p2[8]={1800 600 1800 4700 3500 4700 3500 600}; LayoutSet group_2; LayoutSet group_1; addPolygonData(group_1,p1,8); addPolygonData(group_1,p2,8); boost::polygon::assign(group_2,group_1[0] & group_1[1]); // Here I do the logic operation & (AND) vector<point_data<int> > pts; pts.insert(pts.begin(),group_2[0].begin(),group[0].end()); for(size_t i=0;i<group_2[0].size();i++){ cout<<pts[i].x()<<","<<pts[i].y()<<endl; } Here is the result I get: 6484944,0 3500,600 3500,3600 1800,3600 1800,600 3,1 0,0 6484944,0 It doesn't look correct. It gives me a hard time to fix it. Any suggestions are welcome!! Thank you! -- View this message in context: http://boost.2283326.n4.nabble.com/logic-operation-in-boost-polygon-tp35123… Sent from the Boost - Users mailing list archive at Nabble.com.

3 4

Re: [Boost-users] [msm] EUML in a header file
by Nate Knight 12 May '11

12 May '11

Christophe Henry <christophe.j.henry <at> googlemail.com> writes: > > >Christophe Henry <christophe.j.henry <at> googlemail.com> writes: > > > >> You can also provide your own instances inside a front-end definition, > >> thus eliminating the problem completely, as in: > >> > >http://www.boost.org/doc/libs/1_46_0/libs/msm/doc/HTML/examples/SimpleTutor… > >> A couple more questions. I think you may be missing some more const specifiers in the trunk code. In common.hpp for instance, I think the following #define BOOST_MSM_EUML_EVENT(instance_name) \ struct instance_name ## _helper : msm::front::euml::euml_event<instance_name ## _helper>{ \ instance_name ## _helper(){} \ instance_name ## _helper const& operator()(){return *this;} }; \ instance_name ## _helper const instance_name = instance_name ## _helper(); should be #define BOOST_MSM_EUML_EVENT(instance_name) \ struct instance_name ## _helper : msm::front::euml::euml_event<instance_name ## _helper>{ \ instance_name ## _helper(){} \ instance_name ## _helper const& operator()() const {return *this;} }; \ instance_name ## _helper const instance_name = instance_name ## _helper(); If the operator() is not const then it can't be called on the defined instance. Also, the addition of "= instance_name ## _helper();" makes the macros unusable in class definitions since instance_name is not static.

1 0

[signals2] compilation issues with gcc4.4 and -pedantic
by Christophe Bourez 12 May '11

12 May '11

The following code: #include <boost/signals2.hpp> int main(int , char *[]) { return 0; } compiles fine with gcc-4.1 and gcc-4.2 and the -pedantic option, but generates the following errors using gcc-4.4 with the same compiling options: /home/build/repository/boost-1.46.1-2/gcc-4.4/include/boost/signals2/detail/preprocessed_arg_type_template.hpp:21: error: invoking macro BOOST_SIGNALS2_PREFIXED_ARGS_TEMPLATE_DECL argument 2: empty macro arguments are undefined in ISO C90 and ISO C++98 /home/build/repository/boost-1.46.1-2/gcc-4.4/include/boost/signals2/detail/preprocessed_arg_type_template.hpp:21: error: invoking macro BOOST_PP_CAT argument 1: empty macro arguments are undefined in ISO C90 and ISO C++98 /home/build/repository/boost-1.46.1-2/gcc-4.4/include/boost/signals2/detail/preprocessed_arg_type_template.hpp:21: error: invoking macro BOOST_PP_CAT_I argument 1: empty macro arguments are undefined in ISO C90 and ISO C++98 Adding the option -std=c++0x removes these errors, but I am supporting legacy code that does not compile with -std=c++0x Is there any workaround or patch I could apply ? Thank you, Christophe

3 3

Unwanted implicit conversions to bool
by Dominik Steenken 12 May '11

12 May '11

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello everyone, i am having a bit of a problem using boost/hash in combination with boost/shared_ptr. Essentially, what i want when i hash a shared_ptr object is to hash the object it points to. So i wrote a template function to that effect, i.e. inline std::size_t hash_value(boost::shared_ptr<const IHashable> obj) { return obj->hash_value(); } where IHashable is an interface forcing the existence of the hash_value() function. Now i am getting compiler errors because apparently there is an implicit conversion to bool from boost::shared_ptr<T> and obviously there is a hash function for bool. Thus, something like boost::shared_ptr<IHashable> p(new something()); boost::hasher<something> hasher; std::size_t hash = hasher(p); is now ambiguous. I already found the BOOST_HASH_NO_IMPLICIT_CASTS switch, but it does not seem to change anything. I still get compiler errors like this one: In file included from /usr/include/boost/functional/hash/hash.hpp: 494:0, from /usr/include/boost/functional/hash.hpp:6, from types/../common.h:14, from types/variables.h:11, from types/abstractformula.h:11, from types/unaryoperations.h:11, from types/unaryoperations.cpp:1: types/unaryoperations.cpp:49:37: instantiated from here /usr/include/boost/functional/hash/extensions.hpp:176:34: error: call of overloaded ?hash_value(const boost::shared_ptr<terms::CAbstractFormula>&)? is ambiguous /usr/include/boost/functional/hash/hash.hpp:120:24: note: candidates are: size_t boost::hash_value(bool) types/../common.h:86:24: note: size_t terms::hash_value(boost::shared_ptr<const terms::IHashable>) Any idea on what i could to to prevent this would be greatly appreciated. cheers, Dominik -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJNy70+AAoJEPKXvh6MABK35dkQAKRFv48yZ7XyZh/6F+SSh02G IBfSEMi/xMXerLRH+/FV2lB6/gx1tymkYXxF02gopfIlavHHTWPz0vnkqZYFAABq ZzLMpggx4G50KtUGZfeKKfMGdbR5+0AHHT5ZRuL6aTzsvgr6nMYDdxwBKlAPvTJv nDuH8fHaV2QU6tw8OSmqzsdtiKrA4rnSqLPg4T6g/e/EqvH2Pf8GkXowRVK0T9Sq uAPnqcNZcMPuaIbtACC+AzsVA3CBw5fFQktRVbkLUtqDRVr10a9qOxgnDo6b7Duz c/KGNnWH2n1Lnwp9GbrvZoScqwThr9WqBvdcITD3ivgAkWhy5Fy6pnR1leRZhbZ7 +eFv3c1tY7b4yE7I9qCfRwW8LDhnkAJ/nAdcmGhWNX8RRSkETTguoCe9KUPMPoSs MBUEVk8VUNC9J3/JQmxlDhVju4WvJjlAnYrf7zir2XTFQ7v5eP86BeXkYArl+eyg OI2qRVp2ZuhReorwDc09Hef4/NrXPy3Bpq5nEWsref/mBbsyeopH3wqTZBrtruky RtSiJInhm4CETfMVJ8aJh/QO3MzGw2PXRLLCQ/mR2xHRgvEWOH53r84/1s8H3uSA URvXvPLKBuTpog30+GhHgfWOYx1/1Hy3atHbR9XikNW9y6Pv8IxUISA4AaQXNZyn XkjTDMHQ5XAqj/6Etgr7 =ak4K -----END PGP SIGNATURE-----

4 3

[Thread] Assert after reloading multiple times a .so linked with the static build of Boost.Thread
by Sorin Fetche 12 May '11

12 May '11

Hi, The attached test program shows that after a few hundred reloads of a shared library linked with the static build of Boost.Thread, an assert will be raised (gcc 4.4; boost 1.46.1). Does this show a valid bug in a supported usage pattern? ./a.out Call: 0 Call: 100 Call: 200 Call: 300 Call: 400 Call: 500 a.out: /home/sfetche/local/boost/src/boost_1_46_1/boost/thread/pthread/condition_variable_fwd.hpp:46: boost::condition_variable::~condition_variable(): Assertion `!pthread_mutex_destroy(&internal_mutex)' failed. Aborted The test program demonstrates the usage of a shared library that exposes a C interface and is implemented using statically linked Boost libraries. This approach has been taken in order to allow different modules using different versions of Boost to get (re)loaded in the same plugin-based application and has been inspired by this discussion: http://lists.boost.org/Archives/boost/2005/09/94134.php Thank you, Sorin Fetche

1 1

truncate file to n bytes
by Andrej van der Zee 12 May '11

12 May '11

Hi, I was wondering is there is any way to truncate the file-size to n bytes, while deleting from the end of the file? Does boost::filesystem support something like this? Thank you, Andrej

2 1

[boost::property_tree] how to put to paths with '/' slashes?
by Julien Claassen 12 May '11

12 May '11

Hello everyne! I'm just looking at the property_tree and wonder, if I can do something like this: ptree my_tree; my_tree.put('/',"/path/to/my.node","hello world"); The get functions support this syntax, but I didn't see anything corresponding to it with put ? Any ideas, workarounds? Kind regards and thanks Julien -------- Music was my first love and it will be my last (John Miles) ======== FIND MY WEB-PROJECT AT: ======== http://ltsb.sourceforge.net the Linux TextBased Studio guide ======= AND MY PERSONAL PAGES AT: ======= http://www.juliencoder.de

2 2