January 2008 - Boost-users - lists.preview.boost.org

boost.xpressive is inefficient while seaching in raw bytes
by Aries Tao 30 Jan '08

30 Jan '08

hi everybody,I use boost.xpressive to search email address in a binary file which size is 10*1024*1024 bytes. every bytes is 0x6f in that file.boost.xpressive is inefficient. anyone can help me? thanks! the code is below: //read file CFile file(_T("d:\\test.dat"),CFile::modeRead ); byte* pBuffer = new byte[file.GetLength()]; file.Read(pBuffer,file.GetLength()); std::string str((char*)pBuffer,file.GetLength()); sregex token = sregex::compile("([a-z#~_\\.!\\#$%\\^&\\*\$\$\\-]+(a)[a-z#_\\-]+\\.[a-z#_\\-\\.]+)"); sregex_iterator cur( str.begin(), str.end(), token ); sregex_iterator end; for( ; cur != end; ++cur ) { smatch const &what = *cur; std::string strResult = what[0]; int start = what[0].first - str.begin(); } _________________________________________________________________ Helping your favorite cause is as easy as instant messaging. You IM, we give. http://im.live.com/Messenger/IM/Home/?source=text_hotmail_join

4 9

Generic indexing by "const char *"
by Joseph Fradley 29 Jan '08

29 Jan '08

I have a problem that I would like to solve in the most generic non-intrusive way possible (such as boost serialization). What I want is to access class members both via it's initially designed accessors but also via a "const char *" key. In addition, I want to pass list of key's (via a vector of const char * or a single delimited multikey char *) to get nested member access. For example: ... // these should be equivalent Point p; int val; val = p.x; val = p.getX(); p.getMemberValue("x", val); // there also Rectangle r; int val; Point pVal; r.getMemberValue("corner:x", val); r.getMemberValue("corner", pVal); I thought about having a templated function similar to the serialize() function called 'getMemberValue()', where each 'if' block below could be wrapped into a MACRO taking just the member name. template< class T > bool getMemberValue(const char *key, T & value) { if(!strcmp(key, "member")) { value = this->member; return true; } return false; } This appears to work fine for one level deep but if I want the behavior such as the above rectangle example, I run into trouble. I end up with a function implementation like this for the 'Rectangle' class template< Point > bool getMemberValue(const char *key, Point & value) { if(!strcmp(key, "corner")) { value = this->corner; // Point return true; } if(!strcmp(key, "width")) { value = this->width; // int return true; } if(!strcmp(key, "height")) { value = this->height; // int return true; } return false; } This fails because it ends up trying to set an integer value to a Point variable. Anybody have any suggestions? Joe

4 6

isinf & Boost
by metty 29 Jan '08

29 Jan '08

Hi All, I have to use isinf in an application. The application was originally written using gcc (under linux) which supports isinf. I want to port it to Windows and VC++ doesn't seem to support it. I googled around and I think the "omnipotent" Boost has something to help with this. Unfortunately, I couldn't get the details of how to make use of it. I would be grateful if someone can help me? Thank you in advance! metty ____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ

4 6

[flyweight] Review period extended to February 3
by Ion Gaztañaga 29 Jan '08

29 Jan '08

Hi to all, We've received 4 positive reviews and several comments, but we still want more ;-) Some people expressed interested in the pre-review period and I want to give some time (weekend is the right time to review a Boost library...) to those who are interested in the library and have not found time to review it. The last review day is February 3. Common, the library is very lightweight ;-) to review, it's pretty well documented, it's certainly small and very general purpose. Here is the information. Last call to passengers! *Description:* Flyweights are small-sized handle classes granting constant access to shared common data, thus allowing for the management of large amounts of entities within reasonable memory limits. Boost.Flyweight makes it easy to use this common programming idiom by providing the class template flyweight<T>, which acts as a drop-in replacement for const T. *Online docs:* http://tinyurl.com/2sstyr http://svn.boost.org/svn/boost/sandbox/flyweight/libs/flyweight/index.html *Download:* http://tinyurl.com/hrdm6 http://www.boost-consulting.com/vault/index.php?&direction=0&order=&directo… *Notes:* 1) We've seen some suggestions in the mailing list for Flyweight. Joaquín has nicely explained a couple of issues that we'd like to address/discuss in the review: http://tinyurl.com/33ghtf http://svn.boost.org/svn/boost/sandbox/flyweight/libs/flyweight/doc/review_… 2) Flyweight needs Boost 1.35 elements because the library depends on libraries like Interprocess for some features/tests. Since SVN snapshot tarballs seem to be missing these days, those who want to try flyweight can download a working SVN-HEAD snapshot here: http://igaztanaga.drivehq.com/boost_trunk.tar.bz2 3) Serialization tests won't work. This feature is expected to work when some new features (discussed in the mailing list between Joaquín and Robert Ramey) are added in Boost.Serialization. Those are expected for Boost 1.36. What to include in Review Comments ================================== Your comments may be brief or lengthy, but basically the Review Manager needs your evaluation of the library. If you identify problems along the way, please note if they are minor, serious, or showstoppers. Here are some questions you might want to answer in your review: * What is your evaluation of the design? * What is your evaluation of the implementation? * What is your evaluation of the documentation? * What is your evaluation of the potential usefulness of the library? * Did you try to use the library? With what compiler? Did you have any problems? * How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? * Are you knowledgeable about the problem domain? And finally, every review should answer this question: * Do you think the library should be accepted as a Boost library? Be sure to say this explicitly so that your other comments don't obscure your overall opinion. Ion Gaztañaga - Review Manager -

1 0

[thread_safe_signals] multi_threaded.hpp uses same #ifdef as auto_threaded.hpp - no inclusion possible
by raimar wagner 29 Jan '08

29 Jan '08

Hi! yet another thread_safe_signals problem :-) : auto_threaded.hpp: > #ifndef BOOST_SIGNALS_MULTI_THREADED_MODEL_HEADER > #define BOOST_SIGNALS_MULTI_THREADED_MODEL_HEADER multi_threaded.hpp: > #ifndef BOOST_SIGNALS_MULTI_THREADED_MODEL_HEADER > #define BOOST_SIGNALS_MULTI_THREADED_MODEL_HEADER For using multi-thread support the documentations says: "Thus boost/signals/multi_threaded.hpp is not automatically included when you include boost/signal.hpp, and must be included separately if you wish to use multi_threaded." but this can't work because "auto_threaded.hpp" is included in "thread_safe_signal.hpp", thus every (later) include of "multi_threaded.hpp" does nothing. My workaround was just changing multi_threaded.hpp to > #ifndef BOOST_SIGNALS_MULTI_THREADED_MODEL_HEADER_MULTI > #define BOOST_SIGNALS_MULTI_THREADED_MODEL_HEADER_MULTI but this should also be changed in the downloadable archives. Kindest regards Raimar Wagner

2 1

[thread_safe_signals] Qt/MOC Linker problem with header-only thread_safe_signals-library
by raimar wagner 29 Jan '08

29 Jan '08

Hi! I'm using the "thread_safe_signals"-library in a Qt-Context. I have a file "foo.cpp" containing Qt-stuff which is processed by the moc before it compiles. foo.cpp: > #include "foo.h" > > ... Qt-stuff ... > foo.h: > #include "bar.h" > > ... Qt-declarations .. > bar.h: > #include <boost/thread_safe_signal.hpp> > #include <boost/thread_safe_signals/multi_threaded.hpp> > #include <boost/bind.hpp> > > ... > Now the following happens: 1.) The Qt moc creates moc_foo.cpp based on foo.cpp 2.) everything compiles fine ("g++ (GCC) 4.1.0 (SUSE Linux)" using SCons on SUSE 10.1) 3.) The linking process fails with: > build/release/src/foo.os: In function `boost::signalslib::null_deleter(void const*)': > /path_to_boost/include/boost/thread_safe_signals/connection.hpp:42: multiple definition of ` > boost::signalslib::null_deleter(void const*)' > build/release/src/bar.os:/path_to_boost/include/boost/thread_safe_signals/connection.hpp:42: first > defined here > build/release/src/foo_moc.os: In function `boost::signalslib::null_deleter(void const*)': > /path_to_boost/include/boost/thread_safe_signals/connection.hpp:42: multiple definition of > `boost::signalslib::null_deleter(void const*)' > build/release/src/bar.os:/path_to_boost/include/boost/thread_safe_signals/connection.hpp:42: first > defined here > collect2: ld returned 1 exit status Our workaround was to edit connection.hpp from: 42: > void null_deleter(const void*) {} to 42: > void null_deleter(const void*); and add to bar.cpp: > namespace boost > { > namespace signalslib > { > void null_deleter(const void*) {} > } > } This works, but maybe there is a better solution to cope with this problem. Any ideas? Kindest regards Raimar Wagner

2 1

Building 64-bit Boost Libraries on Windows
by Trueman, Christopher 29 Jan '08

29 Jan '08

I'm continuing to have trouble compiling 64-bit versions of the Boost libraries on Windows using VS2008. I've used a number of the tips posted online including: bjam --toolset=msvc-9.0 address-space=64 but watching the Task Manager I see that it always launches the 32-bit version of the compiler. Does someone have the correct BJAM command line to make this work? I'm using Boost 1.34.1 which I patched in a couple of places to have it recognize the 9.0 (internally version 15) VS 2008 toolset. Any help much appreciated. Thanks. Chris. _______________________________________________________ The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify the sender immediately, and then destroy it.

3 2

[Filesystem] Crashes with global const path
by Hughes, James 29 Jan '08

29 Jan '08

Hello all, We have had problems with boost::path when used as a const global variable, using gcc on ARM Linux. Example code (typed in the the email so probably missing code, but this is the basic premise) #include <boost/filesystem/path.hhp> const boost::path test = "/usr/bin/whatever"; main() { //something } This crashes prior to getting to main, obviously whilst the path is being set up during initialisation. Is this a known problem? Is there a way round it? Have we misunderstood something important? Path works fine elsewhere, its only when some sort of initialisation code is called that it goes pear shaped. James This message (including any attachments) contains confidential and/or proprietary information intended only for the addressee. Any unauthorized disclosure, copying, distribution or reliance on the contents of this information is strictly prohibited and may constitute a violation of law. If you are not the intended recipient, please notify the sender immediately by responding to this e-mail, and delete the message from your system. If you have any questions about this e-mail please notify the sender immediately.

2 2

Serialization of pointers to PODs
by Joseph Fradley 29 Jan '08

29 Jan '08

Is it possible using the boost serialization libraries to serialize pointers to PODs, such as integers? I have tested successfully with pointers to classes but have not been able to get pointers to non-polymorphic serialized. Is this a known issue? Joe

2 3

[review] Fast track review of Boost.Utility/Singleton - rejected for now
by John Torjo 29 Jan '08

29 Jan '08

Hi all, We've gotten a lot of feedback on the Boost.Utility/Singleton. It's clear that such an addition would be beneficial to Boost, but I've chosen to reject the library at this time. Summary: - 4 positive reviews - 4 negative reviews Phil Endecott - yes Nat Goodspeed - yes Dherring[@]ll[]mit[]edu - yes Ingolf Steinbach - yes Anthony Williams - no Gennady - no Pierre-Jules Tremblay - no Michael Marcin - no The main concern was that the library is not flexible enough, and that it imposes too many things on the users (like, if BOOST_HAS_THREADS is defined, the singleton is automatically thread-safe). I would like to see this into Boost, so I hope Tobias will update the library, given all this feedback, and I would suggest another review in 2-3 months. I'd like to be the review manager then as well, if Tobias will still want me. Suggestions: * Should use policies to specify creation/destruction, access to singleton, resurection For creation/destruction, one should be able to have singleton<single_thread<T> >, singleton< synchronized<T> >, singleton< thread_specific<T> > * example for DLL support * more detailed docs As for the next review of the library, I will talk to Tobias, and let the review wizard know. Thanks to Tobias, for the lib, and to all that participated to the review! Best, John - Review Manager - -- http://John.Torjo.com -- C++ expert ... call me only if you want things done right

2 3