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

[multi_index] multi index container with Managed C++
by Parag Gadkari 12 Apr '06

12 Apr '06

I am having trouble while using multi index container with the "managed c++" component. Here is the typedef that the compiler won't accept. typedef multi_index_container< gcroot<interface_entity*>, indexed_by< ordered_unique<identity<gcroot<interface_entity*> > >, ordered_non_unique<member<gcroot<interface_entity*>, int,&interface_entity::entity_drawingid> >, > > entity_collection; The real deal is with the member template which needs the address of member variable of the interface_entity class. Entity class is an abstract Managed type (specified with __gc), and it is not allowed to take the address of a non-static member of a managed type. Does anybody know of a workaround? Thanks Parag

2 3

Re: [Boost-users] Validating file names using regex
by Nat Goodspeed 12 Apr '06

12 Apr '06

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org [mailto:boost-users- > bounces(a)lists.boost.org] On Behalf Of Jean-Sebastien Vachon > Sent: Wednesday, April 12, 2006 3:38 PM > To: boost-users(a)lists.boost.org > Subject: [Boost-users] Validating file names using regex > > I am sure what I am looking for exist somewhere but I haven't > been able to find anything that works in boost::regex. > > What I am looking for is a regular expression that will validate > a filename according to the specification of the OS (UNIX systems > and Windows). > > I would be very grateful if someone could provide me with > these two expressions (one for Linux and one for Windows). [Nat] This isn't what you're asking for -- but would it work to instantiate a boost::filesystem::path with the putative pathname in question and an appropriate checker?

2 1

[xpression] fuzzy on smatch fields
by Lynn Allan 12 Apr '06

12 Apr '06

<alert comment="xpression newbie"> Xpressive looks very promising to be able to do some things I'm trying to implement. Thanks for providing and supporting it. I was trying to figure out the fields that make up xpression smatch'es, and expanded the Example-1 to be more verbose. Basically, I tried to "unpack" as much info as I could find in the variable "what" to clarify some fuzziness on my part. There were some questions: * The suffix and prefix info seemed blank. Are there accessors to get more info to conform to my (possibly flawed) understanding of the docs? * The return from regex_id seemed to be an address (like 00323F58). Is that intended? Is there some accessor to get something more meaningful? (but I'm not clear what would be meaningful). What is the purpose of "regex_id" to the user of xpressive? * With vc7.1, there were warnings unless I cast the lengths and positions ... is this intended? void example1_verbose() { std::string hello( "hello world!" ); sregex rex = sregex::compile( "(\\w+) (\\w+)!" ); smatch what; if( regex_match( hello, what, rex ) ) { std::cout << "Overall Size: " << static_cast<int>(what.size()) << '\n'; std::cout << "Regex Id: " << what.regex_id() << '\n'; std::cout << "what[0]: " << what[0] << '\n'; std::cout << "Length(0): " << static_cast<int>(what.length(0)) << '\n'; std::cout << "Position(0): " << static_cast<int>(what.position(0)) << '\n'; std::cout << "Str(0): " << what.str(0) << '\n'; std::cout << "what[1]: " << what[1] << '\n'; std::cout << "Length(1): " << static_cast<int>(what.length(1)) << '\n'; std::cout << "Position(1): " << static_cast<int>(what.position(1)) << '\n'; std::cout << "Str(1): " << what.str(1) << '\n'; std::cout << "what[2]: " << what[2] << '\n'; std::cout << "Length(2): " << static_cast<int>(what.length(2)) << '\n'; std::cout << "Position(2): " << static_cast<int>(what.position(2)) << '\n'; std::cout << "Str(2): " << what.str(2) << '\n'; std::cout << "Prefix(): " << what.prefix() << '\n'; std::cout << "Prefix().matched: " << what.prefix().matched << '\n'; std::cout << "Prefix().length(): " << static_cast<int>(what.prefix().length()) << '\n'; std::cout << "Prefix().str(): " << what.prefix().str() << '\n'; std::cout << "Suffix(): " << what.suffix() << '\n'; std::cout << "Suffix().matched: " << what.suffix().matched << '\n'; std::cout << "Suffix().length(): " << static_cast<int>(what.suffix().length()) << '\n'; std::cout << "Suffix().str(): " << what.suffix().str() << '\n'; } } Example 1: Verbose: Overall Size: 3 Regex Id: 00323F58 what[0]: hello world! Length(0): 12 Position(0): 0 Str(0): hello world! what[1]: hello Length(1): 5 Position(1): 0 Str(1): hello what[2]: world Length(2): 5 Position(2): 6 Str(2): world Prefix(): Prefix().matched: 0 Prefix().length(): 0 Prefix().str(): Suffix(): Suffix().matched: 0 Suffix().length(): 0 Suffix().str(): </alert>

2 5

link issues with BOOST_AUTO_TEST_CASE() facility
by Pierre-Jules Tremblay 12 Apr '06

12 Apr '06

I would like to use the BOOST_AUTO_TEST_CASE() facility in a static library. Obviously this library does not have a main() so it needs to be linked with a test executable which may run test cases found in one or more of those static libraries. Unfortunately, the tests do not make it past the linker. The executable links fine but runs none of the tests defined in the libraries. Could it be that BOOST_AUTO_TEST_CASE() works via some global which gets stripped when the static lib is created? Do you have a suggestion for a workaround? The idea is to keep some of the lowest-level unit test code in the same translation unit as the class implementation. Thanks, pj

2 3

Obscure error while trying to use Boost XML Serialization (boost::archive::xml_iarchive)
by Dilip 12 Apr '06

12 Apr '06

Hello all I am trying to use Boost Serialization library to de-serialize a complex object hierarchy from XML to its class representation. The class hierarchy gets serialized into XML just fine. But while trying to do the reverse, that is read from XML and pump it into my class, I run into the following compiler error that is driving me nuts. Can someone help please? FYI if its relevant I have a std::list<Stock*> datatype in one of the classes. The error dump is slightly big so I apologize in advance. The compiler is VC 7.1 on windows XP. C:\Boost\include\boost-1_33_1\boost\archive\detail\iserializer.hpp(487) : error C2440: 'reinterpret_cast' : cannot convert from 'const Stock **__w64 ' to 'void ** ' Conversion loses qualifiers C:\Boost\include\boost-1_33_1\boost\archive\detail\iserializer.hpp(484) : while compiling class-template member function 'void boost::archive::detail::load_pointer_type<Archive,Tptr>::invoke(Archive &,Tptr & )' with [ Archive=boost::archive::xml_iarchive, Tptr=const Stock * ] C:\Boost\include\boost-1_33_1\boost\archive\detail\iserializer.hpp(572) : see reference to class template instantiation 'boost::archive::detail::load_pointer_type<Archive,Tptr>' being compiled with [ Archive=boost::archive::xml_iarchive, Tptr=const Stock * ] C:\Boost\include\boost-1_33_1\boost\archive\basic_xml_iarchive.hpp(80) : see reference to function template instantiation 'void boost::archive::load<Archive,T>(Archive &,T & )' being compiled with [ Archive=boost::archive::xml_iarchive, T=const Stock * ] C:\Boost\include\boost-1_33_1\boost\archive\xml_iarchive.hpp(74) : see reference to function template instantiation 'void boost::archive::basic_xml_iarchive<Archive>::load_override<const X*>(const boost::serialization::nvp<T> &,int)' being compiled with [ Archive=boost::archive::xml_iarchive, X=Stock, T=const Stock * ] C:\Boost\include\boost-1_33_1\boost\archive\detail\interface_iarchive.hpp(76) : see reference to function template instantiation 'void boost::archive::xml_iarchive_impl<Archive>::load_override<T>(T &,int)' being compiled with [ Archive=boost::archive::xml_iarchive, T=const boost::serialization::nvp<const Stock *> ] C:\Boost\include\boost-1_33_1\boost\archive\detail\interface_iarchive.hpp(83) : see reference to function template instantiation 'Archive &boost::archive::detail::interface_iarchive<Archive>::operator >><T>(T &)' being compiled with [ Archive=boost::archive::xml_iarchive, T=const boost::serialization::nvp<const Stock *> ] MarketData.cpp(118) : see reference to function template instantiation 'Archive &boost::archive::detail::interface_iarchive<Archive>::operator &<const boost::serialization::nvp<T>>(const boost::serialization::nvp<T> &)' being compiled with [ Archive=boost::archive::xml_iarchive, T=const Stock * ] C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\include\algorithm(21) : see reference to function template instantiation 'void printeachlevel<T>::operator ()<Stock>(const X *& )' being compiled with [ T=boost::archive::xml_iarchive, X=Stock ] MarketData.cpp(131) : see reference to function template instantiation '_Fn1 std::for_each<std::list<_Ty>::iterator,printeachlevel<T>>(_InIt,_InIt,_Fn1)' being compiled with [ _Fn1=printeachlevel<boost::archive::xml_iarchive>, _Ty=Stock *, T=boost::archive::xml_iarchive, _InIt=std::list<Stock *>::iterator ] C:\Boost\include\boost-1_33_1\boost\serialization\access.hpp(109) : see reference to function template instantiation 'void Stocks::serialize<Archive>(Archive &,const unsigned int)' being compiled with [ Archive=boost::archive::xml_iarchive ] C:\Boost\include\boost-1_33_1\boost\serialization\serialization.hpp(81) : see reference to function template instantiation 'void boost::serialization::access::serialize<Archive,T>(Archive &,T &,const unsigned int)' being compiled with [ Archive=boost::archive::xml_iarchive, T=Stocks ] C:\Boost\include\boost-1_33_1\boost\serialization\serialization.hpp(140) : see reference to function template instantiation 'void boost::serialization::serialize<Archive,T>(Archive &,T &,const unsigned int)' being compiled with [ Archive=boost::archive::xml_iarchive, T=Stocks ] C:\Boost\include\boost-1_33_1\boost\archive\detail\iserializer.hpp(164) : see reference to function template instantiation 'void boost::serialization::serialize_adl<Archive,T>(Archive &,T &,const unsigned int)' being compiled with [ Archive=boost::archive::xml_iarchive, T=Stocks ] C:\Boost\include\boost-1_33_1\boost\serialization\extended_type_info_typeid.hpp(74) : while compiling class-template member function 'void boost::archive::detail::iserializer<Archive,T>::load_object_data(boost::archive::detail::basic_iarchive &,void *,const unsigned int) const' with [ Archive=boost::archive::xml_iarchive, T=Stocks ] C:\Boost\include\boost-1_33_1\boost\archive\detail\iserializer.hpp(375) : see reference to class template instantiation 'boost::archive::detail::iserializer<Archive,T>' being compiled with [ Archive=boost::archive::xml_iarchive, T=Stocks ] C:\Boost\include\boost-1_33_1\boost\archive\detail\iserializer.hpp(369) : while compiling class-template member function 'void boost::archive::detail::load_non_pointer_type<Archive,T>::load_standard::invoke(Archive &,T &)' with [ Archive=boost::archive::xml_iarchive, T=Stocks ] C:\Boost\include\boost-1_33_1\boost\archive\detail\iserializer.hpp(425) : see reference to class template instantiation 'boost::archive::detail::load_non_pointer_type<Archive,T>::load_standard' being compiled with [ Archive=boost::archive::xml_iarchive, T=Stocks ] C:\Boost\includ e\boost-1_33_1\boost\archive\detail\iserializer.hpp(418) : while compiling class-template member function 'void boost::archive::detail::load_non_pointer_type<Archive,T>::invoke(Archive &,T &)' with [ Archive=boost::archive::xml_iarchive, T=Stocks ] C:\Boost\include\boost-1_33_1\boost\archive\detail\iserializer.hpp(572) : see reference to class template instantiation 'boost::archive::detail::load_non_pointer_type<Archive,T>' being compiled with [ Archive=boost::archive::xml_iarchive, T=Stocks ] C:\Boost\include\boost-1_33_1\boost\archive\basic_xml_iarchive.hpp(80) : see reference to function template instantiation 'void boost::archive::load<Archive,T>(Archive &,T &)' being compiled with [ Archive=boost::archive::xml_iarchive, T=Stocks ] C:\Boost\include\boost-1_33_1\boost\archive\xml_iarchive.hpp(74) : see reference to function template instantiation 'void boost::archive::basic_xml_iarchive<Archive>::load_override<Stocks>(const boost::serialization::nvp<T> &,int)' being compiled with [ Archive=boost::archive::xml_iarchive, T=Stocks ] C:\Boost\include\boost-1_33_1\boost\archive\detail\interface_iarchive.hpp(76) : see reference to function template instantiation 'void boost::archive::xml_iarchive_impl<Archive>::load_override<T>(T &,int)' being compiled with [ Archive=boost::archive::xml_iarchive, T=const boost::serialization::nvp<Stocks> ] C:\Boost\include\boost-1_33_1\boost\archive\detail\interface_iarchive.hpp(83) : see reference to function template instantiation 'Archive &boost::archive::detail::interface_iarchive<Archive>::operator >><T>(T &)' being compiled with [ Archive=boost::archive::xml_iarchive, T=const boost::serialization::nvp<Stocks> ] MarketData.cpp(179) : see reference to function template instantiation 'Archive &boost::archive::detail::interface_iarchive<Archive>::operator &<const boost::serialization::nvp<T>>(const boost::serialization::nvp<T> &)' being compiled with [ Archive=boost::archive::xml_iarchive, T=Stocks ] C:\Boost\include\boost-1_33_1\boost\serialization\access.hpp(109) : see reference to function template instantiation 'void Securities::serialize<Archive>(Archive &,const unsigned int)' being compiled with [ Archive=boost::archive::xml_iarchive ] C:\Boost\include\boost-1_33_1\boost\serialization\serialization.hpp(81) : see reference to function template instantiation 'void boost::serialization::access::serialize<Archive,T>(Archive &,T &,const unsigned int)' being compiled with [ Archive=boost::archive::xml_iarchive, T=Securities ] C:\Boost\include\boost-1_33_1\boost\serialization\serialization.hpp(140) : see reference to function template instantiation 'void boost::serialization::serialize<Archive,T>(Archive &,T &,const unsigned int)' being compiled with [ Archive=boost::archive::xml_iarchive, T=Securities ] C:\Boost\include\boost-1_33_1\boost\archive\detail\iserializer.hpp(164) : see reference to function template instantiation 'void boost::serialization::serialize_adl<Archive,T>(Archive &,T &,const unsigned int)' being compiled with [ Archive=boost::archive::xml_iarchive, T=Securities ] C:\Boost\include\boost-1_33_1\boost\serialization\extended_type_info_typeid.hpp(74) : while compiling class-template member function 'void boost::archive::detail::iserializer<Archive,T>::load_object_data(boost::archive::detail::basic_iarchive &,void *,const unsigned int) const' with [ Archive=boost::archive::xml_iarchive, T=Securities ] C:\Boost\include\boost-1_33_1\boost\archive\detail\iserializer.hpp(375) : see reference to class template instantiation 'boost::archive::detail::iserializer<Archive,T>' being compiled with [ Archive=boost::archive::xml_iarchive, T=Securities ] C:\Boost\include\boost-1_33_1\boost\archive\detail\iserializer.hpp(369) : while compiling class-template member function 'void boost::archive::detail::load_non_pointer_type<Archive,T>::load_standard::invoke(Archive &,T &)' with [ Archive=boost::archive::xml_iarchive, T=Securities ] C:\Boost\include\boost-1_33_1\boost\archive\detail\iserializer.hpp(425) : see reference to class template instantiation 'boost::archive::detail::load_non_pointer_type<Archive,T>::load_standard' being compiled with [ Archive=boost::archive::xml_iarchive, T=Securities ] C:\Boost\include\boost-1_33_1\boost\archive\detail\iserializer.hpp(418) : while compiling class-template member function 'void boost::archive::detail::load_non_pointer_type<Archive,T>::invoke(Archive &,T &)' with [ Archive=boost::archive::xml_iarchive, T=Securities ] C:\Boost\include\boost-1_33_1\boost\archive\detail\iserializer.hpp(572) : see reference to class template instantiation 'boost::archive::detail::load_non_pointer_type<Archive,T>' being compiled with [ Archive=boost::archive::xml_iarchive, T=Securities ] C:\Boost\include\boost-1_33_1\boost\archive\basic_xml_iarchive.hpp(80) : see reference to function template instantiation 'void boost::archive::load<Archive,T>(Archive &,T &)' being compiled with [ Archive=boost::archive::xml_iarchive, T=Securities ] C:\Boost\include\boost-1_33 _1\boost\archive\xml_iarchive.hpp(74) : see reference to function template instantiation 'void boost::archive::basic_xml_iarchive<Archive>::load_override<Securities>(const boost::serialization::nvp<T> &,int)' being compiled with [ Archive=boost::archive::xml_iarchive, T=Securities ] C:\Boost\include\boost-1_33_1\boost\archive\detail\interface_iarchive.hpp(76) : see reference to function template instantiation 'void boost::archive::xml_iarchive_impl<Archive>::load_override<T>(T &,int)' being compiled with [ Archive=boost::archive::xml_iarchive, T=const boost::serialization::nvp<Securities> ] C:\Boost\include\boost-1_33_1\boost\archive\detail\interface_iarchive.hpp(83) : see reference to function template instantiation 'Archive &boost::archive::detail::interface_iarchive<Archive>::operator >><T>(T &)' being compiled with [ Archive=boost::archive::xml_iarchive, T=const boost::serialization::nvp<Securities> ] MarketData.cpp(209) : see reference to function template instantiation 'Archive &boost::archive::detail::interface_iarchive<Archive>::operator &<const boost::serialization::nvp<T>>(const boost::serialization::nvp<T> &)' being compiled with [ Archive=boost::archive::xml_iarchive, T=Securities ] C:\Boost\include\boost-1_33_1\boost\serialization\access.hpp(109) : see reference to function template instantiation 'void MarketData::serialize<Archive>(Archive &,const unsigned int)' being compiled with [ Archive=boost::archive::xml_iarchive ] C:\Boost\include\boost-1_33_1\boost\serialization\serialization.hpp(81) : see reference to function template instantiation 'void boost::serialization::access::serialize<Archive,T>(Archive &,T &,const unsigned int)' being compiled with [ Archive=boost::archive::xml_iarchive, T=Mar ketData ] C:\Boost\include\boost-1_33_1\boost\serialization\serialization.hpp(140) : see reference to function template instantiation 'void boost::serialization::serialize<Archive,T>(Archive &,T &,const unsigned int)' being compiled with [ Archive=boost::archive::xml_iarchive, T=MarketData ] C:\Boost\include\boost-1_33_1\boost\archive\detail\iserializer.hpp(164) : see reference to function template instantiation 'void boost::serialization::serialize_adl<Archive,T>(Archive &,T &,const unsigned int)' being compiled with [ Archive=boost::archive::xml_iarchive, T=MarketData ] C:\Boost\include\boost-1_33_1\boost\serialization\extended_type_info_typeid.hpp(74) : while compiling class-template member function 'void boost::archive::detail::iserializer<Archive,T>::load_object_data(boost::archive::detail::basic_iarchive &,void *,const unsigned int) const' with [ Archive=boost::archive::xml_iarchive, T=MarketData ] C:\Boost\include\boost-1_33_1\boost\archive\detail\iserializer.hpp(375) : see reference to class template instantiation 'boost::archive::detail::iserializer<Archive,T>' being compiled with [ Archive=boost::archive::xml_iarchive, T=MarketData ] C:\Boost\include\boost-1_33_1\boost\archive\detail\iserializer.hpp(369) : while compiling class-template member function 'void boost::archive::detail::load_non_pointer_type<Archive,T>::load_standard::invoke(Archive &,T &)' with [ Archive=boost::archive::xml_iarchive, T=MarketData ] C:\Boost\include\boost-1_33_1\boost\archive\detail\iserializer.hpp(425) : see reference to class template instantiation 'boost::archive::detail::load_non_pointer_type<Archive,T>::load_standard' being compiled with [ Archive=boost::archive::xml_iarchive, T=MarketData ] C:\Boost\include\boost-1_33_1\boost\archive\detail\iserializer.hpp(418) : while compiling class-template member function 'void boost::archive::detail::load_non_pointer_type<Archive,T>::invoke(Archive &,T &)' with [ Archive=boost::archive::xml_iarchive, T=MarketData ] C:\Boost\include\boost-1_33_1\boost\archive\detail\iserializer.hpp(572) : see reference to class template instantiation 'boost::archive::detail::load_non_pointer_type<Archive,T>' being compiled with [ Archive=boost::archive::xml_iarchive, T=MarketData ] C:\Boost\include\boost-1_33_1\boost\archive\basic_xml_iarchive.hpp(80) : see reference to function template instantiation 'void boost::archive::load<Archive,T>(Archive &,T &)' being compiled with [ Archive=boost::archive::xml_iarchive, T=MarketData ] C:\Boost\include\boost-1_33_1\boost\archive\xml_iarchive.hpp(74) : see reference to function template instantiation 'void boost::archive::basic_xml_iarchive<Archive>::load_override<MarketData>(const boost::serialization::nvp<T> &,int)' being compiled with [ Archive=boost::archive::xml_iarchive, T=MarketData ] C:\Boost\include\boost-1_33_1\boost\archive\detail\interface_iarchive.hpp(76) : see reference to function template instantiation 'void boost::archive::xml_iarchive_impl<Archive>::load_override<T>(T &,int)' being compiled with [ Archive=boost::archive::xml_iarchive, T=const boost::serialization::nvp<MarketData> ] MarketData.cpp(223) : see reference to function template instantiation 'Archive &boost::archive::detail::interface_iarchive<Archive>::operator >><const boost::serialization::nvp<T>>(const boost::serialization::nvp<T> &)' being compiled with [ Archive=boost::archive::xml_iarchive, T=MarketData ] C:\Boost\include\boost-1_33_1\boost\archive\detail\iserializer.hpp(493) : error C2664: 'const T *boost::archive::detail::load_pointer_type<Archive,Tptr>::pointer_tweak<const X>(const boost::serialization::extended_type_info &,void *,const T &)' : cannot convert parameter 2 from 'const Stock *' to 'void *' with [ T=Stock, Archive=boost::archive::xml_iarchive, Tptr=const Stock *, X=Stock ] Conversion loses qualifiers

1 1

Boost.Test - memory allocated during test case run prevents memory leak detection?
by Pierre-Jules Tremblay 12 Apr '06

12 Apr '06

We use Boost.Test extensively as our unit test framework. Recently, we introduced some code to check for memory leaks. Each test case is expected to release all the memory it allocates (i.e. fixtures and what not). However, we observe that several of our test cases appear to leak memory when in fact they don't. For instance, a memory leak check when main() exits reveals no leaks, even though leaks were "found" in several test cases. Our observation is that the apparent leaks appear and disappear as we modify the test code. Scrutinizing the code has revealed that adding a BOOST_REQUIRE(true) here and there in the problematic test cases can make this problem go away. Is it at all possible that Boost.Test somehow allocates memory during a test case run, say for logging or other purpose, and doesn't release it before the test case ends? Here is the code we use to check for memory leaks after each test case is run: #define DECLARE_TEST_CASE(name) \ void test##name##__(); \ void test##name##() \ { \ mytestlib::TestCaseResetLeakCheck(); \ const uint32 uiMemUsageBeforeTest = MMGetAllocatedBytes(); \ test##name##__(); \ const uint32 uiMemUsageAfterTest = MMGetAllocatedBytes(); \ const uint32 uiMemUsageDiff = uiMemUsageBeforeTest > uiMemUsageAfterTest ? uiMemUsageBeforeTest - uiMemUsageAfterTest : uiMemUsageAfterTest - uiMemUsageBeforeTest; \ if (uiMemUsageDiff) \ { \ if (mytestlib::TestCaseLeakCheck()) \ { \ BOOST_ERROR("Test " #name " has memory leaks (" << uiMemUsageAfterTest << " != " << uiMemUsageBeforeTest << ", " << uiMemUsageDiff << " bytes leaked)"); \ } \ else \ { \ BOOST_WARN_MESSAGE(false,"Test " #name " has memory leaks (" << uiMemUsageAfterTest << " != " << uiMemUsageBeforeTest << ", " << uiMemUsageDiff << " bytes leaked) (marked as expected)"); \ } \ } \ } \ void test##name##__() DECLARE_TEST_CASE( SomeTest ) { // arbitrary test code goes here... }

2 2

[regex_spirit_xpressive] Are timings of search algo's available vs "by-hand"?
by Lynn Allan 12 Apr '06

12 Apr '06

<alert comment="boost newbie"> I've been impressed by the functionality provided by the regex-related libraries in boost that I've looked at so far. However, before trekking to far-distant "grok-land" off in the mists, I wanted to get some idea if there were negligible or minor or major performance tradeoffs. I've seen comparisons between regex, spirit, and xpressive (that were from several years ago and probably obsolete .... done by the library developers). I'm wondering how these would compare to a "hand-tuned" state-machine routine, and to an automatically generated state-machine from a FSM utility (tend to be bloated but can be fast). My interest is specialized to finding which pattern in a "group" of patterns was detected, and the offset within the testStr. To illustrate, the regex would be something like detecting the full or abbreviated Day-Of-Week: ((Sunday|Sun)|(Monday|Mon)|(Tuesday|Tue) |(Wednesday|Wed)|(Thursday|Thu) |(Friday|Fri)|(Saturday|Sat)) The testStr is something like: std::string testStr = "Alternate days of the week are Tue and Thursday and Sat and Monday. " "And then Monday and Wed and Friday and Sun. " "Near misses are WeD TuE ThU SuN SaT MoN FrI "; The real application is inputting a batch of 2mb files and generating SGML-like output with embedded tags. (e.g. enclose Tue in <dow=2>Tue</dow> and <dow=4>Thursday</dow>) The above seems like the kind of task for which regex libraries would be appropriate, would be beyond strstr, but wouldn't be excessively difficult to accomplish "by hand". The unknown is whether there is a perfomance trade-off in using a regex library, and whether it is positive, negative, minor, or major. I've started some preliminary timings with vc7.1 release /O2 build with HiResTimer using QueryPerformanceTimer in ABOVE_NORMAL_PRIORITY_CLASS Before proceeding much further, this newbie thought it would be good to check if people with real boost experience have done this kind of benchmarking. A search for "benchmark" and "timings" in boost-user and boost-devel didn't turn up much. Preview: so far the preliminary results look VERY GOOD, but "consider the source". </alert>

1 0

[test] Possible race condition? (minor)
by Paul Giaccone 12 Apr '06

12 Apr '06

Boost unit test framework seems to have a race condition in its output. When I run my test program from a shell, I get this output: paulg@klingon 120% ./CubicTest Running 8 test cases... *** No errors detected paulg@klingon 121% ./CubicTest>/dev/null *** No errors detected Note that the second call above, redirecting output to /dev/null, suggests to me that "Running 8 test cases..." goes to standard out and "*** No errors detected" goes to standard error. Because standard error is unbuffered, this can mean that the messages are output in the reverse order. This is the case when I run my program from Eclipse (under Linux), and, in general, will happen if the tests run faster than the time it takes for the buffer to flush to the output. This suggests one of the following is required: * Flush standard out before running the tests * Send all output to the same stream (but this is not recommended, as this would break the defined behaviour of test suites) * Synchronise the two streams by some other means It's possible that Eclipse displays the output to standard error before the output from standard out, but such behaviour isn't seen when executing a makefile, so it seems likely there there is a race condition in Boost unit test framework. Paul

2 1

multi_array math operation.
by chun ping wang 12 Apr '06

12 Apr '06

Question 1: How would i add or subtract multiarray given the fact that i don't know the dimension of it... Like its N dimension where N = 4. and u know both Multi_array A and Multi_Array B has [x][y][z][w] dimension and u want to add them together. Question 2: are there any built in operator for that...the built in + only does pointers address not adding actual object together.

1 0

[xpressive&regex&spirit] Can previous regex be cached?
by Lynn Allan 12 Apr '06

12 Apr '06

<alert comment=<boost newbie"> Xpressive provides a "tips n tricks" to: Compiling a regex (dynamic or static) is more expensive than executing a match or search. If you have the option, prefer to compile a pattern into a basic_regex<> object once and reuse it rather than recreating it over and over. Would it be feasible/advantageous for the regex-related libraries to automagically to "cache" the immediately previous regex compilation? (or provide as an option) I've seen code that had the same regex being compiled inside a loop, which I suppose would really diminish performance. Perhaps this could be detected, and the user/developer "protected from themselves" ... and/or perhaps informed that this is happening? Could there be a "helper" class that somehow or other allowed the last "n" regexes to be cached? (btw .... what is the plural of regex .... regexen? regices?) </alert>

2 1