- Boost - lists.boost.org

[Bug Sprint] Anyone familiar with the utility library want to try bug #2285?
by Marshall Clow 07 Jun '09

07 Jun '09

Writing some docs for "unwrap_ref". https://svn.boost.org/trac/boost/ticket/2585 -- -- Marshall Marshall Clow Idio Software <mailto:marshall@idio.com> It is by caffeine alone I set my mind in motion. It is by the beans of Java that thoughts acquire speed, the hands acquire shaking, the shaking becomes a warning. It is by caffeine alone I set my mind in motion.

4 7

[function] -fno-exceptions
by Vladimir Prus 07 Jun '09

07 Jun '09

There's a bug report that function library fails to compile with -fno-exceptions, with a patch attached: https://svn.boost.org/trac/boost/ticket/2900 The patch seems pretty safe -- any objections if I apply it? I primarily care because there is a similar bug report against program_options, which I can't fix until function is similarly modified. Of course, there's still the approach to declare that we don't care about -fno-exceptions at all. - Volodya

2 1

Bug Sprint Report for Friday, June 5th
by Marshall Clow 07 Jun '09

07 Jun '09

The boost bug sprint started Friday, May 29th, and runs through Sunday June 7th. Today is the last day! Can we get under 700 open tickets? Status <https://svn.boost.org/trac/boost/report/1> 7:00 AM PDT 5/29: 797 open tickets. 7:45 AM PDT 5/30: 772 open tickets. 6:00 AM PDT 5/31: 761 open tickets. 6:00 AM PDT 6/2: 747 open tickets. 6:00 AM PDT 6/3: 748 open tickets. 6:00 AM PDT 6/4: 739 open tickets. 8:00 AM PDT 6/5: 730 open tickets. 7:00 AM PDT 6/6: 719 open tickets. 7:00 AM PDT 6/7: 706 open tickets. Activity: 5/29: 6 new tickets, 77 modifications, 25 tickets closed 5/30: 2 new tickets, 42 modifications, 17 tickets closed 5/31: 2 new tickets, 27 modifications, 8 tickets closed 6/1: 2 new tickets, 42 modifications, 17 tickets closed 6/2: 5 new tickets, 18 modifications, 5 tickets closed. 6/3: 4 new tickets, 19 modifications, 2 tickets closed. 6/4: 3 new tickets, 42 modifications, 24 tickets closed. 6/5: 3 new tickets, 35 modifications, 8 tickets closed. 6/6: 4 new tickets, 61 modifications, 29 tickets closed. [ Numbers may not add up because I am counting via two different methods, using data that is time-stamped in two different time zones. Also, tickets can be closed and reopened. ] What can you do? See <https://svn.boost.org/trac/boost/wiki/BugSprintJune2009> for details. I've added four new reports to the trac: Open ticket count by owner: <https://svn.boost.org/trac/boost/report/18> Open ticket count by component: <https://svn.boost.org/trac/boost/report/19> Open ticket count by ticket type: <https://svn.boost.org/trac/boost/report/20> Open ticket count by milestone: <https://svn.boost.org/trac/boost/report/21> There's been a lot of discussion on the list about tickets; and there are about a dozen patches that have been tested and are ready to be applied. If you're looking to help, you can look at some of the older bugs, say, the ones for Boost 1.36, and determine if they still apply. If they do, note that in the ticket. There are 42 tickets that are still open that are marked as "to be fixed in Boost 1.36" See <https://svn.boost.org/trac/boost/report/3> for a list of open tickets by milestone. --------- Sign-up sheet -------- The following people have committed to participate in the bug sprint. Please add you name here, along with what you can do. 1) Marshall Clow (coordination, Mac OS X characterization) 2) Beman Dawes (filesystem, system, timer) 3) Doug Gregor (function, graph, logic, mpi, numeric, property_map, signals) 4) "joel falcou" <joel.falcou(a)u-psud.fr> ( linux gcc testing/VC 2008 testing, patching) 5) Michael Caisse <boost(a)objectmodelingdesigns.com> (bug fixing) 6) Jeremiah Willcock <jewillco(a)osl.iu.edu> (will test and commit graph patches) 7) David Abrahams (iterator, python) 8) Sohail Somani (patches for g++ 4.2.4) 9) Steven Watanabe <watanabesj(a)gmail.com> (bug fixes, como) 10) vicente.botet" <vicente.botet(a)wanadoo.fr> 11) Stjepan Rajko <stjepan.rajko(a)gmail.com> (fusion) 12) Daniel Wallin (parameter, ...) -- -- Marshall Marshall Clow Idio Software <mailto:marshall@idio.com> It is by caffeine alone I set my mind in motion. It is by the beans of Java that thoughts acquire speed, the hands acquire shaking, the shaking becomes a warning. It is by caffeine alone I set my mind in motion.

1 0

[website] Tracking for Boost.Build docs
by Vladimir Prus 07 Jun '09

07 Jun '09

During the last release cycle some concerns were raised about Boost.Build index.html containing Google Analytics tracking code in the release tarballs. See: http://article.gmane.org/gmane.comp.lib.boost.devel/188808 That code was removed, but it had the negative effect that I no longer can see access statistics for the live website -- specifically, for http://beta.boost.org/boost-build2/index.html Is there any way to make the website dynamically add the necessary code? I have modified doc/display_build.php to do that for the generated docs, but I cannot find any similar hook that would handle top-level index.html. Thanks in advance, Volodya

3 2

Boost.logging bugs
by Dmitriy Lyfar 06 Jun '09

06 Jun '09

Hello, We are using boost.logging library in our project. We prefered that library because of header-only structure and it looks great. But recently I have found some two bugs. First of them its crash while output in syslog. I found that template<class msg_type> void operator()(const msg_type & msg) const { syslog( LOG_INFO, msg.c_str() ); } looks incorrect, because second argument is format string, so next line lead boost.logging to crash: amazon.co.uk%2fgp%2f%26nbsp%3b%2fref%3dpe_15031_15751501_pe_47%2f%26nbsp%3b (I need output some html parts in syslog like debug info). So I replaced code above with: template<class msg_type> void operator()(const msg_type & msg) const { syslog( LOG_INFO, "%s", msg.c_str() ); } Which works correct, but it seems not general solution. What do you think? And the second one is compiling under gcc 3.4.6 issue: ../3rdparty/boost/boost_1_37_0/boost/logging/format/destination/syslog.hpp: In member function `void boost::logging::destination::syslog_no_levels_t<convert_dest>::operator()(const msg_type&) const [with msg_type = std::basic_string<char, std::char_traits<char>, std::allocator<char> >, convert_dest = boost::logging::destination::do_convert_destination]': ../3rdparty/boost/boost_1_37_0/boost/logging/detail/manipulator.hpp:571: instantiated from `void boost::logging::manipulator::detail::generic_holder<generic_type, manipulator_base>::operator()(typename manipulator_base::param) const [with generic_type = boost::logging::destination::syslog_no_levels_t<boost::logging::destination::do_convert_destination>, manipulator_base = boost::logging::destination::base<boost::logging::default_, boost::logging::default_>]' LMLog.cpp:219: instantiated from here ../3rdparty/boost/boost_1_37_0/boost/logging/format/destination/syslog.hpp:41: error: expected primary-expression That can be fixed by pointing template keyword before operator() calling: ../3rdparty/boost/boost_1_37_0/boost/logging/detail/manipulator.hpp:571 Use virtual void operator()(param val) const { m_val.template operator()(val); } Instead virtual void operator()(param val) const { m_val.operator()(val); } Thank you for such library, I'm waiting for your comments. Regards, Dmitriy Lyfar.

2 2

Forwarded Message: Re: Bug Sprint - #1777 provide md5
by Kasra 06 Jun '09

06 Jun '09

Hi, I an Kevin Sopp are working on boost::crypto which will have an implementation of md5 and many other algorithms. The library is scheduled to be finished before Xmas. With Best Regards Mr. Kasra Nassiri Department of Mathematics & Computer Science Imperial College London

1 0

Interest check: Boost.Debug
by Zachary Turner 06 Jun '09

06 Jun '09

In my spare time I have been working on a library to analyze debug information from a running program. It either already does, or I would like to have it before I'm done, support all of the following (I'm sure there are plenty of other neat additions that I haven't thought of): - Loading debug info either for the currently running executable or from an offline executable - Printing human readable stack traces from a running program - Dumping stack traces to a file in release mode. In this case it's usually just a dump of the entire stack in binary. - Matching dumped stacks from step 3 to debug information offline to get post-mortem information. - Assuming symbol information is loaded either for the running program or an offline program, format a block of memory in a human readable format to print the structure of the memory (for example, display member values of a class with field names, given a block of memory representing an instance of the class) - Iteration of loaded modules - Check whether debugger is attached - output stream that goes to the debugger console, and is not visible in the debugged process. I'm not sure about the feasibility under non-windows platforms (it's very easy in windows), but I would think that if it's possible to figure out the PID of the process debugging you, that it should be possible to send output to their stderr which should achieve the same effect. - launch process under a debugger and receive basic types of debugging notifications. There's some obvious portability concerns, and some of these things are (considerably) more difficult than others, so I can't say I'd be able to support everything. However I already have rudimentary support for about half the items on the list although it is definitely in its infancy since before now I had not considered extending this to any other platforms / architectures. Main problem is that I can't say that I know enough about OSes other than Windows, and architectures other than x86/x64 to know if it would be not worth the hassle to prepare something like this for introduction into boost. Also everything I've done so far is only on Windows, and I don't suppose I'd have the know-how to make it work on any other OS, so in that sense I'd need some assistance. That being said, is it worth it to tackle something like this or should I just not worry about the generality and keep working on it for personal use only?

7 18

[spirit]
by Chandrashekhar Kumar 06 Jun '09

06 Jun '09

Hi, I have to parse the file, the contents of which(with a header) is below and stuff the double part only to std::vector<double>: "A","B","C","D" 1,2,3,4 5,6.7,8 ........ I started simple without header approach first : from libs/spirit/example/lex/example.hpp: inline std::string read_from_file(char const* infile) { std::ifstream instream(infile); if (!instream.is_open()) { std::cerr << "Couldn't open file: " << infile << std::endl; exit(-1); } instream.unsetf(std::ios::skipws); // No white space skipping! return std::string(std::istreambuf_iterator<char>(instream.rdbuf()), std::istreambuf_iterator<char>()); } from libs/spirit/classic/examples/number_list.hpp: /////////////////////////////////////////////////////////////////////////////// // // Our comma separated list parser // /////////////////////////////////////////////////////////////////////////////// bool parse_numbers(char const* str, vector<double>& v) { return parse(str, // Begin grammar ( real_p[push_back_a(v)] >> *(',' >> real_p[push_back_a(v)]) ) , // End grammar space_p).full; } int main() { std::string str = read_from_file("test.csv"); std::vector<double> v; if (parse_numbers(str.c_str(), v)) { cout << "-------------------------\n"; cout << "Parsing succeeded\n"; cout << str << " Parses OK: " << endl; for (vector<double>::size_type i = 0; i < v.size(); ++i) cout << i << ": " << v[i] << endl; cout << "-------------------------\n"; } else { cout << "-------------------------\n"; cout << "Parsing failed\n"; cout << "-------------------------\n"; } } But after running it, I am getting the result as "Parsing failed". I am going thru the doc to understand it better, but any quick spot will help me immensely. Thanks, Chandra

4 5

[Bug Sprint] Ticket #351
by Marshall Clow 05 Jun '09

05 Jun '09

https://svn.boost.org/trac/boost/ticket/351 is the oldest "bug" in the trac system. I'm trying to figure out what Jens meant in his last comment (dated 4-11-2005), where he said "See issue 4.40 in the C++ committee's library TR issue list". I looked at the current version of the library issues list <http://www.open-std.org/jtc1/sc22/wg21/docs/lwg-active.html>, and they don't have a 4.40 :-( I looked at revision #33 of this document (from April 2005), and they didn't have a 4.40 either. Anyone know what document he was referring to? -- -- Marshall Marshall Clow Idio Software <mailto:marshall@idio.com> It is by caffeine alone I set my mind in motion. It is by the beans of Java that thoughts acquire speed, the hands acquire shaking, the shaking becomes a warning. It is by caffeine alone I set my mind in motion.

4 5

Bug Sprint Report for Thursday, June 4th
by Marshall Clow 05 Jun '09

05 Jun '09

The boost bug sprint started Friday, May 29th, and runs through Sunday June 7th. Thursday was a very good day - let's keep it up! The bug sprint will be over Sunday night. Status <https://svn.boost.org/trac/boost/report/1> 7:00 AM PDT 5/29: 797 open tickets. 7:45 AM PDT 5/30: 772 open tickets. 6:00 AM PDT 5/31: 761 open tickets. 6:00 AM PDT 6/2: 747 open tickets. 6:00 AM PDT 6/3: 748 open tickets. 6:00 AM PDT 6/4: 739 open tickets. 8:00 AM PDT 6/5: 730 open tickets. Activity: 5/29: 6 new tickets, 77 modifications, 25 tickets closed 5/30: 2 new tickets, 42 modifications, 17 tickets closed 5/31: 2 new tickets, 27 modifications, 8 tickets closed 6/1: 2 new tickets, 42 modifications, 17 tickets closed 6/2: 5 new tickets, 18 modifications, 5 tickets closed. 6/3: 4 new tickets, 19 modifications, 2 tickets closed. 6/4: 3 new tickets, 42 modifications, 24 tickets closed. [ Numbers may not add up because I am counting via two different methods, using data that is time-stamped in two different time zones. Also, tickets can be closed and reopened. ] What can you do? See <https://svn.boost.org/trac/boost/wiki/BugSprintJune2009> for details. I've added four new reports to the trac: Open ticket count by owner: <https://svn.boost.org/trac/boost/report/18> Open ticket count by component: <https://svn.boost.org/trac/boost/report/19> Open ticket count by ticket type: <https://svn.boost.org/trac/boost/report/20> Open ticket count by milestone: <https://svn.boost.org/trac/boost/report/21> There's been a lot of discussion on the list about tickets; and there are about a dozen patches that have been tested and are ready to be applied. If you're looking to help, you can look at some of the older bugs, say, the ones for Boost 1.36, and determine if they still apply. If they do, note that in the ticket. There are 35 tickets that are still open that are marked as "to be fixed in Boost 1.36" See <https://svn.boost.org/trac/boost/report/3> for a list of open tickets by milestone. --------- Sign-up sheet -------- The following people have committed to participate in the bug sprint. Please add you name here, along with what you can do. 1) Marshall Clow (coordination, Mac OS X characterization) 2) Beman Dawes (filesystem, system, timer) 3) Doug Gregor (function, graph, logic, mpi, numeric, property_map, signals) 4) "joel falcou" <joel.falcou(a)u-psud.fr> ( linux gcc testing/VC 2008 testing, patching) 5) Michael Caisse <boost(a)objectmodelingdesigns.com> (bug fixing) 6) Jeremiah Willcock <jewillco(a)osl.iu.edu> (will test and commit graph patches) 7) David Abrahams (iterator, python) 8) Sohail Somani (patches for g++ 4.2.4) 9) Steven Watanabe <watanabesj(a)gmail.com> (bug fixes, como) 10) vicente.botet" <vicente.botet(a)wanadoo.fr> 11) Stjepan Rajko <stjepan.rajko(a)gmail.com> (fusion) 12) Daniel Wallin (parameter, ...) -- -- Marshall Marshall Clow Idio Software <mailto:marshall@idio.com> It is by caffeine alone I set my mind in motion. It is by the beans of Java that thoughts acquire speed, the hands acquire shaking, the shaking becomes a warning. It is by caffeine alone I set my mind in motion.

1 0