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

[regex] matchinf info with merged regex
by Line Oddskool 13 Jul '06

13 Jul '06

Hi boost.regex gurus, I'm stuck with a problem dealing with some kind of regex merging (using boost 1.33). I don't know if the way I took is viable, so any ideas and advice will be appreciated. To give you some insight, i have a set of a hundred matching (ei) and formating (ri) "rules" e.g. e1 : (a)(?=ll) r1 : (?1o) e1/r1 should mean "matching 'a' of some string like 'all' should be replaced by 'o'" I merge all my e/r into one big regex using regex_merge (for performance), so the resulting matching/formating regex is like : e : e1|e2|...|en r: r1r2...rn I'm getting weird behaviour with this, as the resulting string is sometimes filled with sequences like 'u4u5u6u7u8u9u' or other "trash". So to debug this, I'd like to know which rule (i.e. which ei) matched on what part of the string. I'm unsure if it's possible to get some kind of iterator on the rules that have matched using regex_merge ? I also looked at the match_results returned by the simpler method regex_match(), but I can't figure out how to know which part of my matching regex matched (i.e. which ei) ? Otherwise, is there a way to analyse or dump the matching/replacing behaviour of such a complex regex ? Thanks Line.

2 3

[Iterator] const and an iterator's value_type
by Daniel Mitchell 13 Jul '06

13 Jul '06

In the documentation of iterator_facade it is stated that: "The C++ standard requires an iterator's value_type not be const-qualified, so iterator_facade strips the const from its Value parameter in order to produce the iterator's value_type. Making the Value argument const provides a useful hint to iterator_facade that the iterator is a constant iterator, and the default Reference argument will be correct for all lvalue iterators." and "when defining a constant lvalue iterator, the user can pass a const-qualified version of the iterator's value_type as iterator_facade's Value parameter and omit the Reference parameter which follows." Am I to understand from this that iterator_facade<Derived,T const,Category> is equivalent to iterator_facade<Derived,T,Category,T const&>, and likewise for iterator_adaptor? D.

1 0

Re: [Boost-users] c array parameter in resize method of multi_array
by Manuel.Yguel＠inrialpes.fr 13 Jul '06

13 Jul '06

I think that any container that have the proper size would be ok. I would like to know too, if there are some compile flags that will prevent me to do: void outOfBound() { typedef boost::multi_array<double, 3> array_type; array_type A( boost::extents[3][4][2] ); A[12][3][43] = 8.0; printf( "Value: %f\n", A[12][3][43] ); } either at compile-time or at run time.

1 0

[lambda] ->* vs. bind
by Christian Rössel 13 Jul '06

13 Jul '06

Hello, assume I want to do a std::find_if on a container of A* with struct A { int foo; }; Now I have two ways of writing the predicate for find_if: 1. find_if (cont.begin (), cont.end (), _1 ->* &A::foo == 42); 2. find_if (cont.begin (), cont.end (), bind (&A::foo, _1) == 42); They both perform as expected. Are there any differences that make one of them preferrable? Thanks, Christian

1 0

__fastcall warning when compiling boost in managed c++
by ChuMing 13 Jul '06

13 Jul '06

Hi, I am handling some project which mixes managed and unmanaged C++ code. With boost 1.33 I’m hitting problems with the header is_mem_fun_pointer_tester.hpp. There are warnings popping up due to the use of __fastcall calling convertion in boost and its incompatible with compiling some of our code with the /clr flag turned on. Managed C++ is incompatible with the __fastcall calling convention because what it does is it preloads certain registers with the function parameters but for /clr compilation it is compiling to MSIL so this cannot be done and upon encountering any __fastcall the Managed C++ compiler will change it to __stdcall. Does anyone know the implications of disabling these warnings and whether it is safe to do that? I did not get these warnings with the previous versions of boost though. Thanks and regards, Chu-Ming

2 3

Regex build problem using g++ under cygwin
by Darren.Moore＠csiro.au 13 Jul '06

13 Jul '06

Hi, I've just started trying to use the Regex library with g++ 3.4.4 under cygwin. I am using the boost 1_33_1 libraries that are installed by cygwin's setup program. For some reason that I cannot figure out, building fails for this simple program test-regex.cpp : #include <boost/regex.hpp> using namespace boost; int main() { regex re; re.assign("hey"); } My build command is: g++ -I/usr/include/boost-1_33_1 -lboost_regex-gcc-mt-s test-regex.cpp Compilation is ok, but during linking I get: /cygdrive/d/temp/ccrjdFg7.o:test-regex.cpp:(.text$_ZN5boost11basic_regex IcNS_12regex_traitsIcNS_16cpp_regex_traitsIcEEEEE6assignEPKcS7_j[boost:: basic_regex<char, boost::regex_traits<char, boost::cpp_regex_traits<char> > >::assign(char const*, char const*, unsigned int)]+0x22): undefined reference to `boost::basic_regex<char, boost::regex_traits<char, boost::cpp_regex_traits<char> > >::do_assign(char const*, char const*, unsigned int)' collect2: ld returned 1 exit status I cannot figure out how to solve this problem, and would be grateful if anyone can offer any help. Thanks, Darren Moore.

4 3

[thread] TSS locking?
by Cory Nelson 13 Jul '06

13 Jul '06

Hello! The documentation doesn't seem to mention this. Does thread_specific_ptr have any guarantees about locking (mutex etc) when you call get() or reset()? I'd like to use it in a library but if locks I'll have to roll my own. Thanks! -- Cory Nelson http://www.int64.org

1 0

Seg faults when using boost::regex_replace in multiple threads
by mailinglist＠kamba.net.nz 12 Jul '06

12 Jul '06

Hello, I'm having a few problems with boost::regex_replace seg faulting when used in a multithreaded program. The problem seems to be identical to the one described in http://lists.boost.org/boost-users/2006/06/20235.php, with a seg fault on line 133 of regex_format.hpp, though I have linked against the multithreaded version of libboost_regex.so and the problem is still happening. Unfortunately, I never saw any definitive answer for what was causing the original poster's problems. =========================================== Stack trace: =========================================== Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -584664144 (LWP 28385)] 0x080520e0 in boost::re_detail::basic_regex_formatter<boost::re_detail::string_out_ite rator<std::string>, boost::match_results<char const*, std::allocator<boost::sub_match<char const*> > >, boost::regex_traits_wrapper<boost::regex_traits<char, boost::cpp_regex_traits<char> > > >::format_all (this=0xdd26b8d0) at regex_format.hpp:133 133 switch(*m_position) (gdb) where #0 0x080520e0 in boost::re_detail::basic_regex_formatter<boost::re_detail::string_out_ite rator<std::string>, boost::match_results<char const*, std::allocator<boost::sub_match<char const*> > >, boost::regex_traits_wrapper<boost::regex_traits<char, boost::cpp_regex_traits<char> > > >::format_all (this=0xdd26b8d0) at regex_format.hpp:133 #1 0x080518be in boost::re_detail::basic_regex_formatter<boost::re_detail::string_out_ite rator<std::string>, boost::match_results<char const*, std::allocator<boost::sub_match<char const*> > >, boost::regex_traits_wrapper<boost::regex_traits<char, boost::cpp_regex_traits<char> > > >::format (this=0xdd26b8d0, p1=0xd55005dc "$1", p2=0xd55005de "", f=format_all) at regex_format.hpp:123 #2 0x08051073 in boost::re_detail::regex_format_imp<boost::re_detail::string_out_iterator <std::string>, char const*, std::allocator<boost::sub_match<char const*> >, char, boost::regex_traits_wrapper<boost::regex_traits<char, boost::cpp_regex_traits<char> > > > (out= {<std::iterator<std::output_iterator_tag, char, int, char*, char&>> = {<No data fields>}, out = 0xdd26ba70}, m=@0xd5500518, p1=0xd55005dc "$1", p2=0xd55005de "", flags=format_all, t=@0x8064140) at regex_format.hpp:569 #3 0x08050710 in format<boost::re_detail::string_out_iterator<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >, boost::basic_regex<char, boost::regex_traits<char, boost::cpp_regex_traits<char> > > > (this=0xd5500518, out={<std::iterator<std::output_iterator_tag, char, int, char*, char&>> = {<No data fields>}, out = 0xdd26ba70}, fmt=@0xdd26b990, flags=format_all, re=@0x805f6ec) at match_results.hpp:170 #4 0x0804fe35 in boost::regex_replace<boost::re_detail::string_out_iterator<std::string>, char const*, boost::regex_traits<char, boost::cpp_regex_traits<char> >, char> (out= {<std::iterator<std::output_iterator_tag, char, int, char*, char&>> = {<No data fields>}, out = 0xdd26ba70}, first=0xd550048c "abcdefgh", last=0xd5500494 "", e=@0x805f6ec, fmt=0x805a2a9 "$1", flags=format_all) at regex_replace.hpp:53 #5 0x0804f7e1 in boost::regex_replace<boost::regex_traits<char, boost::cpp_regex_traits<char> >, char> (s=@0xdd26ba80, e=@0x805f6ec, fmt=0x805a2a9 "$1", flags=format_all) at regex_replace.hpp:84 #6 0x0804f3c4 in test_fn () at regexTest.C:32 #7 0xf63e5dec in start_thread () from /lib/tls/libpthread.so.0 #8 0xf6385a2a in clone () from /lib/tls/libc.so.6 (gdb) print *this $1 = {m_traits = @0x8064140, m_results = @0xd5500518, m_out = {<std::iterator<std::output_iterator_tag, char, int, char*, char&>> = {<No data fields>}, out = 0xdd26ba70}, m_position = 0xd44ff5d6 <Address 0xd44ff5d6 out of bounds>, m_end = 0xd55005de "", m_flags = format_all, m_state = output_copy, m_have_conditional = false} ========================================== GCC version is 3.2.3 20030502 (Red Hat Linux 3.2.3-42), with Boost 1.33.1, on a 4 CPU machine. We're using the STL from RogueWave, though since the post from a couple of weeks ago had the same problem with both GCC and STLport libraries I don't think that's the problem. This problem also occurs with version 1.33.0, but not with 1.32 or earlier. Does anyone know if there is a known problem with using these new versions of boost::regex_replace in multiple threads? If it's helpful, I have a very simple test program that demonstrates the problem. Any help on this would be greatly appreciated. Kind regards, Alistair Potts

3 2

serialization with hash_map problem
by Van Kincaid 12 Jul '06

12 Jul '06

Hi, I just started learning to use serialization and having problems with compiling for hash_map (map/deque/etc all work fine for me). I found your discussion a while ago relating to this http://thread.gmane.org/gmane.comp.lib.boost.user/12609/focus=12609 So I built my test program with g++ -D__GLIBCPP__ -DBOOST_HAS_HASH -DBOOST_STD_EXTENSION_NAMESPACE=__gnu_cxx -c test.cpp -o test.o And I still have the following compile errors saying that serialize function for hash_map is not defined. I also looked at the preprocessor output and did find the definition for hash_map serialize() function. It doesn't make sense to me why this happens. Any help is greatly appreciated. The test file is attached at the end. /usr/local/include/boost/serialization/access.hpp: In static member function 'static void boost::serialization::access::serialize(Archive&, T&, unsigned int) [with Archive = boost::archive::text_oarchive, T = __gnu_cxx::hash_map<int, boost::shared_ptr<DaoData>, __gnu_cxx::hash<int>, std::less<int>, std::allocator<boost::shared_ptr<DaoData> > >]': /usr/local/include/boost/serialization/serialization.hpp:81: instantiated from 'void boost::serialization::serialize(Archive&, T&, unsigned int) [with Archive = boost::archive::text_oarchive, T = __gnu_cxx::hash_map<int, boost::shared_ptr<DaoData>, __gnu_cxx::hash<int>, std::less<int>, std::allocator<boost::shared_ptr<DaoData> > >]' /usr/local/include/boost/serialization/serialization.hpp:140: instantiated from 'void boost::serialization::serialize_adl(Archive&, T&, unsigned int) [with Archive = boost::archive::text_oarchive, T = __gnu_cxx::hash_map<int, boost::shared_ptr<DaoData>, __gnu_cxx::hash<int>, std::less<int>, std::allocator<boost::shared_ptr<DaoData> > >]' /usr/local/include/boost/archive/detail/oserializer.hpp:148: instantiated from 'void boost::archive::detail::oserializer<Archive, T>::save_object_data(boost::archive::detail::basic_oarchive&, const void*) const [with Archive = boost::archive::text_oarchive, T = __gnu_cxx::hash_map<int, boost::shared_ptr<DaoData>, __gnu_cxx::hash<int>, std::less<int>, std::allocator<boost::shared_ptr<DaoData> > >]' test.cpp:157: instantiated from here /usr/local/include/boost/serialization/access.hpp:109: error: 'class __gnu_cxx::hash_map<int, boost::shared_ptr<DaoData>, __gnu_cxx::hash<int>, std::less<int>, std::allocator<boost::shared_ptr<DaoData> > >' has no member named 'serialize' ----------------------------------- test.cpp #include <fstream> #include <map> #include <iostream> #include <ext/hash_map> #include <boost/serialization/shared_ptr.hpp> #include <boost/serialization/map.hpp> #include <boost/serialization/hash_map.hpp> #include <boost/archive/text_oarchive.hpp> #include <boost/archive/text_iarchive.hpp> #include <boost/serialization/serialization.hpp> using namespace std; using namespace __gnu_cxx; using namespace boost; using namespace boost::serialization; template<typename DataType, typename KeyType, typename CompareType> class DAO { friend class serialization::access; public: typedef shared_ptr<DataType> DataTypePtr; typedef pair<KeyType, DataTypePtr> KeyDataPair; #if 0 typedef map<KeyType, DataTypePtr> DataTypeMap; #else typedef hash_map<KeyType, DataTypePtr, hash<KeyType>, CompareType> DataTypeMap; #endif typedef typename DataTypeMap::iterator DataTypeMapIter; typedef typename DataTypeMap::const_iterator DataTypeMapConstIter; DAO() {} ~DAO() {} template <class Archive> void serialize( Archive& ar, const unsigned int version ) { ar & m_dataTypeMap; } void insertData( DataTypePtr dataPtr ) { m_dataTypeMap.insert( KeyDataPair( dataPtr->getKey(), dataPtr ) ); } void display() const { DataTypeMapConstIter iter = m_dataTypeMap.begin(); while ( iter != m_dataTypeMap.end() ) { iter->second->display(); iter++; } } void save_binary( const char* filename ) { ofstream ofs(filename); archive::text_oarchive oa(ofs); oa & *this; } bool load_binary( const char* filename ) { try { ifstream ifs( "test.dat", ios::binary ); archive::text_iarchive ia( ifs ); ia & *this; display(); return true; } catch ( exception& e ) { cerr << "Exception caught: " << e.what() << endl; return false; } } private: DataTypeMap m_dataTypeMap; }; class DaoData { public: int m_key; string m_keyStr; DaoData() {} DaoData( int key, const string& keyStr ) : m_key( key ), m_keyStr( keyStr ) { } DaoData( DaoData& daoData ) { m_key = daoData.m_key; m_keyStr = daoData.m_keyStr; } ~DaoData() {} int getKey() const { return m_key; } void display() const { cout << "key = " << m_key << endl; cout << "keyStr = " << m_keyStr << endl; } template <class Archive> void serialize( Archive& ar, const unsigned int version ) { ar & m_key; ar & m_keyStr; } }; void test_dao_serialize() { DAO<DaoData, int, less<int> > myDao; shared_ptr<DaoData> dataPtr( new DaoData( 1, "ONE" ) ); myDao.insertData( dataPtr ); shared_ptr<DaoData> dataPtr2( new DaoData( 2, "TWO" ) ); myDao.insertData( dataPtr2 ); myDao.save_binary( "test.dat" ); //myDao.load_binary( "test.dat" ); } int main() { test_dao_serialize(); return 0; }

1 0

Re: [Boost-users] shared_ptr implicit dynamic cast
by Andrew Holden 12 Jul '06

12 Jul '06

Scott McMurray wrote > My apologies, I didn't know that. Certainly a very nice feature as it > means that even without the virtual destructor both would be safe. > > Promises to double-check the documentation before replying next time, No worries. It wasn't exactly a highly advertised feature. Besides, the note implied that older versions of shared pointer didn't do that, so I just figured you learned about shared pointers before they added it. Andrew

1 0