- Boost - lists.boost.org

[Boost.config] User.hpp for new PGI 10.9 compiler
by K. Noel Belcourt 05 Nov '10

05 Nov '10

Hi, Can a Boost.config developer take a look at the attached user.hpp generated by the configure script for the pgi-10.9 toolset? Are there any obvious changes necessary to boost/config/compiler/pgi.hpp? Thanks. -- Noel

2 5

Best method of checking for ==, <, streamability
by Christopher Jefferson 05 Nov '10

05 Nov '10

A user recently posted on boost-users asking for operator== support in boost::any. I have added this support to my private version, which extends spirit's implementation of any. I am interested in cleaning this up and submitting it to replace boost::any, if everyone is happy with this. The major issue is that my implementation requires type support operator==, operator< , hash and operator<< / operator>>. Are there any techniques in boost for detecting the presence of these operators which are sufficiently reliable they could be used in boost::any? Apologises for this question, but I have lost track of how well such checks can be implemented. Thanks, Christopher Jefferson

5 4

How about a call for bug-fix volunteers?
by Jim Bell 05 Nov '10

05 Nov '10

Library authors shouldn't have to bear the burden of bug reports for their libraries alone. Even maintaining their regression tests across all platforms isn't realistic (and isn't being done). So what if we try to recruit a couple helpers for each library? I see two avenues where we can use some volunteer help to improve boost's quality. 1. Dandelion pickers: look at failed/yellow regression tests and try to fix them. Volunteers could pick a platform they have access to, and try to work across all libraries. You might be surprised at how easy many are to fix. 2. Ticket triage: pick a library and go through all open tickets. Change severity, resolve, request more information, try to map to an existing regression test, interact with the submitter in the comments. (I think Trac needs a "requesting more information" state.) Even a brief 'triage' on each would be helpful, and help users feel they're being heard. (Trac needs to track this, too.) Write new regressions from legitimate issues. Recruiting pitch: it's a great way to improve your skills--troubleshooting, C++, platform-specific expertise, communication. Not so glamorous, but important and great experience. Perhaps we could assign a little of each to each SoC person. Maybe put the word out on Slashdot. See previous topic threads (http://lists.boost.org/Archives/boost/2010/10/index.php) "Report # 29 (aka 1.45 blockers) is too narrow" "[1.45] Beta final schedule" "[1.45] Thread issues"

14 18

Named subexpressions using \k<name>
by Chris Dragon 04 Nov '10

04 Nov '10

I have a user who says they have a bunch of expressions written for the Oniguruma regex library that use \k<name> syntax. According to http://www.boost.org/doc/libs/1_44_0/libs/regex/doc/html/boost_regex/syntax… Boost.regex should also support that syntax, but it does not seem to work. For example: boost::regex_replace( std::string("xyyz"), boost::regex(".*(?<first>x)(?<second>y).*", boost::regex_constants::perl), std::string("$+{second}\\k<first>"), boost::match_default | boost::format_all | boost::match_extra); results in "yk<first>" This result shows that $+{second} evaluated to "y" but \k<first> evaluated to "k<first>". I thought maybe the \k<name> syntax was only supported as a backreference within the first regex instead of the replace string, but this doesn't work either: boost::regex_replace( std::string("xyyz"), boost::regex(".*(?<first>x)(?<second>y)\\k<second>.*", boost::regex_constants::perl), std::string("$+{second}"), boost::match_default | boost::format_all | boost::match_extra); The result is "xyyz" meaning nothing was replaced (the regex did not match). However, if modify the regex to use \\g{name} syntax, it works: boost::regex_replace( std::string("xyyz"), boost::regex(".*(?<first>x)(?<second>y)\\g{second}.*", boost::regex_constants::perl), std::string("$+{second}"), boost::match_default | boost::format_all | boost::match_extra); The result is "y". Am I doing something wrong or have I found a bug? I'm using the latest stable 1_44_0 release compiled from source in VC9 and I also tried the pre-compiled library (http://sourceforge.net/projects/boost/files/boost-binaries/1.44.0/libboost_…) The OS is Windows 7. Thanks for the help!

2 2

[Boost.Timer] Why timer doesn't have a specific windows version using QueryPerformanceCounter() and QueryPerformanceFrequency()?
by dlaugt＠free.fr 04 Nov '10

04 Nov '10

Hi, Boost.Timer is based on the C function clock(). On windows, this function gives a precision of 1 millisecond only as CLOCKS_PER_SEC is equal to 1000. Why Boost.Timer doesn't use for windows QueryPerformanceCounter() and QueryPerformanceFrequency()? These functions give a precision around 2 microseconds. Daniel.

3 2

[build][doc] Testing section and run rule
by Mateusz Loskot 04 Nov '10

04 Nov '10

Hi, I'm looking for reference about run rule and the only thing I can find is this short reference: http://www.boost.org/doc/tools/build/doc/html/bbv2/reference/rules.html pointing to the Testing section which is currently blank: http://www.boost.org/doc/tools/build/doc/html/bbv2/tutorial/testing.html Would there be any chance to get this part updated? I'm looking for details about the run rule arguments: rule run ( sources + : args * : input-files * : requirements * : target-name ? : default-build * ) I'd appreciate if someone could explain what is the differences: sources vs input-files or args vs input-files. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net Charter Member of OSGeo, http://osgeo.org Member of ACCU, http://accu.org

2 2

gcc-4.5.1 warnings (ISO C++ 1998 does not support ‘long long’)
by Neal Becker 03 Nov '10

03 Nov '10

boost-1.44.0 + gcc-4.5.1: Lots of these warnings ./boost/config/suffix.hpp:497:18: warning: ISO C++ 1998 does not support ‘long long’

2 1

Will 1.45 incorporate active regression tickets?
by Jim Bell 03 Nov '10

03 Nov '10

Will 1.45 incorporate active regression tickets? I.e., report {30} <https://svn.boost.org/trac/boost/report/30> Several of these could be incorporated without too much work. I think a scan of these would be worth the release managers' time.

3 9

Unicode Library
by Emery Denuccio 02 Nov '10

02 Nov '10

Hey guys, about three years ago I mentioned I was working on a unicode library for boost and there was some interest then. I guess professional work got in the way and I never got around to polishing it up and submitting for review. I was digging through an old hard drive and found the source. It still lacks a few features, but is pretty damn cool. I threw up on on github if anyone wants to take a look and possibly help me get rolling on it again. Here: http://github.com/imori/boost.unicode Thanks, -em

3 2

[chrono] review version
by vicente.botet 02 Nov '10

02 Nov '10

Hi, I have made some modifications to Boost.Chrono before the review (Version 0.7.0). The library can be downloaded from http://www.boostpro.com/vault/index.php?action=downloadfile&filename=chrono… and the documentation is online on the sandbox http://svn.boost.org/svn/boost/sandbox/chrono/libs/chrono/doc/html/index.ht… or in PDF format http://svn.boost.org/svn/boost/sandbox/chrono/libs/chrono/doc/chrono.pdf Boost.Chrono depends on Boost.Ratio http://www.boostpro.com/vault/index.php?action=downloadfile&filename=ratio.… and optionaly Boost.System Header Only http://www.boostpro.com/vault/index.php?action=downloadfile&filename=system…. Next follows the major changes: [*Features:] * Boost_Chrono is now a configurable header only lib that allows the user to choose in addition if the windows file is included or not. * Added clock_string<> traits. * Define chrono_io for all the clocks * Add input of process_times representation [*Implementation:] * Moved some details to static_integer directory. * Use of detail/win files to avoid the use of windows.h file. * Completed the error_code handling. * Works now with BOOST_SYSTEM_NO_DEPRECATED. [*Fixes:] * Fix some warnings. * Fix original error on Mac * Don't fix the link with boost_system to static. [*Test:] * Added test on process and thread clocks. * Moved to lightweight_test.hpp. * Able to test multiple configurations. [*Doc:] * Removed some not useful parts as the history, the test and the tickets. Best, _____________________ Vicente Juan Botet Escribá http://viboes.blogspot.com/

2 2