May 2009 - Boost-users - lists.boost.org

Re: [Boost-users] CMake Problems with boost 1.39
by Tan, Tom (Shanghai) 08 May '09

08 May '09

>> - The generated boost.test libs have an additional "-s" to the file >> names, ex. libboost_unit_test_framework-vc90-mt-1_39-s.lib, instead of >> libboost_unit_test_framework-vc90-mt-1_39.lib. This will cause a linking >> error while using boost.test. this does noto happen to the bjamed >> results. >> >.-s means that the library links to the static C++ runtime. The issue is, -s is appended to the end of the file name to all .lib files, even for those statically linked files that already have 's' in the middle. Ex. libboost_unit_test_framework-vc90-mt-s-1_39-s.lib, rather than libboost_unit_test_framework-vc90-mt-s-1_39.lib

1 0

Why is _internal_weak_this public in enable_shared_from_this?
by Joseph Garvin 07 May '09

07 May '09

I can see why you might want to make it protected and have it friend the shared_ptr template (because it does the initialization of _internal_weak_this I think), but I don't see any obvious reason for it to be public. Can anyone explain? You can see the relevant code here: http://www.boost.org/doc/libs/1_38_0/boost/enable_shared_from_this.hpp

2 1

[Boost] Boost 1.39: libdir installation path problem
by Marco Guazzone 07 May '09

07 May '09

Hi, I'm installing Boost 1.39 on Fedora 10 64bit (gcc 4.3.2) with the following command: $ ./bootstrip.sh --prefix=/home/marco/sys $ ./bjam install The installation process showed a lot of error like this: --- [error_snip] --- common.copy /lib/libboost_math_tr1f-gcc43-mt-1_39.so.1.39.0 cp: cannot create regular file `/lib/libboost_math_tr1f-gcc43-mt-1_39.so.1.39.0': Permission denied cp "bin.v2/libs/math/build/gcc-4.3.2/release/threading-multi/libboost_math_tr1f-gcc43-mt-1_39.so.1.39.0" "/lib/libboost_math_tr1f-gcc43-mt-1_39.so.1.39.0" ...failed common.copy /lib/libboost_math_tr1f-gcc43-mt-1_39.so.1.39.0... --- [/error_snip] --- In effect it seems that the script "boostrap.sh" did not correctly write the "libdir" configuration in the JAM project config file (at least as expected from what is said in the "boostraip.sh --help" message, which claims that "libdir" defaults to "EPREFIX/lib" which in turns defaults to "PREFIX/lib"). Here below is the generated "project-config.jam" file: --- [snip] --- # Boost.Build Configuration # Automatically generated by bootstrap.sh import option ; import feature ; # Compiler configuration. This definition will be used unless # you already have defined some toolsets in your user-config.jam # file. if ! gcc in [ feature.values <toolset> ] { using gcc ; } project : default-build <toolset>gcc ; # Python configuration using python : 2.5 : /usr ; # List of --with-<library> and --without-<library> # options. If left empty, all libraries will be built. # Options specified on the command line completely # override this variable. libraries = ; # These settings are equivivalent to corresponding command-line # options. option.set prefix : /home/marco/Sys ; option.set exec-prefix : /home/marco/Sys ; option.set libdir : /lib ; option.set includedir : /home/marco/Sys/include ; --- [/snip] --- To solve, I have to explicitly force the lib path with "--libdir=/home/marco/Sys/lib". Ciao, -- Marco

4 5

BGL - graph_viz
by liquid 07 May '09

07 May '09

How to use label_writer (graph_viz) with bundled properties? Regards liquid

1 0

[bind] performance implications?
by Dominique Devienne 07 May '09

07 May '09

Probably a silly question, but has anyone performed benchmarks on using a std::for_each(begin, end, bind(&C::f, _1)); compared to the hand written loop? Under the debugger I see bind adds a 4 or 5 stack frames between the for_each frame and the C::f frame, so I'm wondering if there is any overhead in these? I could bench it for myself on my everyday compiler for my one task, but surely this was considered and is documented somewhere, much more extensively I'll ever can, no? Some boost libraries discuss performance, but I didn't such a section in the Boost.Bind doco. Thanks for pointers or insights, --DD

2 1

multi_array warning with vs2005
by Hicham Mouline 07 May '09

07 May '09

Hello, I get these warnings : c:\program files\boost\boost_1_39_0\boost\multi_array.hpp(477) : warning C4996: 'std::uninitialized_fill_n': Function call with parameters that may be unsafe - this call relies on the caller to check that the passed values are correct. To disable this warning, use -D_SCL_SECURE_NO_WARNINGS. See documentation on how to use Visual C++ 'Checked Iterators' c:\program files\boost\boost_1_38_0\boost\multi_array\extent_gen.hpp(49) : warning C4996: 'std::copy': Function call with parameters that may be unsafe - this call relies on the caller to check that the passed values are correct. To disable this warning, use -D_SCL_SECURE_NO_WARNINGS. See documentation on how to use Visual C++ 'Checked Iterators' 1>c:\program files\boost\boost_1_38_0\boost\multi_array\multi_array_ref.hpp(374) : warning C4996: 'std::transform': Function call with parameters that may be unsafe - this call relies on the caller to check that the passed values are correct. To disable this warning, use -D_SCL_SECURE_NO_WARNINGS. See documentation on how to use Visual C++ 'Checked Iterators' 1>c:\program files\boost\boost_1_38_0\boost\multi_array\multi_array_ref.hpp(380) : warning C4996: 'std::transform': Function call with parameters that may be unsafe - this call relies on the caller to check that the passed values are correct. To disable this warning, use -D_SCL_SECURE_NO_WARNINGS. See documentation on how to use Visual C++ 'Checked Iterators' Ditto for boost_1_38_0 Am I supposed to disable the warning explicitly in my user code? Or should the warning disable be pushed/pop in boost multi_array? Rds,

4 5

Re: [Boost-users] multi_array warning with vs2005
by John Dlugosz 07 May '09

07 May '09

> Date: Thu, 7 May 2009 12:42:09 +0100 > From: "Hicham Mouline" <hicham(a)mouline.org> > Subject: [Boost-users] multi_array warning with vs2005 > To: <boost-users(a)lists.boost.org> > Message-ID: <002701c9cf08$dbefe5b0$93cfb110$@org> > Content-Type: text/plain; charset="us-ascii" > > Hello, > > I get these warnings : ... > Am I supposed to disable the warning explicitly in my user code? Or > should > the warning disable be pushed/pop in boost multi_array? > The warnings are warning against using features that are in fact standard, in favor of using something that may be non-standard but more robust against misuse and possibly slower. So it is appropriate to disable them on code that you are not maintaining, but are using from somewhere else. --John (sorry about the footer; it is not my idea) TradeStation Group, Inc. is a publicly-traded holding company (NASDAQ GS: TRAD) of three operating subsidiaries, TradeStation Securities, Inc. (Member NYSE, FINRA, SIPC and NFA), TradeStation Technologies, Inc., a trading software and subscription company, and TradeStation Europe Limited, a United Kingdom, FSA-authorized introducing brokerage firm. None of these companies provides trading or investment advice, recommendations or endorsements of any kind. The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.

1 0

boost.regex and perl expressions
by Dmitriy Lyfar 07 May '09

07 May '09

Hello, I'm trying to port my old regex code from pcre to boost.regex. There is a sample: void print_captures(const std::string& regx, const std::string& text) { boost::regex e(regx, boost::regex::perl); boost::smatch what; std::cout << "Expression: \"" << regx << "\"\n"; std::cout << "Text: \"" << text << "\"\n"; if(boost::regex_search(text, what, e, boost::match_extra)) { unsigned i, j; for(i = 0; i < what.size(); ++i) std::cout << " $" << i << " = \"" << what[i] << "\"\n"; } else { std::cout << "** No Match found **\n"; } } int main(int , char* []) { print_captures("http:\\/\\/.*\\.(.*\\.cn)", "\n\nhttp:// www.sc500.cn/hi/mom! \ \n test http:// rdfhr.zeyulariy.cn \ \n test http:// adtgr.zeytlariy.cn \n \ http://super.test.com"); return 0; } boost::regex output is: $0 = "http://www.sc500.cn/hi/mom! test http:// rdfhr.zeyulariy.cn test http:// adtgr.zeytlariy.cn" $1 = "zeytlariy.cn" Whereas where I'm using pcre I got following substrings (except full match): sc500.cn zeytlariy.cn zeyulariy.cn which is expected. So I'm confused about how perl expressions are worked. How can I get the same results using boost instead of pcre? Thank you.

1 0

[1.38.0][Serialization] [SunOS] Build ok but crashes when runing
by Jo anneChiang 07 May '09

07 May '09

The following is my configuration: 1. uname -a : SunOs xxx 5.10 Generic_127127-11 sun4u sparc SUNW,Sun-Fire-V215 2. user-config.jam: using sun : 5.10 : my-path-to-sunwspro-CC : <stdlib>sun-stlport <cxxflags>"-library=stlport4 -xtartget=ultra2 -xarch=v9" <linkflags>"=library=stlport4 -xtarget=ultra2 -xarch=v9" 3. running : bjam --with-serialization OK and the static library can be sucessfully built. However when it linked to my program and performs serialization, a segmentation fault occurs. Actually, I also found many among the bundled unit-tests are crashed as well, so supposedly the root cause is not my program logic. (the tests result in 3 kinds of crashes: stream error, segmentation fault and Illegal Instruction) So I'd like to consult if any of you have successfully pass all the unit-tests of boost.serialization under Sun studio CC with stlport4 ? Is there any glue or exprerience that can be provided here ? Or it tends to be a bug ? Thanks much, /maverick _______________________________________ ��ӭʹ�ó��Ż�� http://cn.mail.yahoo.com

1 0

[iostreams] why doesn't file_sink flush?
by Andrew Schweitzer 07 May '09

07 May '09

I'm trying to chain debugging logs together with a filtering_ostream. I've discovered that I need to call flush() on the filtering_ostream to get characters to appear in console in a timely fashion. This flush() call doesn't causes the file to be flushed. After some digging, I've discovered that the boost::iostreams::file_sink doesn't have the flushable_tag (or implement flush). std::fstream does have a flush function, and if I use it directly (not chained into a filtering_ostream), the flush call works as you might expect. So what is the appropriate way of implementing this? Chaining multiple logs together seems like a great way to use iostreams library. And out of curiosity, why doesn't file_sink implement flushable_tag? Here is the code I was using: #include <boost/iostreams/stream.hpp> #include <boost/iostreams/device/file.hpp> #include <boost/iostreams/stream.hpp> #include <boost/iostreams/tee.hpp> #include <boost/iostreams/filtering_stream.hpp> #include <boost/iostreams/categories.hpp> #include <boost/iostreams/concepts.hpp> #include <boost/thread.hpp> #include <boost/thread/xtime.hpp> #include <iostream> int main(int argc, char** argv) { using namespace std; using namespace boost; using namespace boost::iostreams; filtering_ostream fo; file_sink fsink("out.txt"); tee_filter<file_sink> tee_fsink(fsink); fo.push(tee_fsink); fo.push(cout); int i = 0; while(true) { fo << i << " "; //without this, I don't see "one print / second" //with it, I only see them on cout, but not in out.txt. fo.flush(); i++; boost::xtime xt; boost::xtime_get(&xt, boost::TIME_UTC); xt.sec += 1; boost::thread::sleep(xt); } return 0; } tx Andy

3 7