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

Boost.Random: Suspicious code in uniform_smallint_integer
by Daniel Krügler 26 Aug '05

26 Aug '05

Although uniform_smallint_integer currently is no official code (its in the details section and seems nowhere used), I would like to mention, that the current implementation contains a subtle bug: The member _factor is never initialized, thus calling operator()() would cause U.B. The reason is, that the initializer member function set defines a **local** variable _factor, which is never assigned to this->_factor, such that uniform_smallint_integer::_factor will never be assigned. Just one question: Is detail::uniform_smallint_integer a leftover of some experiments by the library responsible or does it exist for interested boost users to test it? Greetings from Bremen, Daniel

1 0

Re: [Boost-users] Boost serialization
by Li Lirong 26 Aug '05

26 Aug '05

You may try to serialize the data to a std::vector. See here for how to write a ostream with std::vector: http://www.boost.org/libs/iostreams/doc/tutorial/container_sink.html Regards, Lirong --- Srikanth Rao <srirao_us(a)yahoo.com> wrote: > Hi, > > I saw a mail from you to the group. I have a similar > issue but I need to send the serialized data on the > network. > > After serializing to a stream, can I get the buffer? > > How? > TIA, > Sri. > > > > __________________________________ > Yahoo! Mail for Mobile > Take Yahoo! Mail with you! Check email on your > mobile phone. > http://mobile.yahoo.com/learn/mail > __________________________________ Do you Yahoo!? Yahoo! Mail - Find what you need with new enhanced search. http://info.mail.yahoo.com/mail_250

1 0

Re: [Boost-users] Boost.Thread memory leak reported
by Sohail Somani 25 Aug '05

25 Aug '05

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Elisha Berns > Sent: Wednesday, August 24, 2005 8:48 PM > To: Boost > Subject: [Boost-users] Boost.Thread memory leak reported > > > > Detected memory leaks! > Dumping objects -> > {146} normal block at 0x00227008, 24 bytes long. > Data: < | > 08 7C 04 00 FF FF FF FF 00 00 00 00 00 00 00 > 00 > {145} normal block at 0x00223928, 8 bytes long. > Data: < p" > 08 70 22 00 01 CD CD CD > Object dump complete. Hi Elisha, Could you come up with a small test case that demonstrates the problem?

4 7

Re: [Boost-users] Boost.Thread memory leak reported
by Sohail Somani 25 Aug '05

25 Aug '05

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of > Christian Henning > Sent: Thursday, August 25, 2005 4:03 PM > To: boost-users(a)lists.boost.org > Subject: Re: [Boost-users] Boost.Thread memory leak reported > > > I'm just wondering why Purify doesn't show anything. (it sucks) Disclaimer: I only used it enough to make the above statement

1 0

[Test] redirecting unit test report
by Kim Barrett 25 Aug '05

25 Aug '05

I'm using the unit test framework provided by Boost.Test, mostly using the auto unit test facility. I wrote a parser for the XML formatted report output, as part of a regression package. Unfortunately, changes between 1.32 and 1.33 are causing a problem. The format of the XML output changed quite a bit between 1.32 and 1.33. Ok, I can deal with that; in fact, the new format is quite a bit easier to deal with, and I've already finished with the changes. It would be nice if this format were documented though. Unfortunately, there is one change that I haven't been able to figure out a good way to deal with. If a test case aborts, due to an exception uncaught by the test itself, the exception is caught by the unit test framework. The occurrence of the abort is recorded in the test results. In 1.32, this would be reported by including an <aborted ...> subentry for the test case data, including some descriptive text. In 1.33, the descriptive text is printed to std::cerr and the report indicates that the test case was aborted via the "result" value for the test case. The generated report no longer contains the descriptive text. (I don't care all that much about this last change.) The problem is the printing of the descriptive text for the exception to std::cerr. That is also the stream to which the test report is written, and I'm capturing the report information by redirecting stderr to a file when invoking a test program. The exception text ends up appearing at the beginning of the report file, and isn't valid XML, which causes my report parser to die. (If necessary, I may end up prefixing the parser with a step to skip over anything that doesn't look like XML, but that's pretty ugly.) Now, I never really liked redirecting stderr to a file in order to capture the report. What if something in the test program were to write to stderr? (Which is exactly what is happening now.) I see that there is now (in 1.33) a mechanism for setting the stream used by the report generator (boost:unit_test::results_reporter::set_stream()). But after spending the last couple of days pouring over the documentation and sources for Boost.Test, I have no idea where I would put a call to that function that doesn't involve patching the Boost.Test sources. There doesn't seem to be a place to insert such user code, at least not that I can find. Have I overlooked something, or is this really a hole in the present design / implementation?

3 13

Intermittent problem(s) building boost 1.33 with VC7.1
by Elisha Berns 25 Aug '05

25 Aug '05

The message "failed to write command file" comes up intermittently and seemingly at random when I build some or all of the 1.33 libraries. Once that message appears the build is killed and that's it. So far I have only been able to build the thread and iostreams libraries. What's the deal? Is it some problem with my machine, or with the build itself? Thanks, Elisha Berns e.berns(a)computer.org tel. (310) 556 - 8332 fax (310) 556 - 2839

2 1

Re: [Boost-users] Boost.Thread memory leak reported
by Sohail Somani 25 Aug '05

25 Aug '05

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of > Christian Henning > Sent: Thursday, August 25, 2005 10:53 AM > To: boost-users(a)lists.boost.org > Subject: Re: [Boost-users] Boost.Thread memory leak reported > > > On 8/25/05, Sohail Somani <s.somani(a)fincad.com> wrote: > > Valgrind doesn't find it either. I have yet to try it with stack > > walker (was about to but xp blue screened so I took it as a sign) > > > > Isn't valgrind for linux? I think the problem might be on > Windows machines, only. > > The functions new_critical_section() and > delete_critical_section() should be called only on Windows > machines, since they are calling Win32 functions. I didn't know it was a Windows only problem until you posted the location of the leaked allocation.

2 1

Re: [Boost-users] Boost.Thread memory leak reported
by Sohail Somani 25 Aug '05

25 Aug '05

Valgrind doesn't find it either. I have yet to try it with stack walker (was about to but xp blue screened so I took it as a sign) > -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Elisha Berns > Sent: Thursday, August 25, 2005 9:45 AM > To: boost-users(a)lists.boost.org > Subject: Re: [Boost-users] Boost.Thread memory leak reported > > > Right, > > Those are the same project settings I'm using. The only > difference is that my code is in a non-MFC class. I tested > it with the VLD memory leak detector found on CodeProject and > it also reports zero leaks. > > Elisha > > > I got exactly the same error. Here is how I did it: > > > > I created a project of a MFC Application inside VC7.1 . The wizards > > creates the usual document/view classes. Inside the > document class I > > placed, like Elisha, a mutex. Inside the OnNewDocument() function I > > put the code from Elisha: > > > > BOOL CMFCTestDoc::OnNewDocument() > > { > > if (!CDocument::OnNewDocument()) > > return FALSE; > > > > // TODO: add reinitialization code here > > // (SDI documents will reuse this document) > > > > boost::thread indexer( > > boost::bind(&CMFCTestDoc::run, this)); > > > > boost::mutex::scoped_lock lock(m_orphan_annotation_mutex); > > > > indexer.join(); > > > > > > return TRUE; > > } > > > > I'm using MFC in a Shared DLL and Multithreaded Debug DLL runtime > libs. > > > > I can send the project files to anyone that is interessted. > > > > By the way, if I use Purify to track down the leaks, it cannot find > them. > > > > Regards, > > Christian > > > > > > > > > > On 8/25/05, Sohail Somani <s.somani(a)fincad.com> wrote: > > > > -----Original Message----- > > > > From: boost-users-bounces(a)lists.boost.org > > > > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Elisha > Berns > > > > Sent: Wednesday, August 24, 2005 8:48 PM > > > > To: Boost > > > > Subject: [Boost-users] Boost.Thread memory leak reported > > > > > > > > > > > > > > > > Detected memory leaks! > > > > Dumping objects -> > > > > {146} normal block at 0x00227008, 24 bytes long. > > > > Data: < | > 08 7C 04 00 FF FF FF FF 00 00 00 00 00 > 00 00 > > > > 00 > > > > {145} normal block at 0x00223928, 8 bytes long. > > > > Data: < p" > 08 70 22 00 01 CD CD CD > > > > Object dump complete. > > > > > > Hi Elisha, > > > > > > Could you come up with a small test case that demonstrates the > problem? > > > > > > > > > _______________________________________________ > > > Boost-users mailing list > > > Boost-users(a)lists.boost.org > > > http://lists.boost.org/mailman/listinfo.cgi/boost-users > > > > > > > _______________________________________________ > > Boost-users mailing list > > Boost-users(a)lists.boost.org > > http://lists.boost.org/mailman/listinfo.cgi/boost-users > > > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > http://lists.boost.org/mailman/listinfo.cgi/boost-users >

2 1

[filesystem] Mingw DLL problems
by Paul 25 Aug '05

25 Aug '05

Hi all, It seems that theres a lot of traffic in regards to using filesystem as a DLL with mingw (or other) compilers. I'd like to lay out what I know and try and figure out a solution for it. Or at least ask for a work-around to be added to the CVS, or to the documentation! Often I see complaints that it will fail to work as expected! This is because the 'native' "flag" passed to path will be virtually IGNORED when you link to it as a DLL. Why? Because native is not a flag, its a free function pointer. Inside the filesystem DLL, it compares the address of the passed checker against its version of 'native', however: the address of 'native' is DIFFERENT in the DLL compared with any other DLL or your executable! So native(you) != native(DLL), so paths will be checked the POSIX way, not the native way. I've heard suggestions that you should define BOOST_ALL_DYN_LINK, however that doesn't seem to do anything in my case. I've tested it. I am betting that most people 'solve' it by statically linking to it, but thats not an option for me. The only solution I have come up with is to add a function to get the DLL's native function address. Instead of passing 'native', I now pass get_native(). This just does return native; but it does it inside the DLL, so you get the "right" function address. Beman said that it should be fixed in the next version of filesystem, however it appears to be Not Hear Yet. So can we please please get an interim fix? Attached was my attempt from back in January, it worked for me, and I'll be applying it to my shiny new 1.33 version. Thanks Paul

1 0

Boost.Thread memory leak reported
by Elisha Berns 25 Aug '05

25 Aug '05

HI, There is a small memory leak reported by VC7.1 just by declaring a boost::mutex (presumably). Since this makes no sense at all, perhaps there is some explanation for this behavior in this compiler. The code looks like this: In the class definition: mutable boost::mutex m_orphan_annotation_mutex; (It's only declared mutable because it's used in 'const' methods also). In the .cpp file: void OrphanedAnnotationMap::IndexOrphanedAnnotations() { boost::thread indexer( boost::bind(&OrphanedAnnotationMap::Index, this)); boost::mutex::scoped_lock lock(m_orphan_annotation_mutex); indexer.join(); } The memory dump is this: Detected memory leaks! Dumping objects -> {146} normal block at 0x00227008, 24 bytes long. Data: < | > 08 7C 04 00 FF FF FF FF 00 00 00 00 00 00 00 00 {145} normal block at 0x00223928, 8 bytes long. Data: < p" > 08 70 22 00 01 CD CD CD Object dump complete. Elisha Berns e.berns(a)computer.org tel. (310) 556 - 8332 fax (310) 556 - 2839

1 0

Trouble using format.hpp on AIX
by Rich Cook 25 Aug '05

25 Aug '05

Hi, Newbie question. I have used Boost for little things and it has worked fine. Now I'd like to use the format.hpp header, but including it on AIX in my project results in the following errors. Does anyone have an idea what is happening? I googled all over the place but found no help on the subject: xlC -c -g -I/g/g0/rcook/aix_5_64_fed/include -I/g/g0/rcook/ downloads/boost_1_33_0 MirandaReader.C -o aix_5_64_fed/MirandaReader.o "/g/g0/rcook/downloads/boost_1_33_0/boost/optional/optional.hpp", line 388.66: 1540-0217 (S) "T" is not a member of "locale". "/g/g0/rcook/downloads/boost_1_33_0/boost/optional/optional.hpp", line 388.10: 1540-0700 (I) The previous message was produced while processing "boost::optional_detail::optional_base<std::locale>::destroy_impl (is_not_reference_tag)". "/g/g0/rcook/downloads/boost_1_33_0/boost/optional/optional.hpp", line 362.9: 1540-0700 (I) The previous message was produced while processing "boost::optional_detail::optional_base<std::locale>::destroy()". "/g/g0/rcook/downloads/boost_1_33_0/boost/optional/optional.hpp", line 208.24: 1540-0700 (I) The previous message was produced while processing "boost::optional_detail::optional_base<std::locale>::~optional_base()". "/g/g0/rcook/downloads/boost_1_33_0/boost/optional/optional.hpp", line 130.7: 1540-0700 (I) The previous message was produced while processing "boost::optional_detail::optional_base<std::locale>::__dftbdt()". "/g/g0/rcook/downloads/boost_1_33_0/boost/optional/optional.hpp", line 471.5: 1540-0700 (I) The previous message was produced while processing "boost::optional<std::locale>::~optional()". "/g/g0/rcook/downloads/boost_1_33_0/boost/format/internals.hpp", line 38.9: 1540-0700 (I) The previous message was produced while processing "boost::io::detail::stream_format_state<char,std::char_traits<char> >::stream_format_state(char)". "/g/g0/rcook/downloads/boost_1_33_0/boost/format/internals.hpp", line 78.53: 1540-0700 (I) The previous message was produced while processing "boost::io::detail::format_item<char,std::char_traits<char>,std::allocat or<char> >::format_item(char)". "/g/g0/rcook/downloads/boost_1_33_0/boost/format/ format_implementation.hpp", line 121.40: 1540-0700 (I) The previous message was produced while processing "boost::basic_format<char,std::char_traits<char>,std::allocator<char> >::make_or_reuse_data(size_t)". "/g/g0/rcook/downloads/boost_1_33_0/boost/format/parsing.hpp", line 415.9: 1540-0700 (I) The previous message was produced while processing "boost::basic_format<char,std::char_traits<char>,std::allocator<char> >::parse(const string_type &)". "/g/g0/rcook/downloads/boost_1_33_0/boost/format/ format_implementation.hpp", line 64.9: 1540-0700 (I) The previous message was produced while processing "boost::basic_format<char,std::char_traits<char>,std::allocator<char> >::basic_format(const string_type &)". "MirandaReader.C", line 138.6: 1540-0700 (I) The previous message was produced while processing "MirandaDataSet::GetGridOrigin(long, Point<double> &)". gmake: *** [aix_5_64_fed/MirandaReader.o] Error 1 -- Richard Cook ✇ Lawrence Livermore National Laboratory Bldg-453 Rm-4037, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ☎ (925) 423-9605  (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL)

1 0

[ptr_container]copy from one to other with iterator
by Thomas Matelich 24 Aug '05

24 Aug '05

I'm looking at ptr_vector to replace our wrapper around vector<shared_ptr>. How do I correctly write the following: ptr_vector<T> a; ptr_vector<T> b; ... b.push_back(a.begin()); I've tried plain iterators, dereferencing, *iter.base(), etc. I guess I could reinterpret_cast<T*>(*iter.base()). Is there a better way? Also, theres a typo in the docs. The examples page talks about using allocate_clone, and I'm pretty sure its supposed to be new_clone (If not, theres a typo in the tutorial). Thanks, Tom

3 8

Re: [Boost-users] [BULK] Re: [BULK] Re: [BULK] Re: [Test] Asserting a failure
by Sohail Somani 24 Aug '05

24 Aug '05

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of > Gennadiy Rozental > Sent: Wednesday, August 24, 2005 12:15 PM > To: boost-users(a)lists.boost.org > Subject: [BULK] Re: [Boost-users] [BULK] Re: [BULK] Re: > [Test] Asserting a failure > Importance: Low > > > > On second thought, why not just modify BOOST_REQUIRE? > > What do you propose to modify? > > One could use BOOST_REQUIRE *instead* of assert() or > BOOST_ASSERT. But if > they prefer keep using BOOST_ASSERT I could provide a handler. Well theres no problem using BOOST_ASSERT unless they use it in their code for different reasons. For example they might use it to log in production versions of the application... I guess its not such a big deal if boost test defines its own handler if enable assert handler is not defined. I don't even remember where this thread started :)

1 0

Re: [Boost-users] [BULK] Re: [BULK] Re: [Test] Asserting a failure
by Sohail Somani 24 Aug '05

24 Aug '05

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of > Sohail Somani > Hmm. That's an idea. I could probably do this within > > Boost.Test so users > > wouldn't need to bother: > > > > test_tools.hpp: > > > > #if !defined(BOOST_TEST_NO_ASSERT_HANDLER) > > > > namespace boost { > > inline void assertion_failed(char const * expr, char const * > > function, char > > const * file, long line) > > { > > ... > > } > > } > > > > #endif > > > > This way by default I will always supply definition for the > > function, unless > > user is willing to suply different one. > > I imagine that would work unless they already use boost > assert and define it in their own code for logging purposes. > Perhaps something along the lines of boost assert for boost test? On second thought, why not just modify BOOST_REQUIRE?

2 1

Re: [Boost-users] [BULK] Re: [BULK] Re: [Test] Asserting a failure
by Sohail Somani 24 Aug '05

24 Aug '05

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of > Gennadiy Rozental > Sent: Wednesday, August 24, 2005 11:50 AM > To: boost-users(a)lists.boost.org > Subject: [BULK] Re: [Boost-users] [BULK] Re: [Test] Asserting > a failure > Importance: Low > > > > > Try replacing your asserts with BOOST_ASSERT which can be a passive > > assert depending on how you use it. > > > > http://www.boost.org/libs/utility/assert.html > > Hmm. That's an idea. I could probably do this within > Boost.Test so users > wouldn't need to bother: > > test_tools.hpp: > > #if !defined(BOOST_TEST_NO_ASSERT_HANDLER) > > namespace boost { > inline void assertion_failed(char const * expr, char const * > function, char > const * file, long line) > { > ... > } > } > > #endif > > This way by default I will always supply definition for the > function, unless > user is willing to suply different one. I imagine that would work unless they already use boost assert and define it in their own code for logging purposes. Perhaps something along the lines of boost assert for boost test?

1 0

Re: [Boost-users] [BULK] Re: [Test] Asserting a failure
by Sohail Somani 24 Aug '05

24 Aug '05

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of > Gennadiy Rozental > Sent: Wednesday, August 24, 2005 9:51 AM > To: boost-users(a)lists.boost.org > Subject: [BULK] Re: [Boost-users] [Test] Asserting a failure > Importance: Low > > > > cannot find one. All I see are macros that assert > successes, and those > > that > > assert exceptions. But my particular function does not > throw, it simply > > "assert()"s. > > I do not know reliable/portable way to intercept an assert > invocation. So > you are on your own here. If you know any hooks to do the > job, I am open to > suggestions. Try replacing your asserts with BOOST_ASSERT which can be a passive assert depending on how you use it. http://www.boost.org/libs/utility/assert.html

2 1

Re: [Boost-users] [1.33][ptr_container] bug in erase() in associative containers?
by JOAQUIN LOPEZ MU?Z 24 Aug '05

24 Aug '05

----- Mensaje original ----- De: Thorsten Ottosen <nesotto(a)cs.aau.dk> Fecha: Miércoles, Agosto 24, 2005 6:05 pm Asunto: Re: [Boost-users] [1.33][ptr_container] bug inerase() inassociativecontainers? > > "JOAQUIN LOPEZ MU?Z" <joaquin(a)tid.es> wrote in message > news:1553a314f2df.14f2df1553a3@tid.es... > > > size_type erase( const key_type& x ) // nothrow > > > { > > > BOOST_ASSERT( !this->empty() ); > > Why the BOOST_ASSERT? Do you require that the container > be non-empty for erase to be callable? Am I missing something? > > >>>>>> > > Hm...I couldn't find anything on this in the standard. Can you > locate the > description for map<K,V>::erase( const K&) ? > In 23.1.2 [lib.associative.reqmts], the table has an entry for the expression "a.erase(k)" saying: "erases all the elements in the container with key equivalent to k. returns the number of erased elements." No precondition is stated that "a" should be nonempty, neither in the table itself nor in the general requisites for the table (23.1.2/7), hence "a" is allowed to be empty. I've taken a closer look at your code and think there are some more of these overzealous asserts: * The following in associative_ptr_container.hpp iterator erase( iterator first, iterator last ) // nothrow { BOOST_ASSERT( !this->empty() ); requires again that the container be nonempty. There's no such precondition in the std for the expression "a.erase(q1,q2)": the only requisite in 23.1.2/7 is that [q1, q2) be a valid range, which is compatible with "a" being empty if q1==q2==a.end() (see 24.1/7, see also DR151 which addresses an issue with the original erroneous requirement that q1 be dereferenceable). * Same problem as above in reversible_ptr_container.hpp. HTH, Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

2 1

Re: [Boost-users] [bjam] [v1] How to copy the generated binaries from a dependent project?
by Ames Andreas 24 Aug '05

24 Aug '05

Hi, many thanks for your help. Rene Rivera wrote: > Hm, for 1.33 I see a "stage" target in the signals/build/Jamfile. You are right. What doesn't fit my use case is that, at least I believe so, I can't specify the destination directory there. It always copies the binaries to toplevel/stage/lib. My statement was misleading here, sorry. > Similarly for BBv1 it's: > > stage my_stage > : <dll>@boost/libs/signals/build/boost_signals > <lib>@boost/libs/signals/build/boost_signals > ; > > It requires that you add definition of "boost" to your Jamrules file: > > project boost : _path_to_boost_ ; Aah, that's exactly what I needed to get started. With a bit of additional boilerplate it does what I want. cheers, aa -- Andreas Ames | Programmer | Comergo GmbH | Voice: +49 69 7505 3213 | andreas . ames AT comergo . com

1 0

[Test] Asserting a failure
by Mike 24 Aug '05

24 Aug '05

Hi. Is there a way inside a test case using the Unit Testing Framework to specify that a particular function call ought to fail? For example, I have a function that asserts when passed invalid input. In my test case I want to pass it an invalid parameter and check that the assert is triggered. I'm looking for a macro called BOOST_CHECK_FAILURE (or something like that), but cannot find one. All I see are macros that assert successes, and those that assert exceptions. But my particular function does not throw, it simply "assert()"s. Any ideas? Thanks, Mike

2 1

Re: [Boost-users] [bjam] [v1] How to copy the generated binaries from a dependent project?
by Ames Andreas 24 Aug '05

24 Aug '05

Hi, Vladimir Prus wrote: > I know your message talks about V1, but with V2 this is a simple as: > > install install-boost-libs-you-want > : <path-to-boost>/libs/signals/build//boost_signals > : <location>some-directory > ; > > for multiple variants: > > install install-boost-libs-you-want > : <path-to-boost>/libs/signals/build//boost_signals/<variant>release > <path-to-boost>/libs/signals/build//boost_signals/<variant>debug > : <location>some-directory > ; Thanks for the hint. I have tried it out with the Boost.Buildv2 that ships with 1.33.0 but unfortunately there were some problems: 1) examples/echo doesn't build at all 2) boost toplevel doesn't build because of an issue in iostreams 3) boost/libs/signals builds only a single subvariant and I couldn't figure out how to build all the others 4) contrary to v1 when I build in a subproject (like signals) v2 seems to always complain about missing python, ICU etc. Unless these are grave failures on my part (I've followed the documentation on boost.org which seems to be a bit outdated) I will presumably stay with v1 and more so because Rene Rivera provided me the clue I needed to get going. cheers, aa -- Andreas Ames | Programmer | Comergo GmbH | Voice: +49 69 7505 3213 | andreas . ames AT comergo . com

1 0

[1.33][ptr_container] bug in erase() in associative containers?
by Malte Clasen 24 Aug '05

24 Aug '05

Hi, the erase() method (defined in associative_ptr_container.hpp, line 104) seems a bit strange: size_type erase( const key_type& x ) // nothrow { BOOST_ASSERT( !this->empty() ); iterator i = find( x ); // nothrow if( i == this->end() ) // nothrow return 0; // nothrow this->remove( i ); // nothrow return this->c_private().erase( i.base() ); // nothrow } http://cvs.sourceforge.net/viewcvs.py/boost/boost/boost/ptr_container/detai… My compiler (vc++7.1) complained about the unknown find() when I called erase() on ptr_map. "find" is not declared neither in this class nor in its base class. The closest valid call I could think of would be this->c_private().find( x ) . But there seems to be a nicer solution: size_type erase( const key_type& x ) // nothrow { BOOST_ASSERT( !this->empty() ); return this->c_private().erase( x ); // nothrow } This compiles fine and does just what I want it to do, even nothrow is guaranteed (I checked the vc++ reference for std::map). Now I wonder why erase() is implemented differently in Boost 1.33. Is there anything I overlooked? Btw, is there a rationale for the declaration of insert()? std::pair<iterator,bool> insert( key_type& k, value_type x ); http://cvs.sourceforge.net/viewcvs.py/boost/boost/boost/ptr_container/ptr_m… Passing key_type by non-const reference caused some unaesthetic constructs in my code because return values (temporaries) cannot be used directly. Malte

2 2

Re: [Boost-users] [1.33][ptr_container] bug in erase() inassociativecontainers?
by JOAQUIN LOPEZ MU?Z 24 Aug '05

24 Aug '05

----- Mensaje original ----- De: Thorsten Ottosen <nesotto(a)cs.aau.dk> Fecha: Martes, Agosto 23, 2005 11:22 pm Asunto: Re: [Boost-users] [1.33][ptr_container] bug in erase() inassociativecontainers? [...] > > > > size_type erase( const key_type& x ) // nothrow > > { > > BOOST_ASSERT( !this->empty() ); > > iterator i = find( x ); // nothrow > > if( i == this->end() ) // nothrow > > return 0; // nothrow > > this->remove( i ); // nothrow > > return this->c_private().erase( i.base() ); // nothrow > > } Why the BOOST_ASSERT? Do you require that the container be non-empty for erase to be callable? Am I missing something? Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

2 1

program_options range checking?
by Fredrik Hedman 24 Aug '05

24 Aug '05

Hello, I would like to be able to specify different sanity checks on the input data using the program_options framework. This should be a common enough requirement, but I can not find any example that exactly fits the bill. To be more specific I have a solution that kind of works, but I think it needs a bit to much typing. Here is what I have now: /*! Check for values greater than min. */ template <typename T> class value_gt { public: value_gt(std::string const & msg, T min) : msg_(msg), min_(min) {} void operator()(T const & v) const { if (v > min_) return; ostringstream os; os << msg_ << " to small. Must be larger than " << min_ << " . Found " << v; throw pgmopt::invalid_option_value(os.str()); } private: std::string msg_; T min_; }; void doSetProgram(Options & options) { options.add_options() ("help,h", "show this message") ("density", pgmopt::value<double>()->notifier( value_gt<double>("density", 1.0)), "initial density") ("particles", pgmopt::value<unsigned>()->notifier( value_gt<unsigned>("particles", 100)), "number of particles") ; } I don't like repeating the type (see code above) and would rather like to have access to the name of the option in the function that does the check. What would be a better solution? Adding to the validators idea or? -- F.

2 2

[bjam] [v1] How to copy the generated binaries from a dependent project?
by Ames Andreas 24 Aug '05

24 Aug '05

Hi, I'm using some of boost's libs in my own projects. Therefore I like to build certain (sub)variants of these libraries from the according library subdirectories to avoid the (quite large) overhead when building from the toplevel boost directory with the --with-<lib> option. Take Boost.Signals as an example. When I build in boost/libs/signals/build using bjam, the subproject (not only signals) seems not to support the stage target so that the resulting binary/ies are build somewhere in boost/bin. Now I would like to create a Jamfile outside the boost source tree which does two things: 1) it builds selected (sub)variants of boost_signals, perhaps using some accordingly named NOTFILE targets, 2) it let's me copy the resulting binary/ies (i.e. libs and dlls) to a specified directory. Unfortunately I seem not to be able to figure out how to do this with bjam, especially how to get the full path of the built binary/ies. I would really like to avoid hardcoding these paths. So any help is appreciated. TIA, aa -- Andreas Ames | Programmer | Comergo GmbH | Voice: +49 69 7505 3213 | andreas . ames AT comergo . com

3 2

[bjam] [v1] Minor issue with vc-7_1
by Ames Andreas 24 Aug '05

24 Aug '05

Hi, when I use bjam -sTOOLS=vc-7_1 "-sBUILD=debug <debug-store>database" lib I get LNK4044 linker warning because the /PDB command line switch is not supported (but ignored) for archive targets. I suppose the vc-Archive action in msvc-tools.jam shouldn't use PDB_LINKFLAG because I can't see why it should be needed. cheers, aa -- Andreas Ames | Programmer | Comergo GmbH | Voice: +49 69 7505 3213 | andreas . ames AT comergo . com

1 0

Re: [Boost-users] regex_replace with file streams
by louis 24 Aug '05

24 Aug '05

Thanks for the help. My platform is Win32 and I was able to create a class: class mystring: public std::iterator<std::bidirectional_iterator_tag, char > mystring class opens the input file and maps it into memory using: CreateFileMapping MapViewOfFile and I pass this into regex_replace. It seems to work - any thoughts? Thanks again Louis > -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of John Maddock > Sent: Tuesday, August 23, 2005 11:08 AM > To: boost-users(a)lists.boost.org > Subject: Re: [Boost-users] regex_replace with file streams > >>I want to use regex_replace to operate on a potentially large input >>file and output the results to another file. So, I can't load the >>entire file into a buffer in memory and pass it in as is done in the >>examples. I can't seem to figure out how to pass fstream or some other >>file I/O into regex_replace (ie create the proper iterator). > > Take a look at the second example in > http://www.boost.org/libs/regex/doc/partial_matches.html > > Unfortunately if you want to do a search and replace in an "infinite" text, > then you're not going to be able to use regex_replace. Instead you'll have > to enumerate through the matches and copy unmatched sections to output, and > then call match_results::format on matched sections to get the text to > output for that section. > > HTH, John. > > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > http://lists.boost.org/mailman/listinfo.cgi/boost-users >

2 1

program_options and lib64
by Philippe Després 24 Aug '05

24 Aug '05

Hello, I am using linux gcc 4.01, boost-1.33 on an amd 64 machine. I use program_options to retrieve a string from a config file but get a crash like this when I notify(): Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 46912541228512 (LWP 12633)] 0x00002aaaab14d2eb in std::string::assign () from /usr/lib64/libstdc++.so.6 (gdb) bt #0 0x00002aaaab14d2eb in std::string::assign () from /usr/lib64/libstdc++.so.6 #1 0x0000000000427689 in boost::program_options::typed_value<std::string, char>::notify (this=0x5de300, value_store=@0x5e1a48) at value_semantic.hpp:32 #2 0x00002aaaaafa50c9 in boost::program_options::notify () from /usr/local/lib/libboost_program_options-gcc-1_33.so.1.33.0 Is there known uncompatibilities between boost/gcc4/lib64 ?? Thank you, -- Philippe Després Associate Specialist UCSF Physics Research Lab 185 Berry Street suite 350 San Francisco CA 94107 (415) 353-4501 PGP PUBLIC KEY http://itsa.ucsf.edu/~despres/publickey.txt

3 2

Re: [Boost-users] [BULK] Re: [BULK] Re: [Test] redirecting unit test report
by Sohail Somani 23 Aug '05

23 Aug '05

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of > Gennadiy Rozental > Sent: Tuesday, August 23, 2005 1:40 PM > To: boost-users(a)lists.boost.org > Subject: [BULK] Re: [Boost-users] [BULK] Re: [Test] > redirecting unit test report > Importance: Low > > Because instances of global_fixure aren't supposed to be > destructed through > abstract pointer. Which is reinforced by protected destructor. Ah. I had a suspicion of this. > > All this could be avoided if you go the route of > BOOST_ASSERT in that > > you can define hooks via some free standing functions. > > What could be avoided and how an alternative would look like? I was thinking of avoiding the need for classes. But since context was snipped I went back and read over the thread again and it seems that you need classes.

1 0

Re: [Boost-users] [BULK] Re: [Test] redirecting unit test report
by Sohail Somani 23 Aug '05

23 Aug '05

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of > Gennadiy Rozental > Sent: Monday, August 22, 2005 10:26 PM > To: boost-users(a)lists.boost.org > Subject: [BULK] Re: [Boost-users] [Test] redirecting unit test report > Importance: Low > > #include <iostream> > > class global_fixure { > public: > global_fixure() { pointer() = this; } > virtual void setup() = 0; > virtual void teardown() = 0; > > static global_fixure*& pointer() { static global_fixure* > p = 0; return > p; } > > protected: > ~global_fixure() {} > }; Why isnt the destructor virtual? Is it because you will never have an instance of this class? What happens if delete a_global_fixture; is called? [snipped some stuff] All this could be avoided if you go the route of BOOST_ASSERT in that you can define hooks via some free standing functions.

2 1

Another iostreams question
by Lisa Glendenning 23 Aug '05

23 Aug '05

Is it possible to do something like template <typename T> T* Access(int n) { return chain.component<n, T>(); } because my compiler (GCC) doesn't like it. And if not, then how can I access a component without knowing at compile time its index?

3 2

regex_replace with file streams
by louis 23 Aug '05

23 Aug '05

Hi, I am new to the boost library, STL and template programming.. I want to use regex_replace to operate on a potentially large input file and output the results to another file. So, I can't load the entire file into a buffer in memory and pass it in as is done in the examples. I can't seem to figure out how to pass fstream or some other file I/O into regex_replace (ie create the proper iterator). Any help would be greatly appreciated. Louis

2 1

[SPIRIT] Problem with actors
by Stephen Henry 23 Aug '05

23 Aug '05

Hi all, I am having a problem with the following snippet of code. What I want to do is parse a line of alpha numeric characters from a file_iterator and then use the read characters to construct a new object which takes a std::string and integer argument for it's constructor. To do this I am using the statement below: p >> (+alpha_p)[ create_dfa( self.m_dfa, construct_<DFA>( construct_<std::string>( arg1 ), var(500) ) ) ]; This is the code I've got: #include <vector> #include <iostream> #include <boost/spirit/core.hpp> #include <boost/spirit/iterator/file_iterator.hpp> #include <boost/spirit/attribute.hpp> #include <boost/spirit/utility/confix.hpp> #include <boost/spirit/actor.hpp> #include <boost/spirit/phoenix.hpp> using namespace boost::spirit; using namespace phoenix; struct DFA { DFA( std::string s, int i ) : m_name(s), m_i(i) {} std::string m_name; int m_i; }; struct create_dfa_impl { template<typename Container, typename Item> struct result { typedef void type; }; template<typename Container, typename Item> void operator()( Container& c, Item const& item ) const { c.push_back( item ); } }; function<create_dfa_impl> const create_dfa = create_dfa_impl(); struct Script_parser : public grammar<Script_parser> { Script_parser( std::vector<DFA> &dfa ) : m_dfa( dfa ) {} template<typename ScannerT> struct definition { definition( Script_parser const& self ) { p = (*alpha_p)[ create_dfa( self.m_dfa, construct_<DFA>( construct_<std::string>(arg1, arg2), 500 ) ) ]; } typedef rule<ScannerT> rule_t; rule_t p; rule_t const& start() const { return p; } }; std::vector<DFA> &m_dfa; }; typedef char char_t; typedef file_iterator<char_t> iterator_t; int main( int argc, char *argv[] ) { using namespace std; if( argc != 2 ) { cout << "Invalid arguments" << endl; return -1; } iterator_t first( argv[1] ); iterator_t last = first.make_end(); std::vector<DFA> vDFA; Script_parser p(vDFA); parser_info<iterator_t> info = parse( first, last, p ); if( info.hit ) { cout << "Parsing successfull" << endl; } } This doesn't even compile, and I have absolutely no idea why. All the compiler shows is pages and pages of garbage that means absolutely nothing. Please help! Stephen

2 1

Failing date_time "default classic" tests
by Steven Solie 23 Aug '05

23 Aug '05

I'm getting the following output from one of the date_time tests with Boost 1.33.0 on AmigaOS: execute-test ../../../bin/boost/libs/date_time/test/testdate_facet_new.test/gcc/debug/testdate_facet_new.run ====== BEGIN OUTPUT ====== Pass :: to_string & default formats match Pass :: to_string & default formats match FAIL :: default classic date FAIL :: default classic date period Pass :: custom date facet date period ... I've traced it down to the %x date format specifier using the default locale while the tests themselves expect something else. According to the ANSI K&R C book this is correct behaviour because C++ classic locale uses the same format specifiers as the ANSI C strftime() function. So am I correct in assuming these two test cases are broken? --Steven

2 1

[program_options] seg fault on ppc64 / linux / gcc 3.4.4
by Liam Routt 23 Aug '05

23 Aug '05

I've just moved our project across to Boost 1.33, which seems to be working fine on our x86 linux gcc 3.4.4 machine. However, I'm getting seg faults on really basic stuff on the mac G5 we have, running linux with gcc 3.4.4 (Gentoo, using ppc64 kernel and userspace). This machine had no problems under Boost 1.32, I should add. Here is a simple test program (based on one of the early examples): ========= #include <boost/program_options.hpp> namespace po = boost::program_options; int main ( int, char* ) { po::options_description generic("Generic options"); generic.add_options() ("version,v", "print version string"); generic.add_options() ("help", "produce help message"); return ( 0 ); } ========= The seg fault happens on the second add_options() line. If the two lines are combined (as in the original example) it faults somewhere in there, but I think it is the same place. My gdb session: ========= GNU gdb 6.3 Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "powerpc64-unknown-linux-gnu"...Using host libthread_db library "/lib/libthread_db.so.1". Core was generated by `a.out '. Program terminated with signal 11, Segmentation fault. Reading symbols from /usr/lib/libboost_program_options.so.1.33.0...done. Loaded symbols for /usr/lib/libboost_program_options.so.1.33.0 Reading symbols from /lib/libc.so.6...done. Loaded symbols for /lib/libc.so.6 Reading symbols from /usr/lib/gcc-lib/powerpc64-unknown-linux-gnu/3.4.4/libstdc++.so.6...done. Loaded symbols for /usr/lib/gcc/powerpc64-unknown-linux-gnu/3.4.4/libstdc++.so.6 Reading symbols from /lib/ld64.so.1...done. Loaded symbols for /lib64/ld64.so.1 Reading symbols from /lib/libm.so.6...done. Loaded symbols for /lib/libm.so.6 Reading symbols from /usr/lib/gcc-lib/powerpc64-unknown-linux-gnu/3.4.4/libgcc_s.so.1...done. Loaded symbols for /usr/lib/gcc/powerpc64-unknown-linux-gnu/3.4.4/libgcc_s.so.1 #0 0x000000800005d7a8 in ._ZN5boost6detail17sp_counted_impl_pINS_15program_options18option_descriptionEE7disposeEv () from /usr/lib/libboost_program_options.so.1.33.0 (gdb) up #1 0x0000008000057b90 in ._ZN5boost15program_options29options_description_easy_initclEPKcS3_ () from /usr/lib/libboost_program_options.so.1.33.0 (gdb) up #2 0x0000000010001930 in main () at my1.cc:14 14 generic.add_options() ("help", "produce help message"); (gdb) up #3 0x00000080000d8fa4 in .__libc_start_main () from /lib/libc.so.6 ========= Any advice or suggestions are welcome. We're installing boost 1.33 in our 32-bit ppc chroot environment, and will see if there is any difference there, in case that helps. Also it is worth noting that we have a program that doesn't use the program_options, but does use boost filesystem, and that seems to run fine. Take care, Liam -- Liam Routt Ph: (03) 8344-1315 Research Programmer caligari(a)cs.mu.oz.au Computer Science, Melbourne University (or liam(a)routt.net)

5 9

Minor glitch in ptr_array?
by Daniel Krügler 23 Aug '05

23 Aug '05

I think that there is a typo in the 2nd c'tor of ptr_container_detail::ptr_array_impl<>: Shouldn't it say this->assign( 0 ); instead of the currently written this->assing( 0 ); ?? Greetings from Bremen, Daniel Krügler

2 2

A proposal to make float_hash_value<> more portable
by Daniel Krügler 23 Aug '05

23 Aug '05

Hello, the current implementation function for hashing of floating point types, the function template float_hash_value<> in hash.hpp, is implicitely written for real types where std::numeric_limits<T>::radix == 2. Although base = 2 is probably the most prominent case, it is not the only representation compatible with Our Holy Standard. E.g. base 16 floating types are well-known to exist. The hidden assumption becomes obvious in the formular std::size_t const length = (std::numeric_limits<T>::digits + std::numeric_limits<int>::digits - 1) / std::numeric_limits<int>::digits; which should actually mean (pseudo formular): std::size_t const length = (std::numeric_limits<T>::digits2 + std::numeric_limits<int>::digits - 1) / std::numeric_limits<int>::digits; where the (non-existing) constant digits2 would describe the "Number of base 2 digits that can be represented without change." To my opinion boost itself provides a simple helper class, namely static_log2, which allows the correct implementation by using the extended formular #include <boost/integer/static_log2.hpp> ... std::size_t const length = (std::numeric_limits<T>::digits * boost::static_log2<std::numeric_limits<T >::radix>::value + std::numeric_limits<int>::digits - 1) / std::numeric_limits<int>::digits; Note that the expression boost::static_log2<std::numeric_limits<T>::radix>::value is exactly 1 in the usual base-2 case, but e.g. 4 in case of base-16. My proposed fix is exact in all cases, where radix is a power of 2, in other cases (like base-10) it would at least be a better approximation than the current one. Greetings from Bremen, Daniel Krügler

2 2

Problem building Boost 1.33 .0 under Cygwin
by Clarke, Carus V 23 Aug '05

23 Aug '05

Hi, I am having a problem building Boost 1.33.0 using gcc under the current version of Cygwin. The build aborts after displaying the following messages: Building Boost.Regex with the optional Unicode/ICU support disabled. Please refer to the Boost.Regex documentation for more information (and if you don't know what ICU is then you probably don't need it). unknown target type for <@boost!libs!test!build>libboost_prg_exec_monitor.dll Could anyone tell me what I am missing? Version 1.32.0 built on my machine with no problems. Thanks, Carus V. (Bud) Clarke carus.v.clarke(a)boeing.com

4 6

Suggestion for Boost.Thread
by ycc 23 Aug '05

23 Aug '05

Hi, booster, I am using boost.thread in Windows with VC6, it's quite handy and useful. I found it's better if the library can add 2 additional methods. One is the typedef platform_dependent thread_id_type; thread_id_type id() const ; sometimes I want to know what thread is really in the log file. so I can write this: std::cout << thread().id() << std::endl; another one is a way to return the raw thread_handle. typedef platform_dependent thread_handle thread_handle handle() const ; by this, I can suspend, terminate the thread in Windows, or in Posix platform using #ifdef. For example; boost::thread t(...); #ifdef WINDOWS ::TerminateThread(t.handle()); #endif Is this doable? Thanks.

2 2

"failed to write command file!" while installing boost 1.33
by tom gee 22 Aug '05

22 Aug '05

Can anybody help me out? here's my procedures: 1. build bjam from the source. 2. run bjam "-sTOOLS=vc-7_1" "--with-python-root=D:\Python24" install After hundreds of successful items, the process suddenly stop with an error "failed to write command file!". I tried seveal times, with or without compiling python libraries, It stopped ramdonly,sometimes at the python libraries, others at the multi-thread libraries. My system is Windows XP SP2 English, with Visual studio 2003. I have have VC2005 express b2 installed. Previously, I encountered the same problem with boost 1.33b2. but i have no problem with boost 1.32 which I 've been happy with for a long time.

2 1

Does Boost support Windows 98?
by Matt England 22 Aug '05

22 Aug '05

Hello, I realize this is a rather ambiguous question, but I thought I'd start somewhere: Does Boost support Windows 98? If it's only partial support, what is missing? (I realize that there are many Boost libraries, and this answer might be a per-library question.) I see vague references in email lists to win98 support, but I'm hoping to find an official reference. I am managing a software development project based on MinGW/Boost, hoping to not have to support Win98, but I just realized that now we need to do so (support win98). Hence my question comes a bit after the fact. Thanks for any help, -Matt

2 1

XML-Serialization_Problem with loading...
by p.speck＠ewersbach.net 22 Aug '05

22 Aug '05

I have a problem with serialization in XML-format. The ser.routine saves the data as xml, but when trying to reload, the execution breaks. When using the text-output saving and loading works fine... I hope someone can help me: Here the code of the functions: ------------------------------------------------ main.cpp: ------------------------------------------------ #include "fixture.h" #include <boost/archive/xml_oarchive.hpp> #include <boost/archive/xml_iarchive.hpp> #include <iostream> #include <fstream> #include <string> #include <sstream> void save(CFixture* fixt, const char* filename) { ofstream ofs(filename); assert(ofs.good()); boost::archive::xml_oarchive oa(ofs); oa << BOOST_SERIALIZATION_NVP(*fixt); ofs.close(); } void load(CFixture* fixt, const char* filename) { ifstream ifs(filename); assert(ifs.good()); cout << filename << endl; boost::archive::xml_iarchive ia(ifs); cout << "Archive" << endl; ia >> BOOST_SERIALIZATION_NVP(*fixt); cout << "loaded" << endl; ifs.close(); } -------------------------------------------------- fixture.h: ------------------------------------------------- /* Header für Fixtures */ #include <vector> #include <string> #include <boost/archive/text_oarchive.hpp> #include <boost/archive/text_iarchive.hpp> #include <boost/serialization/string.hpp> #include <boost/serialization/vector.hpp> #include <boost/serialization/nvp.hpp> class CFvalue { public: friend class boost::serialization::access; template<class Archive> void serialize(Archive & ar, const unsigned int version) { cout << "CFvalue" << endl; ar & BOOST_SERIALIZATION_NVP(min); ar & BOOST_SERIALIZATION_NVP(max); ar & BOOST_SERIALIZATION_NVP(name); ar & BOOST_SERIALIZATION_NVP(picture); } //...CUT...// class CFunctionvalues { protected: string svalue; int dvalue; int dvalue2; double pvalue; public: virtual bool setdvalue(int) = 0; virtual bool setdvalue2(int) = 0; virtual bool setpvalue(double) = 0; virtual bool setsvalue(const char*) = 0; virtual int getdvalue() = 0; virtual int getdvalue2() = 0; virtual double getpvalue() = 0; virtual string getsvalue() = 0; friend class boost::serialization::access; template<class Archive> void serialize(Archive & ar, const unsigned int version) { cout << "CFunctionvalue" << endl; ar & BOOST_SERIALIZATION_NVP(svalue); ar & BOOST_SERIALIZATION_NVP(dvalue); ar & BOOST_SERIALIZATION_NVP(dvalue2); ar & BOOST_SERIALIZATION_NVP(pvalue); } }; class CFunction : public CFunctionvalues { public: friend class boost::serialization::access; template<class Archive> void serialize(Archive & ar, const unsigned int version) { cout << "CFunction" << endl; ar & BOOST_SERIALIZATION_NVP(min); ar & BOOST_SERIALIZATION_NVP(max); ar & BOOST_SERIALIZATION_NVP(channel); ar & BOOST_SERIALIZATION_NVP(channel2); ar & BOOST_SERIALIZATION_NVP(has16bit); ar & BOOST_SERIALIZATION_NVP(type); ar & BOOST_SERIALIZATION_NVP(inverted); ar & BOOST_SERIALIZATION_NVP(name); ar & BOOST_SERIALIZATION_NVP(valuelist); ar & BOOST_SERIALIZATION_BASE_OBJECT_NVP(CFunctionvalues); } //...CUT...// class CFunctionset : public CFunctionvalues { protected: CFunction* base; public: friend class boost::serialization::access; template<class Archive> void serialize(Archive & ar, const unsigned int version) { cout << "CFunctionset" << endl; ar & BOOST_SERIALIZATION_BASE_OBJECT_NVP(CFunctionvalue); } //...CUT...// ------------------------------------------------- XML-Output ------------------------------------------------- <?xml version="1.0" encoding="UTF-8" standalone="yes" ?> <!DOCTYPE boost_serialization> <boost_serialization signature="serialization::archive" version="3"> <*fixt class_id="0" tracking_level="0" version="0"> <channels>2</channels> <type>1</type> <name>MAX250</name> <manufacturer>GLP</manufacturer> <picture>max.jpg</picture> <functions class_id="1" tracking_level="0" version="0"> <count>2</count> <item class_id="2" tracking_level="0" version="0"> <min>0</min> <max>255</max> <channel>1</channel> <channel2>0</channel2> <has16bit>0</has16bit> <type>1</type> <inverted>0</inverted> <name>PAN</name> <valuelist class_id="3" tracking_level="0" version="0"> <count>2</count> <item class_id="4" tracking_level="0" version="0"> <min>0</min> <max>100</max> <name>links</name> <picture></picture> </item> <item> <min>101</min> <max>255</max> <name>rechts</name> <picture></picture> </item> </valuelist> <svalue></svalue> <dvalue>0</dvalue> <dvalue2>0</dvalue2> <pvalue>0</pvalue> </item> <item> <min>0</min> <max>255</max> <channel>4</channel> <channel2>0</channel2> <has16bit>0</has16bit> <type>3</type> <inverted>0</inverted> <name>COLOR</name> <valuelist> <count>3</count> <item> <min>0</min> <max>50</max> <name>White</name> <picture></picture> </item> <item> <min>51</min> <max>100</max> <name>Rot</name> <picture></picture> </item> <item> <min>101</min> <max>255</max> <name>Gelb</name> <picture></picture> </item> </valuelist> <svalue></svalue> <dvalue>0</dvalue> <dvalue2>0</dvalue2> <pvalue>0</pvalue> </item> </functions> </*fixt>

2 2

boost logging from shared libraries
by Austin Bingham 22 Aug '05

22 Aug '05

First, I wasn't sure where would be the most appropriate place to post this question, so I apologize if it's gone to the wrong place. I'm trying to figure out how to put logging statements in some shared libraries which are then controlled via manipulate_logs() calls an the executable that uses the libraries. It appears, after some rudimentary experiments, that this does not work, and I was hoping to find out if there is a way to do it. The logging system, of course, does log manipulation using log names and regular expression matching. As such, I assumed that logs were statically allocated and, in some way, all registered with some central registry which made them all available via their names. Stepping through logging calls in the libraries seems to indicate that logging code is being accessed and, as far as I can tell, the logs are "enabled" and, in fact, trying to log messages (to cout, for what it's worth). However, I don't see anything printed except for log messages genereted from the executable's source code. So, is what I'm trying to do even feasible? I would love to be able to have diagnostics built into my libraries which I could dis/enable as necessary from the executive level. Hopefully I'm just missing something simple. Thanks. -- Austin Bingham "If I were creating the world I wouldn't mess about with butterflies and daffodils. I would have started with lasers, eight o'clock, Day One!" Evil

2 4

XML-Serialization_Problem with loading: Debug output
by p.speck＠ewersbach.net 22 Aug '05

22 Aug '05

#0 0x4013383b in raise () from /lib/tls/libc.so.6 #1 0x40134fa2 in abort () from /lib/tls/libc.so.6 #2 0x400b6f57 in __cxa_call_unexpected () from /usr/lib/libstdc++.so.5 #3 0x400b6f94 in std::terminate () from /usr/lib/libstdc++.so.5 #4 0x400b7106 in __cxa_throw () from /usr/lib/libstdc++.so.5 #5 0x0805d1a3 in boost::archive::basic_xml_iarchive<boost::archive::xml_iarchive>::load_start () #6 0x0804d34b in boost::archive::basic_xml_iarchive<boost::archive::xml_iarchive>::load_override<CFixture> () #7 0x0804d328 in boost::archive::xml_iarchive_impl<boost::archive::xml_iarchive>::load_override<boost::serialization::nvp<CFixture> > () #8 0x0804cb08 in boost::archive::detail::interface_iarchive<boost::archive::xml_iarchive>::operator>><boost::serialization::nvp<CFixture> > () #9 0x0804bf05 in load () #10 0x0804bac4 in main ()

1 0

MPL: Creating a vector of vector_c's from a vector_c
by Pascal Bauer 22 Aug '05

22 Aug '05

Hello, I have the following problem: Given typedef mpl::vector_c<int, 3, 0, 3, 6, 9> MyVector; Now, I wish to create a mpl::vector with 3 entries that look like mpl::vector< mpl::vector_c<int, 1, 0, 3, 6, 9>, mpl::vector_c<int, 1, 1, 4, 7, 10>, mpl::vector_c<int, 1, 2, 5, 8, 11> > In words The first number in MyVector gives me the number of resulting vector_c types. the resulting types should contain a 1 instead of that number. The other numbers should be replace gradualy: The first vector_c should contain the same numbers as the original type. In the second vector_c, all the numbers should be incremented by one, and so forth. I have to admit, that this task overstrains me, so it would be very kind, if someone could help me to figure this out. Cheers Pascal Bauer -- ************************************ * Pascal Bauer * * * * Theoretical Astrophysics Group * * Mail: pascal.bauer(a)phim.unibe.ch * ************************************

1 0

[date_time] timezone bug for boost::posix_time::microsec_clock::local_time()
by Brendon Costa 22 Aug '05

22 Aug '05

Hi, I have noticed that there seems to be a problem with the boost date_time library 1.33 (Downloaded about 2 days ago) when trying to use the localtime information under a NetBSD system. Specifically when I have a small test program: #include "boost/date_time/posix_time/posix_time.hpp" #include "boost/date_time/c_local_time_adjustor.hpp" #include <iostream> int main() { using namespace boost::posix_time; ptime loc = microsec_clock::local_time(); ptime utc = microsec_clock::universal_time(); std::cout << "Local: " << to_simple_string(loc) << std::endl; std::cout << "UTC: " << to_simple_string(utc) << std::endl; std::cout << "Local again: " << to_simple_string( boost::date_time::c_local_adjustor<ptime>::utc_to_local(utc)) << std::endl; return 0; } It will display the same time for both UTC time and Local time (Living in Melbourn Australia) where I expected them to differ. I found that the above program would fail unless I did the following: #include "boost/date_time/posix_time/posix_time.hpp" #include "boost/date_time/c_local_time_adjustor.hpp" #include <iostream> int main() { using namespace boost::posix_time; tzset(); ptime loc = microsec_clock::local_time(); ptime utc = microsec_clock::universal_time(); std::cout << "Local: " << to_simple_string(loc) << std::endl; std::cout << "UTC: " << to_simple_string(utc) << std::endl; std::cout << "Local again: " << to_simple_string( boost::date_time::c_local_adjustor<ptime>::utc_to_local(utc)) << std::endl; return 0; } Thanks, Brendon Costa.

2 3

[serialization] dynamic arrays of chars
by Ivan 21 Aug '05

21 Aug '05

I have a parser and there is one big object that holds the whole file being parsed as a dynamic array class File { public char * ptr; }; File file; file.ptr = new char[very_big_number_like_100000]; The parser creates a lot of objects that keep pointers into this dynamic array. class A { char* internalPtr1; }; class B { char* internalPtr2; }; class C { char* internalPtr3; }; A a; B b; C c; a.internalPtr1 = file.ptr + 234; b.internalPtr2 = file.ptr + 10673; c.internalPtr3 = file.ptr + 9583; How could I serialize the file object and these numerous small objects? I could write separate save/load for each of these A, B, C and so on but I'll need access to File::ptr inside the save/load funcs and this would be an ugly solution. Any ideas?

2 2

How do I convince bjam to build multi-threaded libraries?
by Andrew Schweitzer 21 Aug '05

21 Aug '05

I'm not getting the "=mt" version of the library I'm building. When I run bjam, it just doesn't build the "-mt" versions. I *think* it did in the past, I just don't know how I convinced it to do so. A cursory look at the "getting started" page didn't reveal the answer. Do I just need to look more closely? Any pointers appreciated. Here's what I do: Download windows bjam.exe to boost directory. open command prompt. cd to libs\log\build call vcvars32.bat call ..\..\..\bjam Thanks Andrew

4 3

lambda vs string concatenation
by jll＠soundobjectlogic.com 21 Aug '05

21 Aug '05

Hello, I'm just discovering Boost, and it looks great. However, I can't get the following code to work. I use g++ (GCC) 3.4.4 20050721 and boost 1.32 (also tried 1.33). When I try a similar example with mere integers it works though... #include <string> #include <sstream> #include <iterator> #include <vector> #include <boost/lambda/bind.hpp> #include <boost/lambda/lambda.hpp> using namespace std; using namespace boost::lambda; int main() { vector<string> cols; cols.push_back("foo"); string prefix = "t1."; for_each(cols.begin(), cols.end(), _1 = prefix + _1); cout << cols.front() << endl; return 0; } g++ t.cpp && ./a.out /usr/include/boost/lambda/detail/operator_lambda_func_base.hpp: In member function `RET boost::lambda::lambda_functor_base<boost::lambda::other_action<boost::lambda::assignment_action>, Args>::call(A&, B&, C&, Env&) const [with RET = std::basic_string<char, std::char_traits<char>, std::allocator<char> >&, A = std::basic_string<char, std::char_traits<char>, std::allocator<char> >, B = const boost::tuples::null_type, C = const boost::tuples::null_type, Env = const boost::tuples::null_type, Args = boost::tuples::tuple<boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::arithmetic_action<boost::lambda::plus_action>, boost::tuples::tuple<const std::string, boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> > >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type>]': /usr/include/boost/lambda/detail/lambda_functors.hpp:146: instantiated from `typename T::sig<boost::tuples::tuple<A&, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> >::type boost::lambda::lambda_functor<Base>::operator()(A&) const [with A = std::basic_string<char, std::char_traits<char>, std::allocator<char> >, T = boost::lambda::lambda_functor_base<boost::lambda::other_action<boost::lambda::assignment_action>, boost::tuples::tuple<boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::arithmetic_action<boost::lambda::plus_action>, boost::tuples::tuple<const std::string, boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> > >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> >]' /usr/lib/gcc/i386-redhat-linux/3.4.4/../../../../include/c++/3.4.4/bits/stl_algo.h:158: instantiated from `_Function std::for_each(_InputIterator, _InputIterator, _Function) [with _InputIterator = __gnu_cxx::__normal_iterator<std::string*, std::vector<std::string, std::allocator<std::string> > >, _Function = boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::other_action<boost::lambda::assignment_action>, boost::tuples::tuple<boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::arithmetic_action<boost::lambda::plus_action>, boost::tuples::tuple<const std::string, boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> > >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> > >]' t.cpp:16: instantiated from here /usr/include/boost/lambda/detail/operator_lambda_func_base.hpp:237: error: no match for 'operator=' in 'boost::lambda::detail::select [with Arg = boost::lambda::placeholder<1>, A = std::basic_string<char, std::char_traits<char>, std::allocator<char> >, B = const boost::tuples::null_type, C = const boost::tuples::null_type, Env = const boost::tuples::null_type](((const boost::lambda::lambda_functor<boost::lambda::placeholder<1> >&)(+boost::tuples::get [with int N = 0, HT = boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, TT = boost::tuples::cons<boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::arithmetic_action<boost::lambda::plus_action>, boost::tuples::tuple<const std::string, boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> > >, boost::tuples::null_type>](((const boost::tuples::cons<boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, boost::tuples::cons<boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::arithmetic_action<boost::lambda::plus_action>, boost::tuples::tuple<const std::string, boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> > >, boost::tuples::null_type> >&)((const boost::tuples::cons<boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, boost::tuples::cons<boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::arithmetic_action<boost::lambda::plus_action>, boost::tuples::tuple<const std::string, boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> > >, boost::tuples::null_type> >*)((const boost::tuples::tuple<boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::arithmetic_action<boost::lambda::plus_action>, boost::tuples::tuple<const std::string, boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> > >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type>*)this)))))), ((std::basic_string<char, std::char_traits<char>, std::allocator<char> >&)(+a)), ((const boost::tuples::null_type&)(+b)), ((const boost::tuples::null_type&)(+c)), ((const boost::tuples::null_type&)(+env))) = boost::lambda::detail::select [with Arg = boost::lambda::lambda_functor_base<boost::lambda::arithmetic_action<boost::lambda::plus_action>, boost::tuples::tuple<const std::string, boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> >, A = std::basic_string<char, std::char_traits<char>, std::allocator<char> >, B = const boost::tuples::null_type, C = const boost::tuples::null_type, Env = const boost::tuples::null_type](((const boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::arithmetic_action<boost::lambda::plus_action>, boost::tuples::tuple<const std::string, boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> > >&)(+boost::tuples::get [with int N = 1, HT = boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, TT = boost::tuples::cons<boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::arithmetic_action<boost::lambda::plus_action>, boost::tuples::tuple<const std::string, boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> > >, boost::tuples::null_type>](((const boost::tuples::cons<boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, boost::tuples::cons<boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::arithmetic_action<boost::lambda::plus_action>, boost::tuples::tuple<const std::string, boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> > >, boost::tuples::null_type> >&)((const boost::tuples::cons<boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, boost::tuples::cons<boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::arithmetic_action<boost::lambda::plus_action>, boost::tuples::tuple<const std::string, boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> > >, boost::tuples::null_type> >*)((const boost::tuples::tuple<boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::arithmetic_action<boost::lambda::plus_action>, boost::tuples::tuple<const std::string, boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> > >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type>*)this)))))), ((std::basic_string<char, std::char_traits<char>, std::allocator<char> >&)(+a)), ((const boost::tuples::null_type&)(+b)), ((const boost::tuples::null_type&)(+c)), ((const boost::tuples::null_type&)(+env)))' /usr/lib/gcc/i386-redhat-linux/3.4.4/../../../../include/c++/3.4.4/bits/basic_string.h:426: note: candidates are: std::basic_string<_CharT, _Traits, _Alloc>& std::basic_string<_CharT, _Traits, _Alloc>::operator=(const std::basic_string<_CharT, _Traits, _Alloc>&) [with _CharT = char, _Traits = std::char_traits<char>, _Alloc = std::allocator<char>] /usr/lib/gcc/i386-redhat-linux/3.4.4/../../../../include/c++/3.4.4/bits/basic_string.h:437: note: std::basic_string<_CharT, _Traits, _Alloc>& std::basic_string<_CharT, _Traits, _Alloc>::operator=(const _CharT*) [with _CharT = char, _Traits = std::char_traits<char>, _Alloc = std::allocator<char>] /usr/lib/gcc/i386-redhat-linux/3.4.4/../../../../include/c++/3.4.4/bits/basic_string.h:451: note: std::basic_string<_CharT, _Traits, _Alloc>& std::basic_string<_CharT, _Traits, _Alloc>::operator=(_CharT) [with _CharT = char, _Traits = std::char_traits<char>, _Alloc = std::allocator<char>] /usr/include/boost/lambda/detail/operator_lambda_func_base.hpp: In member function `RET boost::lambda::lambda_functor_base<boost::lambda::arithmetic_action<boost::lambda::plus_action>, Args>::call(A&, B&, C&, Env&) const [with RET = boost::lambda::detail::return_type_deduction_failure<boost::lambda::detail::return_type_2_arithmetic_phase_3<std::string, std::string> >, A = std::basic_string<char, std::char_traits<char>, std::allocator<char> >, B = const boost::tuples::null_type, C = const boost::tuples::null_type, Env = const boost::tuples::null_type, Args = boost::tuples::tuple<const std::string, boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type>]': /usr/include/boost/lambda/detail/select_functions.hpp:28: instantiated from `typename Arg::sig<boost::tuples::tuple<A&, B&, C&, Env&, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> >::type boost::lambda::detail::select(const boost::lambda::lambda_functor<T>&, A&, B&, C&, Env&) [with Arg = boost::lambda::lambda_functor_base<boost::lambda::arithmetic_action<boost::lambda::plus_action>, boost::tuples::tuple<const std::string, boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> >, A = std::basic_string<char, std::char_traits<char>, std::allocator<char> >, B = const boost::tuples::null_type, C = const boost::tuples::null_type, Env = const boost::tuples::null_type]' /usr/include/boost/lambda/detail/operator_lambda_func_base.hpp:237: instantiated from `RET boost::lambda::lambda_functor_base<boost::lambda::other_action<boost::lambda::assignment_action>, Args>::call(A&, B&, C&, Env&) const [with RET = std::basic_string<char, std::char_traits<char>, std::allocator<char> >&, A = std::basic_string<char, std::char_traits<char>, std::allocator<char> >, B = const boost::tuples::null_type, C = const boost::tuples::null_type, Env = const boost::tuples::null_type, Args = boost::tuples::tuple<boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::arithmetic_action<boost::lambda::plus_action>, boost::tuples::tuple<const std::string, boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> > >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type>]' /usr/include/boost/lambda/detail/lambda_functors.hpp:146: instantiated from `typename T::sig<boost::tuples::tuple<A&, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> >::type boost::lambda::lambda_functor<Base>::operator()(A&) const [with A = std::basic_string<char, std::char_traits<char>, std::allocator<char> >, T = boost::lambda::lambda_functor_base<boost::lambda::other_action<boost::lambda::assignment_action>, boost::tuples::tuple<boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::arithmetic_action<boost::lambda::plus_action>, boost::tuples::tuple<const std::string, boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> > >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> >]' /usr/lib/gcc/i386-redhat-linux/3.4.4/../../../../include/c++/3.4.4/bits/stl_algo.h:158: instantiated from `_Function std::for_each(_InputIterator, _InputIterator, _Function) [with _InputIterator = __gnu_cxx::__normal_iterator<std::string*, std::vector<std::string, std::allocator<std::string> > >, _Function = boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::other_action<boost::lambda::assignment_action>, boost::tuples::tuple<boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::arithmetic_action<boost::lambda::plus_action>, boost::tuples::tuple<const std::string, boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> > >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> > >]' t.cpp:16: instantiated from here /usr/include/boost/lambda/detail/operator_lambda_func_base.hpp:206: error: conversion from `std::basic_string<char, std::char_traits<char>, std::allocator<char> >' to non-scalar type `boost::lambda::detail::return_type_deduction_failure<boost::lambda::detail::return_type_2_arithmetic_phase_3<std::string, std::string> >' requested -- Jean-Louis Leroy Sound Object Logic http://www.soundobjectlogic.com

2 1

some bug in hash library of boost 1.33
by 沈慧峰 20 Aug '05

20 Aug '05

example points.cpp has a big bug leads to can not compile line 23 error : return x = other.x && y == other.y; The correct code must be : return x == other.x && y == other.y;

2 1

boost::program_options endless-loop ?
by Leon Mergen 20 Aug '05

20 Aug '05

Hello, I'm trying to integrate the boost::program_options library into my application, but am running into some strange problems. For some reason, when calling the boost::program_options::store() function, the program enters an endless loop running processor usage too 100%. I've created a test-case which generates this error for me (see attachment). This is the output of the application: ======================================================================= lmergen@solatis3:~/Projects/Tsukku Client/src2 $ ./TsukkuNode 1 2 3 4 5 6 ======================================================================= And here it enters the endless loop. When I lookup the process id and do a kill -11 to easily generate a core dump, it looks like it's messing around with mutexes: ======================================================================= #0 0xffffe410 in __kernel_vsyscall () #1 0xb7d6325b in __lll_mutex_lock_wait () from /lib/tls/i686/cmov/libpthread.so.0 #2 0xb7d60690 in _L_mutex_lock_26 () from /lib/tls/i686/cmov/libpthread.so.0 #3 0xbffff598 in ?? () #4 0xb7ff6730 in _dl_map_object_deps () from /lib/ld-linux.so.2 #5 0x080604dd in scoped_lock (this=0x80b4bc4, m=@0x1) at lwm_pthreads.hpp:72 #6 0x080604dd in scoped_lock (this=0xbffff5c0, m=@0x80b4bc4) at lwm_pthreads.hpp:72 #7 0x0805faed in boost::detail::sp_counted_base::release (this=0x80b4bb8) at shared_count.hpp:140 #8 0x0805f0c7 in ~shared_count (this=0xbffff6a4) at shared_count.hpp:378 #9 0xb7f0e700 in boost::program_options::common_command_line_parser::run () from /usr/lib/libboost_program_options-gcc-1_32.so.1.32.0 #10 0x0805d969 in boost::program_options::basic_command_line_parser<char>::run (this=0xbffff7d0) at parsers.hpp:84 #11 0x0805d8b3 in boost::program_options::parse_command_line<char> (argc=1, argv=0xbffffa94, desc=@0xbffff9c0, style=0, ext=Cannot access memory at address 0xfffffff5 ) at parsers.hpp:97 #12 0x0805d514 in main (argc=1, argv=0xbffffa94) at Main.cpp:28 ======================================================================= Line number 28 at Main.cpp is "boost::program_options::store ( boost::program_options::parse_command_line ( argc, argv, desc ), vm );". I've tested this, and it does the same when parsing the config file before the command line. Anyone has any idea what's causing this problem ? Thanks in advance! Regards, Leon Mergen

1 1

[1.33.0][date_time] Weird warning
by Paul 20 Aug '05

20 Aug '05

I got the following warning while compiling with (debian-testing) g++ 4.0.1-2 I couldn't see the problem in the code? /usr/local/include/boost-1_33/boost/date_time/time_duration.hpp: In function 'time_duration boost::date_time::parse_undelimited_time_duration(const std::string&) [with time_duration = boost::posix_time::time_duration]': /usr/local/include/boost-1_33/boost/date_time/time_duration.hpp:58: warning: control may reach end of non-void function 'static typename frac_sec_type::int_type boost::date_time::time_resolution_traits<frac_sec_type, res, resolution_adjust, frac_digits, v_type>::to_tick_count(v_type, v_type, v_type, typename frac_sec_type::int_type) [with frac_sec_type = boost::date_time::time_resolution_traits_adapted64_impl, boost::date_time::time_resolutions res = micro, typename frac_sec_type::int_type resolution_adjust = 1000000, short unsigned int frac_digits = 6u, v_type = int32_t]' being inlined Just a bit concerned, I don't like warnings :) Paul

3 3

Can't build with intel 9.0
by Mike Gibson 20 Aug '05

20 Aug '05

I was having problems getting boost 1.32 to build with the intel 9.0 compiler and saw that 1.33 was out and listed support for intel 9.0. I can't get it to build though. I get an error compiling greg_month.cpp in lexical_cast.hpp(156). I'm building using the following command: C:\src\boost\boost_1_33_0>bjam -sTOOLS=intel-win32 -sINTEL_PATH="C:\Program Files\Intel\Compiler\C++\9.0\IA32" install Here is the error: C:\src\boost\boost_1_33_0/boost/lexical_cast.hpp(156): error: no operator ">>" matches these operands operand types are: std::basic_stringstream<char, std::char_traits<char>, std::allocator<char>> >> boost::date_time::date_names_put<boost::grego rian::greg_facet_config, wchar_t, std::ostreambuf_iterator<wchar_t, std::char_traits<wchar_t>>>::string_type stream >> output && ^

3 6

Build the dll version of regex fails with vc-7_1-stlport
by 沈慧峰 20 Aug '05

20 Aug '05

Since the stl library of vc7.1 has some bugs and insufficiency. I use stlport libray all the times. I compile regex library with stlport 4.62 and 5.0RC4, with or without the ICU. The dll all can not be compiled successfully! (In below I only describe the compile process with ICU.) First I try the stlport 4.62 with VC7.1 to build the library of regex, the script I use is(the icu is also compiled with the same stlport) : call "c:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\bin\vcvars32.bat" set TOOLS=vc-7_1-stlport set STLPORT_PATH=c:\opt set STLPORT_4.62_PATH=C:\opt\STLport-4.6.2 set STLPORT_VERSION=4.6.2 set ICU_PATH=c:\opt\icu bjam "-sBUILD=debug release <runtime-link>dynamic <threading>multi <native-wchar_t>on" "-sICU_PATH=c:\opt\icu" --with-regex stage But the dll files can not be compiled successfully. The error occurs when linking(Attentions the exp and pdb files exists). vc-Link bin\boost\libs\regex\build\boost_regex.dll\vc-7_1-stlport\debug\native-wchar_t-on\threading-multi\boost_regex-vc71-mt-gdp-1_33.dll bin\boost\libs\regex\build\boost_regex.dll\vc-7_1-stlport\debug\native-wchar_t-on\threading-multi\boost_regex-vc71-mt-gdp-1_33.lib Creating library bin\boost\libs\regex\build\boost_regex.dll\vc-7_1-stlport\debug\native-wchar_t-on\threading-multi\boost_regex-vc71-mt-gdp-1_33.lib and object bin\boost\libs\regex\build\boost_regex.dll\vc-7_1-stlport\debug\native-wchar_t-on\threading-multi\boost_regex-vc71-mt-gdp-1_33.exp w32_regex_traits.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) public: __thiscall _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >::~basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >(void)" (__imp_??1?$basic_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@QAE@XZ) referenced in function "class _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> > __cdecl boost::re_detail::w32_transform(unsigned long,unsigned short const *,unsigned short const *)" (?w32_transform@re_detail@boost@@YA?AV?$basic_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@KPBG0@Z) wc_regex_traits.obj : error LNK2001: unresolved external symbol "__declspec(dllimport) public: __thiscall _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >::~basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >(void)" (__imp_??1?$basic_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@QAE@XZ) usinstances.obj : error LNK2001: unresolved external symbol "__declspec(dllimport) public: __thiscall _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >::~basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >(void)" (__imp_??1?$basic_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@QAE@XZ) w32_regex_traits.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) public: __thiscall _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >(unsigned short const *,class _STL::allocator<unsigned short> const &)" (__imp_??0?$basic_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@QAE@PBGABV?$allocator@G@1@@Z) referenced in function "class _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> > __cdecl boost::re_detail::w32_cat_get(class boost::shared_ptr<void> const &,unsigned long,int,class _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> > const &)" (?w32_cat_get@re_detail@boost@@YA?AV?$basic_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@ABV?$shared_ptr@X@2@KHABV34@@Z) w32_regex_traits.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) public: __thiscall _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >(class _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> > const &)" (__imp_??0?$basic_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@QAE@ABV01@@Z) referenced in function "class _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> > __cdecl boost::re_detail::w32_cat_get(class boost::shared_ptr<void> const &,unsigned long,int,class _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> > const &)" (?w32_cat_get@re_detail@boost@@YA?AV?$basic_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@ABV?$shared_ptr@X@2@KHABV34@@Z) wc_regex_traits.obj : error LNK2001: unresolved external symbol "__declspec(dllimport) public: __thiscall _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >(class _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> > const &)" (__imp_??0?$basic_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@QAE@ABV01@@Z) usinstances.obj : error LNK2001: unresolved external symbol "__declspec(dllimport) public: __thiscall _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >(class _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> > const &)" (__imp_??0?$basic_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@QAE@ABV01@@Z) w32_regex_traits.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) public: class _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> > & __thiscall _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >::append(unsigned int,unsigned short)" (__imp_?append@?$basic_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@QAEAAV12@IG@Z) referenced in function "class _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> > __cdecl boost::re_detail::w32_transform(unsigned long,unsigned short const *,unsigned short const *)" (?w32_transform@re_detail@boost@@YA?AV?$basic_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@KPBG0@Z) usinstances.obj : error LNK2001: unresolved external symbol "__declspec(dllimport) public: class _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> > & __thiscall _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >::append(unsigned int,unsigned short)" (__imp_?append@?$basic_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@QAEAAV12@IG@Z) w32_regex_traits.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) public: __thiscall _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >(void)" (__imp_??0?$basic_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@QAE@XZ) referenced in function "class _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> > __cdecl boost::re_detail::w32_transform(unsigned long,unsigned short const *,unsigned short const *)" (?w32_transform@re_detail@boost@@YA?AV?$basic_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@KPBG0@Z) usinstances.obj : error LNK2001: unresolved external symbol "__declspec(dllimport) public: __thiscall _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >(void)" (__imp_??0?$basic_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@QAE@XZ) w32_regex_traits.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) public: __thiscall _STL::_Nondebug_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >::~_Nondebug_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >(void)" (__imp_??1?$_Nondebug_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@QAE@XZ) referenced in function $L42681 wc_regex_traits.obj : error LNK2001: unresolved external symbol "__declspec(dllimport) public: __thiscall _STL::_Nondebug_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >::~_Nondebug_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >(void)" (__imp_??1?$_Nondebug_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@QAE@XZ) usinstances.obj : error LNK2001: unresolved external symbol "__declspec(dllimport) public: __thiscall _STL::_Nondebug_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >::~_Nondebug_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >(void)" (__imp_??1?$_Nondebug_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@QAE@XZ) w32_regex_traits.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) public: class _STL::_Nondebug_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> > * __thiscall _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >::_Get_base(void)" (__imp_?_Get_base@?$basic_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@QAEPAV?$_Nondebug_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@2@XZ) referenced in function "public: __thiscall _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> ><unsigned short const *>(unsigned short const *,unsigned short const *,class _STL::allocator<unsigned short> const &)" (??$?0PBG@?$basic_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@QAE@PBG0ABV?$allocator@G@1@@Z) wc_regex_traits.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) public: class _STL::_Nondebug_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> > * __thiscall _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >::_Get_base(void)" (__imp_?_Get_base@?$basic_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@QAEPAV?$_Nondebug_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@2@XZ) referenced in function "private: void __thiscall _STL::_Nondebug_string<wchar_t,class _STL::char_traits<wchar_t>,class _STL::allocator<wchar_t> >::_M_range_initialize<wchar_t const *>(wchar_t const *,wchar_t const *,struct _STL::forward_iterator_tag const &)" (??$_M_range_initialize@PB_W@?$_Nondebug_string@_WV?$char_traits@_W@_STL@@V?$allocator@_W@2@@_STL@@AAEXPB_W0ABUforward_iterator_tag@1@@Z) usinstances.obj : error LNK2001: unresolved external symbol "__declspec(dllimport) public: class _STL::_Nondebug_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> > * __thiscall _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >::_Get_base(void)" (__imp_?_Get_base@?$basic_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@QAEPAV?$_Nondebug_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@2@XZ) w32_regex_traits.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) public: __thiscall _STL::_String_base<unsigned short,class _STL::allocator<unsigned short> >::~_String_base<unsigned short,class _STL::allocator<unsigned short> >(void)" (__imp_??1?$_String_base@GV?$allocator@G@_STL@@@_STL@@QAE@XZ) referenced in function $L42777 wc_regex_traits.obj : error LNK2001: unresolved external symbol "__declspec(dllimport) public: __thiscall _STL::_String_base<unsigned short,class _STL::allocator<unsigned short> >::~_String_base<unsigned short,class _STL::allocator<unsigned short> >(void)" (__imp_??1?$_String_base@GV?$allocator@G@_STL@@@_STL@@QAE@XZ) usinstances.obj : error LNK2001: unresolved external symbol "__declspec(dllimport) public: __thiscall _STL::_String_base<unsigned short,class _STL::allocator<unsigned short> >::~_String_base<unsigned short,class _STL::allocator<unsigned short> >(void)" (__imp_??1?$_String_base@GV?$allocator@G@_STL@@@_STL@@QAE@XZ) w32_regex_traits.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) public: __thiscall _STL::_String_base<unsigned short,class _STL::allocator<unsigned short> >::_String_base<unsigned short,class _STL::allocator<unsigned short> >(class _STL::allocator<unsigned short> const &)" (__imp_??0?$_String_base@GV?$allocator@G@_STL@@@_STL@@QAE@ABV?$allocator@G@1@@Z) referenced in function "public: __thiscall _STL::_Nondebug_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >::_Nondebug_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> ><unsigned short const *>(unsigned short const *,unsigned short const *,class _STL::allocator<unsigned short> const &)" (??$?0PBG@?$_Nondebug_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@QAE@PBG0ABV?$allocator@G@1@@Z) wc_regex_traits.obj : error LNK2001: unresolved external symbol "__declspec(dllimport) public: __thiscall _STL::_String_base<unsigned short,class _STL::allocator<unsigned short> >::_String_base<unsigned short,class _STL::allocator<unsigned short> >(class _STL::allocator<unsigned short> const &)" (__imp_??0?$_String_base@GV?$allocator@G@_STL@@@_STL@@QAE@ABV?$allocator@G@1@@Z) usinstances.obj : error LNK2001: unresolved external symbol "__declspec(dllimport) public: __thiscall _STL::_String_base<unsigned short,class _STL::allocator<unsigned short> >::_String_base<unsigned short,class _STL::allocator<unsigned short> >(class _STL::allocator<unsigned short> const &)" (__imp_??0?$_String_base@GV?$allocator@G@_STL@@@_STL@@QAE@ABV?$allocator@G@1@@Z) w32_regex_traits.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) private: void __thiscall _STL::_Nondebug_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >::_M_terminate_string(void)" (__imp_?_M_terminate_string@?$_Nondebug_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@AAEXXZ) referenced in function "private: void __thiscall _STL::_Nondebug_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >::_M_range_initialize<unsigned short const *>(unsigned short const *,unsigned short const *,struct _STL::forward_iterator_tag const &)" (??$_M_range_initialize@PBG@?$_Nondebug_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@AAEXPBG0ABUforward_iterator_tag@1@@Z) wc_regex_traits.obj : error LNK2001: unresolved external symbol "__declspec(dllimport) private: void __thiscall _STL::_Nondebug_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >::_M_terminate_string(void)" (__imp_?_M_terminate_string@?$_Nondebug_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@AAEXXZ) usinstances.obj : error LNK2001: unresolved external symbol "__declspec(dllimport) private: void __thiscall _STL::_Nondebug_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >::_M_terminate_string(void)" (__imp_?_M_terminate_string@?$_Nondebug_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@AAEXXZ) w32_regex_traits.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) public: void __thiscall _STL::_String_base<unsigned short,class _STL::allocator<unsigned short> >::_M_allocate_block(unsigned int)" (__imp_?_M_allocate_block@?$_String_base@GV?$allocator@G@_STL@@@_STL@@QAEXI@Z) referenced in function "private: void __thiscall _STL::_Nondebug_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >::_M_range_initialize<unsigned short const *>(unsigned short const *,unsigned short const *,struct _STL::forward_iterator_tag const &)" (??$_M_range_initialize@PBG@?$_Nondebug_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@AAEXPBG0ABUforward_iterator_tag@1@@Z) wc_regex_traits.obj : error LNK2001: unresolved external symbol "__declspec(dllimport) public: void __thiscall _STL::_String_base<unsigned short,class _STL::allocator<unsigned short> >::_M_allocate_block(unsigned int)" (__imp_?_M_allocate_block@?$_String_base@GV?$allocator@G@_STL@@@_STL@@QAEXI@Z) usinstances.obj : error LNK2001: unresolved external symbol "__declspec(dllimport) public: void __thiscall _STL::_String_base<unsigned short,class _STL::allocator<unsigned short> >::_M_allocate_block(unsigned int)" (__imp_?_M_allocate_block@?$_String_base@GV?$allocator@G@_STL@@@_STL@@QAEXI@Z) usinstances.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) public: int __thiscall _STL::_Nondebug_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >::compare(class _STL::_Nondebug_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> > const &)const " (__imp_?compare@?$_Nondebug_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@QBEHABV12@@Z) referenced in function "public: int __cdecl boost::basic_regex<unsigned short,struct boost::regex_traits<unsigned short,class boost::w32_regex_traits<unsigned short> > >::compare(class boost::basic_regex<unsigned short,struct boost::regex_traits<unsigned short,class boost::w32_regex_traits<unsigned short> > > const &)const " (?compare@?$basic_regex@GU?$regex_traits@GV?$w32_regex_traits@G@boost@@@boost@@@boost@@QBAHABV12@@Z) usinstances.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) public: class _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> > & __thiscall _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >::operator=(class _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> > const &)" (__imp_??4?$basic_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@QAEAAV01@ABV01@@Z) referenced in function "public: class _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> > __thiscall boost::match_results<unsigned short const *,class _STL::allocator<struct boost::sub_match<unsigned short const *> > >::str(int)const " (?str@?$match_results@PBGV?$allocator@U?$sub_match@PBG@boost@@@_STL@@@boost@@QBE?AV?$basic_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@H@Z) usinstances.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) public: unsigned int __thiscall _STL::_Nondebug_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >::size(void)const " (__imp_?size@?$_Nondebug_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@QBEIXZ) referenced in function "public: class _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> > __thiscall boost::match_results<unsigned short const *,class _STL::allocator<struct boost::sub_match<unsigned short const *> > >::format(class _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> > const &,enum boost::regex_constants::_match_flags)const " (?format@?$match_results@PBGV?$allocator@U?$sub_match@PBG@boost@@@_STL@@@boost@@QBE?AV?$basic_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@ABV34@W4_match_flags@regex_constants@2@@Z) usinstances.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) public: unsigned short const * __thiscall _STL::_Nondebug_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >::data(void)const " (__imp_?data@?$_Nondebug_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@QBEPBGXZ) referenced in function "public: class _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> > __thiscall boost::match_results<unsigned short const *,class _STL::allocator<struct boost::sub_match<unsigned short const *> > >::format(class _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> > const &,enum boost::regex_constants::_match_flags)const " (?format@?$match_results@PBGV?$allocator@U?$sub_match@PBG@boost@@@_STL@@@boost@@QBE?AV?$basic_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@ABV34@W4_match_flags@regex_constants@2@@Z) usinstances.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) public: void __thiscall _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >::reserve(unsigned int)" (__imp_?reserve@?$basic_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@QAEXI@Z) referenced in function "public: class _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> > __thiscall boost::sub_match<unsigned short const *>::str(void)const " (?str@?$sub_match@PBG@boost@@QBE?AV?$basic_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@XZ) usinstances.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) public: __thiscall _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >(unsigned short const *,unsigned int,class _STL::allocator<unsigned short> const &)" (__imp_??0?$basic_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@QAE@PBGIABV?$allocator@G@1@@Z) referenced in function "public: class _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> > __cdecl boost::re_detail::basic_regex_implementation<unsigned short,struct boost::regex_traits<unsigned short,class boost::w32_regex_traits<unsigned short> > >::str(void)const " (?str@?$basic_regex_implementation@GU?$regex_traits@GV?$w32_regex_traits@G@boost@@@boost@@@re_detail@boost@@QBA?AV?$basic_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@XZ) usinstances.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) public: unsigned short * __thiscall _STL::_Nondebug_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >::end(void)" (__imp_?end@?$_Nondebug_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@QAEPAGXZ) referenced in function "bool __cdecl _STL::_Dereferenceable<struct _STL::_DBG_iter<class _STL::_Nondebug_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >,struct _STL::_Const_traits<unsigned short> > >(struct _STL::_DBG_iter<class _STL::_Nondebug_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >,struct _STL::_Const_traits<unsigned short> >)" (??$_Dereferenceable@U?$_DBG_iter@V?$_Nondebug_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@U?$_Const_traits@G@2@@_STL@@@_STL@@YA_NU?$_DBG_iter@V?$_Nondebug_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@U?$_Const_traits@G@2@@0@@Z) usinstances.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) public: unsigned short * __thiscall _STL::_Nondebug_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >::begin(void)" (__imp_?begin@?$_Nondebug_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@QAEPAGXZ) referenced in function "bool __cdecl _STL::_Incrementable<struct _STL::_DBG_iter_base<class _STL::_Nondebug_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> > > >(struct _STL::_DBG_iter_base<class _STL::_Nondebug_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> > > const &,int,struct _STL::random_access_iterator_tag const &)" (??$_Incrementable@U?$_DBG_iter_base@V?$_Nondebug_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@@_STL@@@_STL@@YA_NABU?$_DBG_iter_base@V?$_Nondebug_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@@0@HABUrandom_access_iterator_tag@0@@Z) usinstances.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) public: struct _STL::_DBG_iter<class _STL::_Nondebug_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >,struct _STL::_Nonconst_traits<unsigned short> > __thiscall _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >::begin(void)" (__imp_?begin@?$basic_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@QAE?AU?$_DBG_iter@V?$_Nondebug_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@U?$_Nonconst_traits@G@2@@2@XZ) referenced in function "public: unsigned long __thiscall boost::re_detail::w32_regex_traits_implementation<unsigned short>::lookup_classname(unsigned short const *,unsigned short const *)const " (?lookup_classname@?$w32_regex_traits_implementation@G@re_detail@boost@@QBEKPBG0@Z) usinstances.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) public: unsigned short & __thiscall _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >::operator[](unsigned int)" (__imp_??A?$basic_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@QAEAAGI@Z) referenced in function "public: unsigned long __thiscall boost::re_detail::w32_regex_traits_implementation<unsigned short>::lookup_classname(unsigned short const *,unsigned short const *)const " (?lookup_classname@?$w32_regex_traits_implementation@G@re_detail@boost@@QBEKPBG0@Z) usinstances.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) public: class _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> > & __thiscall _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >::assign(unsigned int,unsigned short)" (__imp_?assign@?$basic_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@QAEAAV12@IG@Z) referenced in function "unsigned short const * __cdecl boost::re_detail::re_is_set_member<unsigned short const *,unsigned short,struct boost::regex_traits<unsigned short,class boost::w32_regex_traits<unsigned short> >,unsigned long>(unsigned short const *,unsigned short const *,struct boost::re_detail::re_set_long<unsigned long> const *,struct boost::re_detail::regex_data<unsigned short,struct boost::regex_traits<unsigned short,class boost::w32_regex_traits<unsigned short> > > const &,bool)" (??$re_is_set_member@PBGGU?$regex_traits@GV?$w32_regex_traits@G@boost@@@boost@@K@re_detail@boost@@YAPBGPBG0PBU?$re_set_long@K@01@ABU?$regex_data@GU?$regex_traits@GV?$w32_regex_traits@G@boost@@@boost@@@01@_N@Z) usinstances.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) public: int __thiscall _STL::_Nondebug_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >::compare(unsigned short const *)const " (__imp_?compare@?$_Nondebug_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@QBEHPBG@Z) referenced in function "int __cdecl boost::re_detail::string_compare<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >(class _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> > const &,unsigned short const *)" (??$string_compare@GV?$char_traits@G@_STL@@V?$allocator@G@2@@re_detail@boost@@YAHABV?$basic_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@PBG@Z) usinstances.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) public: unsigned short const & __thiscall _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >::operator[](unsigned int)const " (__imp_??A?$basic_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@QBEABGI@Z) referenced in function "int __cdecl boost::re_detail::string_compare<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >(class _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> > const &,unsigned short const *)" (??$string_compare@GV?$char_traits@G@_STL@@V?$allocator@G@2@@re_detail@boost@@YAHABV?$basic_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@PBG@Z) usinstances.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) public: bool __thiscall _STL::_Nondebug_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >::empty(void)const " (__imp_?empty@?$_Nondebug_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@QBE_NXZ) referenced in function "int __cdecl boost::re_detail::string_compare<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >(class _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> > const &,unsigned short const *)" (??$string_compare@GV?$char_traits@G@_STL@@V?$allocator@G@2@@re_detail@boost@@YAHABV?$basic_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@PBG@Z) usinstances.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) public: __thiscall _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >(unsigned int,unsigned short,class _STL::allocator<unsigned short> const &)" (__imp_??0?$basic_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@QAE@IGABV?$allocator@G@1@@Z) referenced in function "public: class _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> > __thiscall boost::re_detail::w32_regex_traits_implementation<unsigned short>::transform_primary(unsigned short const *,unsigned short const *)const " (?transform_primary@?$w32_regex_traits_implementation@G@re_detail@boost@@QBE?AV?$basic_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@PBG0@Z) usinstances.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) public: class _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> > & __thiscall _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >::erase(unsigned int,unsigned int)" (__imp_?erase@?$basic_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@QAEAAV12@II@Z) referenced in function "public: class _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> > __thiscall boost::re_detail::w32_regex_traits_implementation<unsigned short>::transform_primary(unsigned short const *,unsigned short const *)const " (?transform_primary@?$w32_regex_traits_implementation@G@re_detail@boost@@QBE?AV?$basic_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@PBG0@Z) usinstances.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) public: class _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> > & __thiscall _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >::assign(class _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> > const &)" (__imp_?assign@?$basic_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@QAEAAV12@ABV12@@Z) referenced in function "public: class _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> > __thiscall boost::re_detail::w32_regex_traits_implementation<unsigned short>::transform_primary(unsigned short const *,unsigned short const *)const " (?transform_primary@?$w32_regex_traits_implementation@G@re_detail@boost@@QBE?AV?$basic_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@PBG0@Z) usinstances.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) public: class _STL::_Nondebug_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> > & __thiscall _STL::_Nondebug_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >::assign(unsigned short const *,unsigned short const *)" (__imp_?assign@?$_Nondebug_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@QAEAAV12@PBG0@Z) referenced in function "public: class _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> > & __thiscall _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >::assign<unsigned short const *>(unsigned short const *,unsigned short const *)" (??$assign@PBG@?$basic_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@QAEAAV01@PBG0@Z) usinstances.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) bool __cdecl _STL::operator<(class _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> > const &,class _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> > const &)" (__imp_??M_STL@@YA_NABV?$basic_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@0@0@Z) referenced in function "public: bool __thiscall _STL::less<class _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> > >::operator()(class _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> > const &,class _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> > const &)const " (??R?$less@V?$basic_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@@_STL@@QBE_NABV?$basic_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@1@0@Z) usinstances.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) bool __cdecl _STL::operator>(class _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> > const &,class _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> > const &)" (__imp_??O_STL@@YA_NABV?$basic_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@0@0@Z) referenced in function "public: struct boost::re_detail::re_syntax_base * __thiscall boost::re_detail::basic_regex_creator<unsigned short,struct boost::regex_traits<unsigned short,class boost::w32_regex_traits<unsigned short> > >::append_set(class boost::re_detail::basic_char_set<unsigned short,struct boost::regex_traits<unsigned short,class boost::w32_regex_traits<unsigned short> > > const &,struct boost::mpl::bool_<0> *)" (?append_set@?$basic_regex_creator@GU?$regex_traits@GV?$w32_regex_traits@G@boost@@@boost@@@re_detail@boost@@QAEPAUre_syntax_base@23@ABV?$basic_char_set@GU?$regex_traits@GV?$w32_regex_traits@G@boost@@@boost@@@23@PAU?$bool_@$0A@@mpl@3@@Z) usinstances.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) public: struct _STL::_DBG_iter<class _STL::_Nondebug_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >,struct _STL::_Nonconst_traits<unsigned short> > __thiscall _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >::insert(struct _STL::_DBG_iter<class _STL::_Nondebug_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >,struct _STL::_Nonconst_traits<unsigned short> >,unsigned short)" (__imp_?insert@?$basic_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@QAE?AU?$_DBG_iter@V?$_Nondebug_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@U?$_Nonconst_traits@G@2@@2@U32@G@Z) referenced in function "public: struct boost::re_detail::re_syntax_base * __thiscall boost::re_detail::basic_regex_creator<unsigned short,struct boost::regex_traits<unsigned short,class boost::w32_regex_traits<unsigned short> > >::append_set(class boost::re_detail::basic_char_set<unsigned short,struct boost::regex_traits<unsigned short,class boost::w32_regex_traits<unsigned short> > > const &,struct boost::mpl::bool_<0> *)" (?append_set@?$basic_regex_creator@GU?$regex_traits@GV?$w32_regex_traits@G@boost@@@boost@@@re_detail@boost@@QAEPAUre_syntax_base@23@ABV?$basic_char_set@GU?$regex_traits@GV?$w32_regex_traits@G@boost@@@boost@@@23@PAU?$bool_@$0A@@mpl@3@@Z) usinstances.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) public: struct _STL::_DBG_iter<class _STL::_Nondebug_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >,struct _STL::_Nonconst_traits<unsigned short> > __thiscall _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> >::end(void)" (__imp_?end@?$basic_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@QAE?AU?$_DBG_iter@V?$_Nondebug_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@_STL@@U?$_Nonconst_traits@G@2@@2@XZ) referenced in function "public: struct boost::re_detail::re_syntax_base * __thiscall boost::re_detail::basic_regex_creator<unsigned short,struct boost::regex_traits<unsigned short,class boost::w32_regex_traits<unsigned short> > >::append_set(class boost::re_detail::basic_char_set<unsigned short,struct boost::regex_traits<unsigned short,class boost::w32_regex_traits<unsigned short> > > const &,struct boost::mpl::bool_<0> *)" (?append_set@?$basic_regex_creator@GU?$regex_traits@GV?$w32_regex_traits@G@boost@@@boost@@@re_detail@boost@@QAEPAUre_syntax_base@23@ABV?$basic_char_set@GU?$regex_traits@GV?$w32_regex_traits@G@boost@@@boost@@@23@PAU?$bool_@$0A@@mpl@3@@Z) usinstances.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) bool __cdecl _STL::operator==(class _STL::basic_string<unsigned short,class _STL::char_traits<unsigned short>,class _STL::allocator<unsigned short> > const &,unsigned short const *)" (__imp_??8_STL@@YA_NABV?$basic_string@GV?$char_traits@G@_STL@@V?$allocator@G@2@@0@PBG@Z) referenced in function "unsigned int __cdecl boost::re_detail::find_sort_syntax<class boost::re_detail::w32_regex_traits_implementation<unsigned short>,unsigned short>(class boost::re_detail::w32_regex_traits_implementation<unsigned short> const *,unsigned short *)" (??$find_sort_syntax@V?$w32_regex_traits_implementation@G@re_detail@boost@@G@re_detail@boost@@YAIPBV?$w32_regex_traits_implementation@G@01@PAG@Z) bin\boost\libs\regex\build\boost_regex.dll\vc-7_1-stlport\debug\native-wchar_t-on\threading-multi\boost_regex-vc71-mt-gdp-1_33.dll : fatal error LNK1120: 34 unresolved externals "link" /nologo /INCREMENTAL:NO /DEBUG /DLL /subsystem:console /out:"bin\boost\libs\regex\build\boost_regex.dll\vc-7_1-stlport\debug\native-wchar_t-on\threading-multi\boost_regex-vc71-mt-gdp-1_33.dll" /IMPLIB:"bin\boost\libs\regex\build\boost_regex.dll\vc-7_1-stlport\debug\native-wchar_t-on\threading-multi\boost_regex-vc71-mt-gdp-1_33.lib" /LIBPATH:"c:\opt\icu\lib" /LIBPATH:"c:\opt\STLport-4.6.2\lib" /LIBPATH:"C:\Program Files\Microsoft Visual Studio .NET 2003\VC7\lib" "icuuc.lib" "icuin.lib" "stlport_vc71_stldebug.lib" @"bin\boost\libs\regex\build\boost_regex.dll\vc-7_1-stlport\debug\native-wchar_t-on\threading-multi\boost_regex-vc71-mt-gdp-1_33.CMD" ...failed vc-Link bin\boost\libs\regex\build\boost_regex.dll\vc-7_1-stlport\debug\native-wchar_t-on\threading-multi\boost_regex-vc71-mt-gdp-1_33.dll bin\boost\libs\regex\build\boost_regex.dll\vc-7_1-stlport\debug\native-wchar_t-on\threading-multi\boost_regex-vc71-mt-gdp-1_33.lib... ...skipped <@boost!lib>boost_regex-vc71-mt-gdp-1_33.dll for lack of <@boost!libs!regex!build\boost_regex.dll\vc-7_1-stlport\debug\native-wchar_t-on\threading-multi>boost_regex-vc71-mt-gdp-1_33.dll... ...skipped <@boost!lib>boost_regex-vc71-mt-gdp-1_33.lib for lack of <@boost!libs!regex!build\boost_regex.dll\vc-7_1-stlport\debug\native-wchar_t-on\threading-multi>boost_regex-vc71-mt-gdp-1_33.lib... The release dll file compiles error are the similar. ==================================================================================================== Second I try the stlport 5.0RC4(icu are recompiled with this version), I find only the dll files compiling fails. call "c:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\bin\vcvars32.bat" set TOOLS=vc-7_1-stlport set STLPORT_PATH=c:\opt set STLPORT_50_PATH=C:\opt\STLport set STLPORT_VERSION=5.0 set ICU_PATH=c:\opt\icu bjam "-sBUILD=debug release <runtime-link>dynamic <threading>multi <native-wchar_t>on" "-sICU_PATH=c:\opt\icu" --with-regex stage The error is : vc-Link bin\boost\libs\regex\build\boost_regex.dll\vc-7_1-stlport\debug\native-wchar_t-on\threading-multi\boost_regex-vc71-mt-gdp-1_33.dll bin\boost\libs\regex\build\boost_regex.dll\vc-7_1-stlport\debug\native-wchar_t-on\threading-multi\boost_regex-vc71-mt-gdp-1_33.lib LINK : fatal error LNK1181: cannot open input file 'stlport_vc71_stldebug.lib' vc-Link bin\boost\libs\regex\build\boost_regex.dll\vc-7_1-stlport\release\native-wchar_t-on\threading-multi\boost_regex-vc71-mt-p-1_33.dll bin\boost\libs\regex\build\boost_regex.dll\vc-7_1-stlport\release\native-wchar_t-on\threading-multi\boost_regex-vc71-mt-p-1_33.lib LINK : fatal error LNK1181: cannot open input file 'stlport_vc71.lib' But I find in stlport 5.0 the rule of library and dll file is changed. The files are : stlport_d50.dll, stlport_r50.dll, stlport_stld50.dll, stlport_d50.lib, stlport_r50.lib, stlport_stld50.lib, stlport_static_d50.lib, stlport_static_r50.lib, stlport_static_stld50.lib I also try copy stlport_d50.lib and stlport_r50.lib as stlport_vc71_stldebug.lib and stlport_vc71.lib, and the link is completed. So I am very surprise which tell the regex to link with stlport_vc71_stldebug.lib and stlport_vc71.lib, I think it may be the boost or bjam, not stlport. Since the stlport 5.0 will be released soon. I think it is a big bug.

2 5

Syntax question
by Stephen Gross 19 Aug '05

19 Aug '05

I'm trying to static assert the value of a sequence. I've got the syntax slightly wrong, but I can't quite figure it out. Here's what my code looks like: ========================== template<typename SEQ, int SIZE> void assertSeqSize() { BOOST_STATIC_ASSERT(( boost::equal_to<boost::mpl::size<SEQ>::type, boost::mpl::int_<SIZE> > )) && "You have attempted to invoke a functor with the incorrect number of Arguments."; } ========================== The compiler (gcc 3.3.1) tells me: ../../c++/include/functors/ArgList.h: In function `void SAGE::FUNCTORS::assertSeqSize()': ../../c++/include/functors/ArgList.h:46: error: parse error before `>' token ../../c++/include/functors/ArgList.h:46: error: template argument 1 is invalid ../../c++/include/functors/ArgList.h:46: error: parse error before `&&' token Can anyone tell me my mistake? Did I stick an extra '::type' where I didn't need one? Thanks, --Steve Stephen Gross Case Western School of Medicine Cleveland, OH "By Grabthar's hammer, by the sons of Worvan, you shall be avenged." - Dr. Lazarus

2 1

Segfault in Boost
by Jeff Lounsberry 19 Aug '05

19 Aug '05

I'm getting a segfault in Boost when I go to use mutexes. I built the Boost unit test for threads with the following: bjam "-sTOOLS=gcc" "-sBUILD debug <runtime-link>static <threading>multi" In Boost 1.32 there are errors with text_mutex_lib: root@unstable:~/scratch/boost_1_32_0/bin/boost/libs/thread/test/test_mutex_lib.test/gcc/debug/runtime-link-static/threading-multi> ./test_mutex_lib Running 6 test cases... Exception in "test_try_mutex": signal: memory access violation /root/scratch/boost_1_32_0/libs/test/build/../src/unit_test_suite.cpp(150): fatal error in "test_try_mutex": Testing aborted Exception in "test_recursive_mutex": signal: memory access violation /root/scratch/boost_1_32_0/libs/test/build/../src/unit_test_suite.cpp(150): fatal error in "test_recursive_mutex": Testing aborted Exception in "test_recursive_try_mutex": signal: memory access violation /root/scratch/boost_1_32_0/libs/test/build/../src/unit_test_suite.cpp(150): fatal error in "test_recursive_try_mutex": Testing aborted Exception in "test_recursive_timed_mutex": signal: memory access violation /root/scratch/boost_1_32_0/libs/test/build/../src/unit_test_suite.cpp(150): fatal error in "test_recursive_timed_mutex": Testing aborted *** errors detected in test suite "Boost.Threads: mutex test suite"; see standard output for details [---] In Boost 1.32 there are errors with test_xtime_lib: root@unstable:~/scratch/boost_1_32_0/bin/boost/libs/thread/test/test_xtime_lib.test/gcc/debug/runtime-link-static/threading-multi> ./test_xtime_lib Running 2 test cases... Exception in "test_xtime_cmp": signal: memory access violation /root/scratch/boost_1_32_0/libs/test/build/../src/unit_test_suite.cpp(150): fatal error in "test_xtime_cmp": Testing aborted Exception in "test_xtime_get": signal: memory access violation /root/scratch/boost_1_32_0/libs/test/build/../src/unit_test_suite.cpp(150): fatal error in "test_xtime_get": Testing aborted *** errors detected in test suite "Boost.Threads: xtime test suite"; see standard output for details Segmentation fault [---] In Boost 1.33 there are errors with test_mutex_lib: root@unstable:~/scratch/boost_1_33_0/bin/boost/libs/thread/test/test_mutex_lib.test/gcc/debug/runtime-link-static/threading-multi> ./test_mutex_lib Running 6 test cases... unknown location(0): fatal error in "test_try_mutex": signal: memory access violation *** errors detected in test suite "Boost.Threads: mutex test suite"; see standard output for details [--] In Boost 1.33 there are no errors with test_xtime_lib: root@unstable:~/scratch/boost_1_33_0/bin/boost/libs/thread/test/test_xtime_lib.test/gcc/debug/runtime-link-static/threading-multi> ./test_xtime_lib Running 2 test cases... *** No errors detected Well then, i'm thoroughly confused. It seems the unit test Boost has are making calls to libthreaddb.so (NPTL). Anyone have any ideas? I've reproduced this on 2 machines (opterons 246), 2 distros now. What really boggles me is that the one xtime test works on 1.33 but the mutex test doesn't. Simple mutex calls work fine however. Are these specific problems with the test or something deeper? I've seen no discussion on the mailing list.

3 2

program-options: Spaces in a value?
by Stephen W. Carson 19 Aug '05

19 Aug '05

What is the best way to specify spaces in a command line value with program_options. I tried putting quotes around the value and program_options couldn't deal with that as far as I could tell. Example: foo --input-file "C:\foo bar.txt" BTW, just saw the new design on the boost home page. Very nice! A great improvement in aeshetics and usability. -- Stephen W. Carson, Software Engineer DirXion Software in St. Louis, MO (636) 717-2367 The Boost Wiki: http://www.boost.org/wiki

2 1

The example error of boost 1.33 date_time
by 沈慧峰 19 Aug '05

19 Aug '05

"add_month" are not in date-time of boost 1.33. I have compiled date_time as the lib. The example are not in boost\libs\date_time\example, I use grep and can not find it. > The example of > "boost/doc/html/date_time/examples.html#date_time.examples.month_add" can > not be compiled. > I use the vc71+stlport 4.62, the command line is cl /MD /EHsc > /DBOOST_LIB_DIAGNOSTIC. > I also can not find this example code under the directory > "boost\libs\date_time\example\gregorian\". This example program is in cvs (http://tinyurl.com/9gnxq) Did you build the library first? This example uses one of the to_string functions. These functions depend on the compiled binary libray. I could provide more help if you post your error messages. Bart <P><HR></P>_______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

2 1

Bind operator== in standard algorithms
by Alexander Borghgraef 19 Aug '05

19 Aug '05

Ok, I've just discovered boost::bind, and it is a marvelous discovery :-) Now, I do seem to have a problem: the operator overloading for logical operators seems to work on its own, but not when I apply it within standard algorithms such as find_if. Still, the bind documentation states that this should be possible, and gives examples such as: std::remove_if( first, last, !bind( &X::visible, _1 ) ); std::find_if( first, last, bind( &X::name, _1 ) == "peter" ); If we look at some simple test code I wrote: int add3( int i ){ return i + 3; }; int main() { int x = 2; int y = 5; bind( add3, _1)(x) == y; // Compiles find_if( l.begin(), l.end(), bind<int>( equal_to<int>(), bind(add3, _1), y) ); // Compiles find_if( l.begin(), l.end(), bind(add3, _1) == y ); // Doesn't compile } From the last line I get the following error message: error: no match for 'operator==' in 'boost::bind [with R = int, B1 = int, A1 = boost::arg<1>](add3, (<unnamed>::_1, boost::arg<1>())) == y' I'm puzzled why the standalone bind expression containing == does compile, whereas the one inside find_if doesn't. Of course, I do have a functional equivalent I can work with in the first find_if line, but it does seem neat to be able to write more readable code, as in the examples. Anyone care to explain this to me? Ok, standard disclaimers: I use the g++ 3.4.4 compiler on Fedora, I did include all necessary boost:: and std:: namespace stuff in my code, but left it out in this post, and I have no clue whatsoever which version of boost I have installed ( Can I find it in the code somewhere? Otherwise I'll ask the sysadmin which version he installed when I see him.). -- Alex Borghgraef

4 4

Re: [Boost-users] thread safety of the mutex ctor
by Christopher Hunt 19 Aug '05

19 Aug '05

On 18/08/2005, at 8:04 AM, boost-users-request(a)lists.boost.org wrote: > On 8/17/05, Christopher Hunt <huntc(a)internode.on.net> wrote: >> On 18/08/2005, at 1:19 AM, boost-users-request(a)lists.boost.org wrote: >> >>> I envisage two threads accessing a function like this concurrently: >>> >>> template<typename T> >>> boost::shared_ptr<T> >>> my_func() >>> { >>> static boost::mutex m; >>> boost::mutex::scoped_lock l(m); >>> >>> static boost::shared_ptr<T> p(new T); >>> return p; >>> } >>> >>> and my worry is that both threads could attempt to do the static >>> initialisation of m concurrently. Is there protection against this? >>> Is it even possible to protect against this? >> >> The scope of m is actually outside of your function given that it is >> static. Thus it will be initialised outside of your function generally >> before any other threads get to start up. > > This does not sound right to me, so I whipped up a test case... on > HP-UX, given the code: Sorry, I should have looked at the problem more closely - you're right to be suspicious of course. Stroustrup is actually pretty clear on this too, "It will be initialized only the first time the thread of execution reaches its definition". Whoops - sorry for throwing you off. Using the Singleton Design Pattern, I have a static mutex in my class covering the static instance member. Given their static member nature, they get initialised during process startup. Again Stroustrup confirms this with, "A variable defined outside any function (that is, global, namespace, and *class static variables*) is initialized (constructed) before main() is invoked,...". In case it helps, here's something that I knocked together (and tested) using the boost library. The class implements the Singleton design pattern safely and is also more robust from an exception handling perspective (note: this is the first time I've used boost threads - I'm actually using another thread class library...): ***** #include <stdexcept> #include <boost/thread/mutex.hpp> // Modified Singleton class from Gamma et. al. Returns // a reference to the instance instead of a pointer // recognising the use of exceptions. Additionally, // the instance is guaranteed to be allocated in a // thread safe manner. class Singleton { public: static Singleton& Instance() throw(std::bad_alloc); protected: Singleton() throw(std::bad_alloc); private: static Singleton* mInstanceP; static boost::mutex mInstancePMutex; }; // Implementation using namespace boost; using namespace std; Singleton* Singleton::mInstanceP = 0; mutex Singleton::mInstancePMutex; Singleton& Singleton::Instance() throw(bad_alloc) { boost::mutex::scoped_lock theInstancePMutexLock(mInstancePMutex); if (mInstanceP == 0) mInstanceP = new Singleton(); return *mInstanceP; } Singleton::Singleton() throw(bad_alloc) {} int main (int argc, char * const argv[]) { try { Singleton& theSingleton = Singleton::Instance(); // Guaranteed thread safe. } catch (const bad_alloc&) {} return 0; } ***** 'hope that this is useful. Cheers, -C

1 0

[shared_ptr][1.33.0] Header includes troublesome win32 macros.
by Jason Kankiewicz 18 Aug '05

18 Aug '05

On win32 using VC7.1, the Windows macros 'CMYK' and 'RGB' are bleeding through the 'boost/shared_ptr.hpp' header file. These are my header file's includes up to and including the offending boost header: #include <algorithm> #include <functional> #include <iterator> #include <set> #include <stdexcept> #include <string> #include <utility> #include <vector> #include <boost/shared_ptr.hpp> #undef CMYK // I added this to make it compile. #undef RGB // I added this to make it compile. The declarations of my 'CMYK' and 'RGB' functions within this header compiled without error until I installed the 1.33.0 release of Boost. I had been using the CVS HEAD previously so the error must have been introduced during the week or two prior to release.

2 1

Iostreams library question
by Lisa Glendenning 18 Aug '05

18 Aug '05

Hello, I just recently began using the boost iostreams library, and I can't figure out a way to see if a file has been successfully opened. E.g., I would like to reproduce this behavior: std::ofstream file("filename"); if(!file) { // error opening file } Thanks, Lisa Glendenning

2 1

[serialization][1.33.0?] xml_iarchive leak
by Jeff Flinn 18 Aug '05

18 Aug '05

Robert, The following code leads to numerous leaks when lIn's contents are not an xml_archive. Any thoughts on the cause? try { std::ifstream lIn( lpszPathName ); if( lIn.good() ) { boost::archive::xml_iarchive ia( lIn ); } } catch( boost::archive::xml_archive_exception& aExc ) { std::string lErr = aExc.what(); } Thanks, Jeff Flinn

4 13

Range + fixed_string
by Martin 18 Aug '05

18 Aug '05

I have a project that uses the fixed_string library (which is still in the review que). This library worked fine with string_algo in boost 1.32 but not with boost 1.33. I traced the problem to be the following template <typename StringT> struct C { typedef range_result_iterator<StringT>::type range_iterator_type; typedef StringT::iterator iterator_type; BOOST_STATIC_ASSERT((is_same<range_iterator_type, iterator_type>::value)); int dummy; }; main() { C<std::string> a; // ok C<array<char, 5> > b; // ok C<const_string<> > c; // ok C<vector<char> > d; // ok C<fixed_string<10> > e; // static assert } Didn't find any obvious reason in any of the libraries involved. Is it a problem with the VC70 compiler? (Also noticed that the range library copied a lot from the string_algo library e.g. BOOST_STRING_TYPENAME and code layout. Doesn't matter but it confused me sometimes about what library source I was looking at)

2 1

[serialization] how for a particular object to get ID that is assigned by the lib
by Ivan 18 Aug '05

18 Aug '05

Hi, How could I determine the objectID of an object after it's been saved? I mean the ID that boost::serialization generates for each object at saving. In other words - I know the address of the object and I would like to get its ID after it's been saved. Does anyone know how to do that? Example follows at the end. Ivan #include <boost/archive/text_oarchive.hpp> class A { template<class Archive> void serialize(Archive & ar, const unsigned int version) { ar & i; } public: int i;| }; int main() { std::ofstream ofs("filename"); boost::archive::text_oarchive oa(ofs); A a; a.i = 1; oa & a; // need ID of *a* here !!! }

2 1

Re: [Boost-users] thread safety of the mutex ctor
by James E Taylor 18 Aug '05

18 Aug '05

Are you sure there are no guarantees for function scope statics? I think the following is thread safe: void my_func() { static pthread_mutex_t m = PTHREAD_MUTEX_INITIALIZER; pthread_mutex_lock(&m); // do something once pthread_mutex_unlock(&m); } because the C-style PTHREAD_MUTEX_INITIALIZER doesn't involve a constructor call: the static is initialised before _any_ threads are running. Also, constructors of global statics are not guaranteed to be single-threaded for the same reason you can't safely reference one static from the constructor of another (The Static Initialisation Order Fiasco); one constructor could create a thread that goes and uses an uninitialised static, whilst the main thread tries to initialise it. Do you know whether the mutex ctor is thread-safe? T. Scott Urban <scottu(a)apptechsys.com> wrote : > On Thu, 2005-08-18 at 06:22 +1000, Christopher Hunt wrote: > > On 18/08/2005, at 1:19 AM, boost-users-request(a)lists.boost.org > wrote: > > > > > I envisage two threads accessing a function like this > concurrently: > > > > > > template<typename T> > > > boost::shared_ptr<T> > > > my_func() > > > { > > > static boost::mutex m; > > > boost::mutex::scoped_lock l(m); > > > > > > static boost::shared_ptr<T> p(new T); > > > return p; > > > } > > > > > > and my worry is that both threads could attempt to do the static > > > initialisation of m concurrently. Is there protection against this? > > > > Is it even possible to protect against this? > > The scope of m is actually outside of your function given that it is > > static. Thus it will be initialised outside of your function generally > > before any other threads get to start up. > > The scope of m is in the function, not global, but it has static > duration. Unlike a global, m will only be constructed if my_func() is > ever called in your program. > > That should set of warning bells in you brain. > > I don't believe there are any guarantees about the thread safety of the > initialization of function scope statics. This applies not just to the > mutex class in question but any type. A particular compiler might make > this usage thread safe - or maybe only guarantee initialization of basic > types - but I don't know if it's covered by the pthread spec - and > that's not helpful anyway to boost users, in general. And of course, > the C++ standard is as usual silent on the matter. > > You can make the mutex global - anonymous namespace or whatever. Since > global initializations are single threaded, you trade the threading > problem for the loss of on-demand resource usage. > > Another way to deal with this kind of problem is to use a modified > singleton pattern, but to make that thread safe, you need another mutex > (unless you want to risk DCL), so seems kind of pointless for this > instance. > > > > > > -- > t. scott urban <scottu(a)apptechsys.com> -- James E Taylor james(a)onalog.net ___________________________________ NOCC, http://nocc.sourceforge.net

2 1

boost 1.32: read_write_mutex assertion
by Slawomir Lisznianski 18 Aug '05

18 Aug '05

Hello, I'm using Boost.Threads read/write mutex with the writer scheduling priority. Under heavy load, from many threads, I'm getting the following assertion: <..>/boost/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:190: void boost::deta il::thread::read_write_mutex_impl<Mutex>::do_write_lock() [with Mutex = boost::mutex]: Assertion `++loop_count == 1' failed. Abort (core dumped) The system is Linux kernel 2.4.21 (SMP) with 4 CPUs (Intel XEON MP) and g++ 3.2.3 20030502 (Red Hat Linux 3.2.3-42). Has anyone else experienced a similar problem? Thanks, Slawomir

2 2

Re: [Boost-users] Boost 1.33.0 released
by Randy Bowen 18 Aug '05

18 Aug '05

I recall talk some time ago that the current Boost.Tuple library was going to be replaced by a TR1 compliant version, possibly that from the Fusion package in Spirit. Is that still the plan for the future? > > Boost 1.33.0 > ------------ > > New Libraries > > * Iostreams Library: Framework for defining streams, stream > buffers and i/o filters, from Jonathan Turkanis. > * Functional/Hash Library: A TR1 hash function object that can be > extended to hash user defined types, from Daniel James. > * Parameter Library: Write functions that accept arguments by > name: especially useful when a function has more than one > argument with a useful default value, since named arguments can > be passed in any order. > * Pointer Container Library: Containers for storing heap-allocated > polymorphic objects to ease OO-programming, from Thorsten Ottosen. > * Wave: Standards conformant implementation of the mandated > C99/C++ preprocessor functionality packed behind an easy to use > iterator interface, from Hartmut Kaiser. >

2 1

Re: [Boost-users] thread safety of the mutex ctor
by James E Taylor 18 Aug '05

18 Aug '05

Thanks, that makes sense. Ben Hutchings <ben.hutchings(a)businesswebsoftware.com> wrote : > James E Taylor wrote: > > >I hope this isn't a stupid question, but.... > > > >Is the boost mutex constructor thread-safe? > > > > > Clearly it's unsafe for multiple threads to call a constructor on the > same block of memory concurrently. To answer the real question, dynamic > initialisation of local static variables is generally not thread-safe. > > >and my worry is that both threads could attempt to do the static > initialisation of m concurrently. Is there protection against this? Is it > even possible to protect against this? > > > >I've tried to use boost::call_once, which would give sufficient guarantees > but it's quite inflexible as nothing can be passed to or from the function > being called. > > > > > I don't see that there's any other way to do this using current C++ and > Boost. > > Ben. > > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > http://lists.boost.org/mailman/listinfo.cgi/boost-users -- James E Taylor james(a)onalog.net ___________________________________ NOCC, http://nocc.sourceforge.net

1 0

Problems Compiling boost
by gbonfim＠quality.com.br 18 Aug '05

18 Aug '05

I'm starting with boost library and have some problems and doubts. First, i'd like to know if i can compile boost only with bjam or there is other way. I'm trying to do that on linux, but without success. Anybody could explain me better how to use boost library in a project in c++ on linux that i have alredy created? Thanks for the help, Gustavo

3 2

Re: [Boost-users] [BULK] Re: [range] From 1.33.0 gives new warning vs 1.32
by Sohail Somani 18 Aug '05

18 Aug '05

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of > Thorsten Ottosen > Sent: Monday, August 15, 2005 11:17 AM > To: boost-users(a)lists.boost.org > Subject: [BULK] Re: [Boost-users] [range] From 1.33.0 gives > new warning vs 1.32 > Importance: Low > > > > "Kevin Wheatley" <hxpro(a)cinesite.co.uk> wrote in message > news:4300715B.ED49E94C@cinesite.co.uk... > > I had some code that with 1.32 compiled fine when compiled with > > warnings as errors, but now with 1.33 I get: > > > Compiled with gcc 3.2.3 under Linux, > > > > perhaps something like this is needed? > > > template< class Char > > > inline Char* str_end( Char* s ) > > { > > - return (Char*)str_end( s, s ); > > + return const_cast<Char*>(str_end( s, s )); > > what's the difference? A c-style cast is also a const-cast. You didn't just say that.

3 6

I find a error in the document of boost 1.33
by 沈慧峰 18 Aug '05

18 Aug '05

The example of "boost/doc/html/date_time/examples.html#date_time.examples.month_add" can not be compiled. I use the vc71+stlport 4.62, the command line is cl /MD /EHsc /DBOOST_LIB_DIAGNOSTIC. I also can not find this example code under the directory "boost\libs\date_time\example\gregorian\". The example code is : /* Simple program that uses the gregorian calendar to progress by exactly * one month, irregardless of how many days are in that month. * * This method can be used as an alternative to iterators */ #include "boost/date_time/gregorian/gregorian.hpp" #include <iostream> int main() { using namespace boost::gregorian; date d = day_clock::local_day(); add_month mf(1); date d2 = d + mf.get_offset(d); std::cout << "Today is: " << to_simple_string(d) << ".\n" << "One month from today will be: " << to_simple_string(d2) << std::endl; return 0; }

2 1

thread safety of the mutex ctor
by James E Taylor 18 Aug '05

18 Aug '05

I hope this isn't a stupid question, but.... Is the boost mutex constructor thread-safe? I am writing a singleton template and trying to avoid the static initialisation/destruction order fiasco. I envisage two threads accessing a function like this concurrently: template<typename T> boost::shared_ptr<T> my_func() { static boost::mutex m; boost::mutex::scoped_lock l(m); static boost::shared_ptr<T> p(new T); return p; } and my worry is that both threads could attempt to do the static initialisation of m concurrently. Is there protection against this? Is it even possible to protect against this? I've tried to use boost::call_once, which would give sufficient guarantees but it's quite inflexible as nothing can be passed to or from the function being called. I know that integral types (like a pthread_t) of static storage are initialised before main() and before constructors of statically allocated objects are called, which means there would be no problem using a pthread_t above. However, constructors of objects of static storage are called at a time when there could be multiple threads running. Am I worrying about nothing? Or is there a problem here? Thanks, James -- James E Taylor ___________________________________ NOCC, http://nocc.sourceforge.net

3 2

Re: [Boost-users] Boost-users Digest, Vol 637, Issue 1
by James E Taylor 18 Aug '05

18 Aug '05

Thanks, Pablo, I'll have a look at it. James > FYI Matthew Wilson gave a technique (in "Imperfect C++&quot for handling > this, > by turning the mutex initialization into an integer initialization (that > doesn't have a problem with [multiple] simultaneous threads entering the > function) > > It uses STLSoft's spin_mutex, and looks pretty much like what you have > already: > > <code> > #include <platformstl/spin_mutex.hpp> > #include <stlsoft/lock_scope.hpp> > using platformstl::spin_mutex; > using stlsoft::lock_scope; > > template<typename T> > boost::shared_ptr<T> > my_func() > { > // static boost::mutex m; > // boost::mutex::scoped_lock l(m); > static int spin_count = 0; // No race condition initializing an > int > spin_mutex mutex(&spin_count); // Build the mutex on top of the > static > int > lock_scope lock(mutex); > > static boost::shared_ptr<T> p(new T); > return p; > } > </code> > > This assumes, of course, you can (and are willing to) use STLSoft... > > > HTH, > Pablo ___________________________________ NOCC, http://nocc.sourceforge.net

1 0

Random access to sequences
by Stephen Gross 18 Aug '05

18 Aug '05

I read up on boost::mpl::at<...>. It's pretty cool, but I wanted to make it a little easier to use. I found it a little annoying to have to type out 'int_<...>' for the index number, so I created a struct to automate that feature: ========================== template<typename SEQ, int IDX> struct atIdx { typedef typename boost::mpl::at<SEQ, boost::mpl::int_<IDX> >::type type; }; ========================== With the struct above, you can do the following: ============================= typedef boost::mpl::vector<int, char, int> t; atIdx<t, 0>::type i; // This line is shorter than the one below: /* atIdx<t, boost::mpl::int_<0> >::type i; */ ============================= Is this feature already available in boost somewhere? If I've reinvented the wheel, I'll be happy to use an existing implementation... Thanks, --Steve Stephen Gross Case Western School of Medicine Cleveland, OH "By Grabthar's hammer, by the sons of Worvan, you shall be avenged." - Dr. Lazarus

2 1

Re: [Boost-users] thread safety of the mutex ctor
by Christopher Hunt 17 Aug '05

17 Aug '05

On 18/08/2005, at 1:19 AM, boost-users-request(a)lists.boost.org wrote: > I envisage two threads accessing a function like this concurrently: > > template<typename T> > boost::shared_ptr<T> > my_func() > { > static boost::mutex m; > boost::mutex::scoped_lock l(m); > > static boost::shared_ptr<T> p(new T); > return p; > } > > and my worry is that both threads could attempt to do the static > initialisation of m concurrently. Is there protection against this? > Is it even possible to protect against this? The scope of m is actually outside of your function given that it is static. Thus it will be initialised outside of your function generally before any other threads get to start up. Cheers, -C

3 2

Wave capabilities
by Foster Gareth 17 Aug '05

17 Aug '05

Hello list, I've been reading through the wave docs, it looks very impressive. I was wondering, is it possible to use Wave to extract all the macro/class/function definitions with their respective line numbers from a source file? I noticed the mention of include paths etc however, does this mean that just throwing random source files from a large source tree at Wave, with no regard for whether or not all the types in it will be defined, is going to result in it throwing exceptions? Thanks for any help. Cheers, Gaz ********************************************** * http://www.mozilla.org/products/firefox/ * **********************************************

2 1

[Signals] Boost.signals dll version crashes on OS X
by Chiedo Acholonu 17 Aug '05

17 Aug '05

I built the boost.signals library using bjam and am trying to use it in an xcode project named TestSignals. The project only consists of the signals library and the maximum.cpp example file (boost-root/libs/signals/example/maximum.cpp). The project builds but it crashes with a SIGBUS signal 10 when run. This only happens with the dynamic version of signals. I have defined BOOST_SIGNALS_DYN_LINK and built the library multithreaded, so I'm not sure what I'm doing wrong. I'm running OS X 10.4.2 with Xcode 2.1. Here is a snippet of the crash log (I can post the rest on request): Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000000 Thread 0 Crashed: 0 maximum.ob 0x0040c824 std::less<int>::operator()(int const&, int const&) const + 48 (stl_function.h:227) 1 maximum.ob 0x0040e0d8 boost::signals::detail::any_bridge_compare<std::less<int>, int>::operator()(boost::any const&, boost::any const&) const + 364 (named_slot_map.hpp:62) 2 maximum.ob 0x0040e148 boost::detail::function::function_obj_invoker2<boost::signals::detail::any_bridge_compare<std::less<int>, int>, bool, boost::any, boost::any>::invoke(boost::detail::function::any_pointer, boost::any, boost::any) + 76 (function_template.hpp:119) Any help would be much appreciated. Chiedo

1 0

boost:signals SIGSEV
by Massimiliano Liccardo 17 Aug '05

17 Aug '05

I opened the bug https://sourceforge.net/tracker/index.php?func=detail&aid=1262038&group_id=… concerning a segmentation fault using the boost:signals library. I attached the source i used. bye -- Massimiliano Liccardo (maX) <liccardo(a)acmesolutions.it> jid:coccolesto@jabber.org GnuPG public key available on wwwkeys.eu.pgp.net Key ID: D01F1CAD Key fingerprint: 992D 91B7 9682 9735 12C9 402D AD3F E4BB D01F 1CAD "la velocità induce all'oblio, la lentezza al ricordo"

1 0

[Regex] regex_match changed to match_any in 1.33?
by John Sichi 17 Aug '05

17 Aug '05

In boost/regex/v4/regex_match.hpp, a number of the overloads (the ones that don't take a result parameter) are now bitwise-oring in regex_constants::match_any. As a result, a sequence like boost::regexp exp("a(bc)?") char *value = "abcbc"; bool result = boost::regex_match(value, value + 5, exp); will now set result to true where it was previously false in 1.32. I fixed our code by passing in a dummy result object as an extra parameter. Was this change intentional? I couldn't find any documentation that mentions it. JVS

5 6

Re: [Boost-users] std::vector<std::string> pb
by Lana Abadie 17 Aug '05

17 Aug '05

Hi Joel, Thanks! It works now. Lana -----Original Message----- From: boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Joel de Guzman Sent: Tuesday, August 16, 2005 7:50 PM To: boost-users(a)lists.boost.org Subject: Re: [Boost-users] std::vector<std::string> pb Lana Abadie wrote: > > Hello, > Sorry to reiterate but if it's not the right forum to send this kind > of message, I would really appreciate that sb tells me where to post > it, because I'm stuck. > Thanks for helping > Lana > /*****************************/ Hi Lana, I'm sorry I wasn't able to reply as soon as possible. Yes, the proper forum is: C++-sig mailing list C++-sig(a)python.org http://mail.python.org/mailman/listinfo/c++-sig Anyway, here are some links that you might find useful: http://mail.python.org/pipermail/c++-sig/2004-March/007025.html http://mail.python.org/pipermail/c++-sig/2004-March/007028.html http://mail.python.org/pipermail/c++-sig/2004-March/007029.html Cheers, -- Joel de Guzman http://www.boost-consulting.com http://spirit.sf.net _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

1 0

[boost::program_options] bad_function_call and -g
by alexandre.ignjatovic＠insia.org 17 Aug '05

17 Aug '05

Hi, Does anyone know why i get a bad_function_call at the execution of this code (compiled without the '-g' option): namespace bpo = boost::program_options; _optDesc.add_options() ("version,v", "print version") ("help,h", "print this help message") ("config-file,f", bpo::value<std::string>(&_cfg)->default_value(_cfg), "specify configuration file") ("id,i", bpo::value<std::string>(&_id)->default_value(a_id), "specify server identifier"); bpo::variables_map vm; bpo::store(bpo::parse_command_line(argc, argv, _optDesc), vm); bpo::notify(vm); while it runs correctly with "-g" ? Compiler : gcc 343 (linux) or cc 57 (solaris) Boost version: 1.32.0 The exception seems to be trown by the notify function. By the way, it is quit hard to trace undebuggable compiled code (no -g, no way :)) Thanks in advance. -- Alexandre Ignjatovic

2 4

bjam - How to remove intermediate files?
by Matt Vogt 17 Aug '05

17 Aug '05

What is the equivalent of 'make clean' with bjam? 'bjam clean' seems to remove targets as well as intermediate files... I just want to remove objects in the build tree. Thanks, Matt

2 1

[Deprecation methods] (was [range] From 1.33.0 gives newwarningvs1.32)
by Sohail Somani 16 Aug '05

16 Aug '05

> maybe, but remember the code in question is deprecated and so > is likely to disappear in1.34. Speaking of deprecation, are there any compiler independent ways to indicate API deprecation ala Java? I investigated this a while back using compile time errors if a certain preprocessor directive was defined but it got hairy with virtual methods. Sohail

1 0

std::vector<std::string> pb
by Lana Abadie 16 Aug '05

16 Aug '05

Hello, Sorry to reiterate but if it's not the right forum to send this kind of message, I would really appreciate that sb tells me where to post it, because I'm stuck. Thanks for helping Lana /*****************************/ Hello, I am using boost for the first time. I have the following boost.cpp file: #include "../confDBAPIpython/test1.h" #include <boost/python.hpp> #include <boost/python/suite/indexing/vector_indexing_suite.hpp> #include <boost/python/module.hpp> #include <boost/python/def.hpp> #include <boost/python/implicit.hpp> using namespace boost::python; BOOST_PYTHON_MODULE(confDBAPIpython) { // Compile check only... class_<std::vector<int> >("IntVec") .def(vector_indexing_suite<std::vector<int> >()); class_<std::vector<std::string> >("StringVec") .def(vector_indexing_suite<std::vector<std::string> >()); def("DBConnexion",PyDBConnexion); def("DBDeconnexion",PyDBDeconnexion); def("GetDeviceTypeRow",PyGetDeviceTypeRow); def("GetDeviceRow_devicename",PyGetDeviceRow_devicename); def("GetDeviceRow_deviceid",PyGetDeviceRow_deviceid); def("GetDetailedConnectivityBetweenDevices",PyGetDetailedConnectivityBet weenDevices); def("GetConnectivityBetweenDevices",PyGetConnectivityBetweenDevices); } The two last fct returns vector<std::string>. When I try to use them in python, I have the following error message: list_str=libconfDBAPIpython.GetConnectivityBetweenDevices("TFC","THOR_00 ","ECAL_L1FE06_02_00"); print list_str[0]; Traceback (most recent call last): File "<stdin>", line 1, in ? TypeError: No Python class registered for C++ class std::string I don't understand why. I thought it will be handled by the vector_indexing_suite. I have no problem when a fcuntion returns a string or a vector<int> Thanks for helping Lana

2 1

Re: [Boost-users] [BULK] Re: [BULK] Re: [range] From 1.33.0 gives newwarningvs 1.32
by Sohail Somani 16 Aug '05

16 Aug '05

> no. I always use const_cast in my own code. so that is why I > believe it might be there for a reason. Speaking from my own experience, I've found that people use C-style casts because theyre lazy OR they don't understand what they want to do. The latter is really scary sometimes but its normal. Anyway, because I am dealing with a legacy C api, sometimes I have to const_cast to call these functions, but marking these with const_cast makes the casts easy to look for.

1 0

Re: [Boost-users] [BULK] Re: [BULK] Re: [range] From 1.33.0 gives newwarningvs1.32
by Sohail Somani 16 Aug '05

16 Aug '05

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of > Thorsten Ottosen > Sent: Tuesday, August 16, 2005 8:45 AM > To: boost-users(a)lists.boost.org > Subject: [BULK] Re: [Boost-users] [BULK] Re: [range] From > 1.33.0 gives newwarningvs1.32 > Importance: Low > Porting something to 10+ compilers is not always super easy. I agree, I have to only deal with the two of the most popular ones and even that's a headache sometimes. > And changing something that might break a regression is > always something I'm a bit reluctant to do. Yes, I've seen > compilers where a reinterpret_cast > + const_cast did not do what c-style cast would do. Don't ask me why. > + :-) You scare me.

1 0

Re: [Boost-users] [BULK] Re: [range] From 1.33.0 gives newwarningvs 1.32
by Sohail Somani 16 Aug '05

16 Aug '05

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of > David Abrahams > Sent: Monday, August 15, 2005 2:55 PM > To: boost-users(a)lists.boost.org > Subject: Re: [Boost-users] [BULK] Re: [range] From 1.33.0 > gives newwarningvs 1.32 > > Thorsten, the difference is in fragility over time with > maintenance. That's why the compiler issues the warning. Any > decent beginner's book on C++ will advise you to eschew all > casts, and prefer the new-style ones. Do you really need to > have the fundamentals of good > C++ programming practice explained? > > Incidentally, if you find that the proper C++ construct is > "less portable. somehow." you should use BOOST_WORKAROUND to > isolate the compiler for which it fails to work, if only so > that the reason for the workaround is documented. I thought the same thing but my name isnt Dave Abrahams and I don't have an important email address. Doh.

2 1

Re: [Boost-users] [serialization][1.33.0?] xml_iarchive leak
by Richard Jennings 16 Aug '05

16 Aug '05

> > > b) If I recall correctly, the borland version of scoped_ptr > fails when > > the type is incomplete - which makes it not useful for implementing > > the PIMPL idiom. > > it always fails unless the destructor is included first in > the cpp file IIRC. > Sadly this does not work on BCB even if the destructor is defined in the cpp file, which means that scoped_ptr can't be used for pimpl with this compiler. The details are here: http://lists.boost.org/Archives/boost/2001/12/21796.php You can of course use shared_ptr, but then the intention is less clear.

2 1

Re: [Boost-users] Maybe a problem with boost::object_pool?
by Labour, Matthieu (MLPRO SF) 16 Aug '05

16 Aug '05

Thank you for your answer Sorry about the wrong info RedHat: uname -a : Linux ejecxapeqdtmad01 2.4.21-32.0.1.ELsmp #1 SMP Tue May 17 17:52:23 EDT 2005 i686 athlon i386 GNU/Linux /etc/redhat-release: Red Hat Enterprise Linux AS release 3 (Taroon Update 5) GNU gcc version: gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-52) I'll try to update gcc and run the test again Did you try to run the test and and crash the program? Thank you -----Original Message----- From: boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Caleb Epstein Sent: Thursday, August 11, 2005 4:51 PM To: boost-users(a)lists.boost.org Subject: Re: [Boost-users] Maybe a problem with boost::object_pool? On 8/9/05, Labour, Matthieu (MLPRO SF) <matthieu_labour(a)ml.com> wrote: > I use Red Hat linux 3.2.3-47 Are you sure that is the version you're using? That doesn't look like a RedHat version number. What does "uname -a" tell you, and what is the contents of /etc/redhat-release? I have: Linux scsefpldcs0213 2.4.21-27.0.4.ELhugemem #1 SMP Sat Apr 16 18:22:53 EDT 2005 i686 i686 i386 GNU/Linux Red Hat Enterprise Linux AS release 3 (Taroon Update 4) > Gcc version 3.2.3 20030502 Perhaps the compiler is at fault here. Thats an old-ish version of GCC. I use 3.3.4. It could also be a buggy GNU libc or libstdc++ if you're on an older RedHat version. -- Caleb Epstein caleb dot epstein at gmail dot com _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users -------------------------------------------------------- If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ --------------------------------------------------------

2 1

Problem with Comeau 4.3.3 (compilation)
by pisalmon＠numericable.fr 16 Aug '05

16 Aug '05

Hi, I have some problem with boost compilation when I use Comeau 4.3.3 Compiler (with gcc 3.3.5 on Ubuntu Hoary) and bjam tools : The signal librairy cant compile. Do you known why ???

1 0

Re: [Boost-users] [range] From 1.33.0 gives new warning vs 1.32
by Peter Foley 16 Aug '05

16 Aug '05

Hi, "Thorsten Ottosen" <nesotto(a)cs.aau.dk> wrote in message news:<ddqm49$tjf$1(a)sea.gmane.org>... > > what's the difference? A c-style cast is also a const-cast. > > -Thorsten I notice nobody has pointed you in this direction but Scott Meyers in more Effective C++ discusses in Item 2 ("Prefer C++ style casts") why it is preferable to use the new C++ style casts. Key points: * Easier to understand why a cast is happening * You can explicitly say what you are casting to * It is much easier to search for exactly where you are casting in your code * More fine grained control I am not a fantastic programmer but I feel that I have learnt a lot from his books. Out of all the reference/text books that I have purchased I think these books have been the best. Peter.

1 0

Re: [Boost-users] [serialization]save/load objects to/from a block of memory?
by Jasper, Alexander 16 Aug '05

16 Aug '05

Hi! >> Li Lirong wrote: > > How can I save/load my c++ objects to/from a block of memory using > > Boost.Serialization? Can anyone give some sample code? > > You can simply stream into a std::stringstream: > > std::stringstream stream; > { > boost::text_oarchive oa(stream); > oa << my_data; > } > But don't do that with to much data. I tried that with a similar approach, but it didn't work. It is far better to serialize to a lot of 'small' (e.g. 64K) blocks rather a huge one (100MB) that needs, even worse, to be realloced once and again. This completely fragmented the address space in my app. Of course this only important, if you are dealing with bigger amounts of data. If you are interested I could send you my implementation of a stream buffer that uses fixed size blocks. I'm not completely satisfied with it, though. I still suffers from scalability problems. kind regards Alex

1 0

[range] From 1.33.0 gives new warning vs 1.32
by Kevin Wheatley 16 Aug '05

16 Aug '05

I had some code that with 1.32 compiled fine when compiled with warnings as errors, but now with 1.33 I get: cc1plus: warnings being treated as errors boost_1_33_0_gcc_3.2.3/include/boost-1_33/boost/range/detail/implementation_help.hpp: In function `Char* boost::range_detail::str_end(Char*) [with Char = char]': boost_1_33_0_gcc_3.2.3/include/boost-1_33/boost/range/end.hpp:96: instantiated from here boost_1_33_0_gcc_3.2.3/include/boost-1_33/boost/range/detail/implementation_help.hpp:57: warning: cast from `const char*' to `char*' discards qualifiers from pointer target type boost_1_33_0_gcc_3.2.3/include/boost-1_33/boost/range/detail/implementation_help.hpp: In function `Char* boost::range_detail::str_end(Char*) [with Char = wchar_t]': boost_1_33_0_gcc_3.2.3/include/boost-1_33/boost/range/end.hpp:101: instantiated from here boost_1_33_0_gcc_3.2.3/include/boost-1_33/boost/range/detail/implementation_help.hpp:57: warning: cast from `const wchar_t*' to `wchar_t*' discards qualifiers from pointer target type Compiled with gcc 3.2.3 under Linux, perhaps something like this is needed? Thanks Kevin --- boost_1_33_0/boost/range/detail/implementation_help.hpp 2005-05-05 13:58:51.000000000 +0100 +++ boost_1_33_0_gcc_3.2.3/include/boost-1_33/boost/range/detail/implementation_help.hpp 2005-08-15 11:33:59.000000000 +0100 @@ -54,7 +54,7 @@ template< class Char > inline Char* str_end( Char* s ) { - return (Char*)str_end( s, s ); + return const_cast<Char*>(str_end( s, s )); } template< class T, std::size_t sz > -- | Kevin Wheatley, Cinesite (Europe) Ltd | Nobody thinks this | | Senior Technology | My employer for certain | | And Network Systems Architect | Not even myself |

4 5

auto linking and 'system' layout
by Serge Skorokhodov 16 Aug '05

16 Aug '05

Hi, I attempted to use boost built with system layout (vc-7_1) to simplify deployment etc. Unfortunately, my code failed to link as the linker tried to link the date_time libraries with TOOLS and version marks (I'm not sure about other libraries as it was fatal enough:). Is this a known limitation of auto linking? Is there a workaround? I haven't search the documentation real thoroughly but no hints of how to turn auto linking off...:( TIA -- Serge

3 7

Re: [Boost-users] [BULK] Re: [BULK] Re: [range] From 1.33.0 gives new warningvs 1.32
by Sohail Somani 15 Aug '05

15 Aug '05

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of > Thorsten Ottosen > Sent: Monday, August 15, 2005 2:38 PM > To: boost-users(a)lists.boost.org > Subject: [BULK] Re: [Boost-users] [BULK] Re: [range] From > 1.33.0 gives new warningvs 1.32 > Importance: Low > > > > > > perhaps something like this is needed? > > > > > > > template< class Char > > > > > inline Char* str_end( Char* s ) > > > > { > > > > - return (Char*)str_end( s, s ); > > > > + return const_cast<Char*>(str_end( s, s )); > > > > > > what's the difference? A c-style cast is also a const-cast. > > > > You didn't just say that. > > Apparently I did. > > What's the difference in the generated object code? A small percentage of people read object code on a regular basis. I tend to read the source more.

1 0

[serialization]save/load objects to/from a block of memory?
by Li Lirong 15 Aug '05

15 Aug '05

Hi, How can I save/load my c++ objects to/from a block of memory using Boost.Serialization? Can anyone give some sample code? Thanks, Lirong

2 1

Troubles with Boost.Log
by martin f krafft 15 Aug '05

15 Aug '05

Dear all, I have been spending the last two days trying to get John Torjo's logging library[0] working, but I am failing even though I can already see the goal[1]. Unfortunately, John seems to be on vacation or is otherwise occupied so as to not find time to answer my emails. Thus I turn to you... I have two problems right now, one small and one rather large one. The small one may well be my own confusion. Like most Boost libraries, Boost.Jam turns Boost.Log into eight different libraries: the permutations of release or debug, threade or not, and static or shared. For my first tests, I chose the single-threaded, static, release library. However, even the simplest programme segfaults in the weirdest places until I tell the linker to also link in libpthread (or Boost.Thread). What gives? Why does a single-threaded library need pthreads? The larger problem is a heisenproblem, that is I cannot pin it down, which is largely a problem due to libpthread mucking about with gdb in a way I can't seem to control. In a nutshell though, log messages sometimes get written twice, sometimes not at all, and all this without any threads or caching. So once I figured out how to make it work without pthreads, I'll be back with more. Any hints? 0. http://www.torjo.com/code/logging.zip 1. http://lists.debian.org/debian-devel/2005/08/msg00768.html -- martin; (greetings from the heart of the sun.) \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck invalid/expired pgp (sub)keys? use subkeys.pgp.net as keyserver! spamtraps: madduck.bogus(a)madduck.net "a fundamentalist is someone who hates sin more than he loves virtue." -- john h. schaar

1 0

boost::xtime
by Luca Zappella 15 Aug '05

15 Aug '05

Hi all, I would like to use boost mutex with TimedLock concept but I ran into the boost::xtime type. The problem is that I can not understand the second parameter of the method: int xtime_get(xtime*, int) In the doc I can not find anything, can someone help me? Thanks a lot, Luca

2 1

Re: [Boost-users] Problems: Building Boost with VC7 and STLport4.6.2
by Jasper, Alexander 15 Aug '05

15 Aug '05

Hi! If you are using VC7 rather VC 7.1 you of course use -sTOOLS=vc-7-stlport instead of -sTOOLS=vc-7_1-stlport. But VC7 is crap. If it is possible I strongly recommend you to upgrade to 7.1 which really works a lot of better than any release before. Also make sure you do a clean rebuild to prevent old compiler switches being stored in the precompiled header files. Boost further requires you to enable the debug mode of stl-port, if I'm not mistakes. Adding the following to stl-user-config.h solved things for me. #ifdef NDEBUG #undef _STLP_DEBUG #else #define _STLP_DEBUG 1 #endif BTW. STLPort 4.6.2 does not work well in conjunction with boost.serialize. A bug in the ostream::write method prevents it from handling writing 0 bytes correctly. Unfortunately the serializer writes 0 bytes in case of empty strings for instance. kind regards Alex > > Thanks a lot for your reply! I tried your method and it > works! All the compiler errors disappeared. I think the > important thing is to turn the feature "stlport-iostreams" on. > But the linker still asks me for something like > "stlport_vc6.lib". I'm using vc7 now. And I built STLport > 4.6.2 also with vc7. But the linker still asks me for > something related to vc6. Does any one know the possible causes? > > > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > http://lists.boost.org/mailman/listinfo.cgi/boost-users >

1 0

Re: [Boost-users] Problems: Building Boost with VC7 and STLport 4.6.2
by Jasper, Alexander 15 Aug '05

15 Aug '05

Hi! I had the same problem a few weeks ago. You've got to use the following command line. For debug libs build\bjam.exe -sTOOLS=vc-7_1-stlport "-sBUILD=<define>BOOST_NO_STD_WSTRING" "-sSTLPORT_4.6.2_PATH=D:\Alexander...." "-sstlport-iostreams=on" --with-date_time stage You need to build release libs with an extra step: build\bjam.exe -sTOOLS=vc-7_1-stlport "-sBUILD=release <define>BOOST_NO_STD_WSTRING" "-sSTLPORT_4.6.2_PATH=D:\Alexander...." "-sstlport-iostreams=on" --with-date_time stage This informations is based to 1.32, though. But I think it applies to 1.33 as well. hope this helps Alex > -----Ursprüngliche Nachricht----- > Von: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org]Im Auftrag von Hao Song > Gesendet: Sonntag, 14. August 2005 17:33 > An: boost-users(a)lists.boost.org > Betreff: [Boost-users] Problems: Building Boost with VC7 and STLport > 4.6.2 > > > Hi, > I tried to build Boost with VC7 and STLport 4.6.2, but failed to > compile some source files of Boost.date_time. Error messages are like: > > vc-C++ > E:\CppLibs\boost_1_33_0\temp\bin\boost\libs\date_time\build\bo > ost_date_time.dll\vc7-stlport\release\threading-multi\greg_month.obj > greg_month.cpp > E:\CppLibs\STLport-4.6.2\stlport\stl\_iterator_base.h(98) > : error C2825: > ¡°_Iterator::iterator_category¡±£ºcan not form a qualified name > > E:\CppLibs\boost_1_33_0\boost\date_time\date_parsing.hpp(270) : see > reference to class template instantiation > '_STL::iterator_traits<_Iterator>' > being compiled > with > [ > > _Iterator=_STL::basic_string<char,_STL::char_traits<char>,_STL > ::allocator<char>>::iterator > ] > > E:\CppLibs\boost_1_33_0\boost\date_time\gregorian\parsers.hpp(79) : > see reference to function template instantiation > 'boost::date_time::period<point_rep,duration_rep> > boost::date_time::from_simple_string_type<boost::gregorian::da > te,char>(const > _STL::basic_string<_CharT,_Traits,_Alloc> &)' being compiled > with > [ > point_rep=boost::gregorian::date, > duration_rep=boost::gregorian::date_duration, > _CharT=char, > _Traits=_STL::char_traits<char>, > _Alloc=_STL::allocator<char> > ] > E:\CppLibs\STLport-4.6.2\stlport\stl\_iterator_base.h(98) : > error C2039: > 'iterator_category' : is not a member of 'operator "global > namespace" ' > > And bjam failed to build DLLs > > vc-Link > E:\CppLibs\boost_1_33_0\temp\bin\boost\libs\date_time\build\bo > ost_date_time.dll\vc7-stlport\debug\threading-multi\boost_date > _time-vc7-mt-gdp-1_33.dll > E:\CppLibs\boost_1_33_0\temp\bin\boost\libs\date_time\build\bo > ost_date_time.dll\vc7-stlport\debug\threading-multi\boost_date > _time-vc7-mt-gdp-1_33.lib > LINK : fatal error LNK1181: cannot open input > file¡°stlport_vc6_stldebug.lib¡± > > > > It seems that auto-linking doesn't function properly. but I > can't see why. > any idea about these? Thanks in advance! > > > >

2 1