January 2009 - Boost - lists.preview.boost.org

[1.38] Generating README.txt
by Daniel James 28 Jan '09

28 Jan '09

Hi Beman, Cmake needs a README.txt file based on the release notes. There's an out of date one in trunk, but nothing in the release branch. We generate this fairly easily using the lynx browser: lynx -dump -nolist -display_charset=utf-8 \ http://beta.boost.org/users/history/minimal.php/version_1_38_0 \ > README.txt It's probably easiest for you to add this to your release scripts, but if you prefer I could do it when generating the documentation, and upload the README.txt file and you could then copy it into place. Daniel

2 2

to_utf8/from_utf8
by Goran Mitrovic 27 Jan '09

27 Jan '09

It would be nice if boost would export and document to_utf8 and from_utf8 functions (possibly from string utils *headers only* library). Currently, I use following workaround, but I believe those two useful utility functions deserve better: #define BOOST_PROGRAM_OPTIONS_NO_LIB 1 #include <boost/program_options/detail/convert.hpp> #include <boost/program_options/detail/utf8_codecvt_facet.hpp> #undef BOOST_PROGRAM_OPTIONS_NO_LIB #include <libs/program_options/src/convert.cpp> #include <libs/program_options/src/utf8_codecvt_facet.cpp>

1 0

[1.38.0] [Getting started] Windows example boo boo?
by Beman Dawes 27 Jan '09

27 Jan '09

In the Windows example in section 5.4.2, C:\WINDOWS> cd C:\Program Files\boost\boost_1_38_0 C:\Program Files\boost\boost_1_38_0> bjam ^ More? --build-dir="C:\Documents and Settings\dave\build-boost" ^ More? --toolset= --build-type=complete msvc stage Shouldn't "msvc" follow "--toolset="? --Beman

2 3

[format] Inconsistencies with printf
by Sam Partington 27 Jan '09

27 Jan '09

Hi, There are still several differences between printf and Boost.Format : http://www.boost.org/doc/libs/1_37_0/libs/format/doc/format.html#printf_dif… Whilst I realise that it is difficult to fully meet the printf formats, is there likely to be an improvement in this area? We are using Boost.Format to replace a lot of existing sprintfs, so having exact compatiblitity would be very useful. At the least it would be nice if unsupported options were ignored silently. For example we had the format string "%8.8x" silently pad the result with spaces rather than zeros, which rather surprised us, as we have all exceptions switched enabled. I have managed to add a rather poor emulation of the precision with integral types. It only works correctly when the width and the precision are the same, but at least it will raise an exception in other cases, and if exceptions are disabled it prefers to pad with zeros as that breaks our code less. I realise that others mileage may vary. But for myself I prefer this non-silent version. i.e. : "%8.8x" % 0x1234 == 00001234 "%8.3x" % 0x1234 == 00001234 * "%3.8x" % 0x1234 == 00001234 * sprintf would return " 1234" here. parsing.hpp:267 : In function parse_printf_directive just before the switch on the type char. // begin SRP added if(precision_set && strchr("xXpoudi", int(wrap_narrow(fac, *start, 0)))) { if (fpar->fmtstate_.precision_ != fpar->fmtstate_.width_) { // we only support the precision on integral types if the width and // the precision are identical. If exceptions are enabled then // throw, but if not do something vaguely sensible, and pad with // zeros up to the largest width specified maybe_throw_exception(exceptions, start-start0+offset, fstring_size); if (fpar->fmtstate_.precision_ > fpar->fmtstate_.width_) { fpar->fmtstate_.width_ = fpar->fmtstate_.precision_; } } fpar->pad_scheme_ |= format_item_t::zeropad; } // end SRP added One of the goals of the Format library is to "provide printf-compatibility, as much as it makes sense in a type-safe and type-extendable context." Is this goal still valid? Sam

1 0

[1.38.0] Beta under construction; branches/release closed
by Beman Dawes 27 Jan '09

27 Jan '09

The beta release is under construction. Please do not make any further commits to branches/release. Thanks, --Beman

1 0

[crypto] Feed Back
by Kasra 26 Jan '09

26 Jan '09

Hi, Since I have uploaded boost.crypto library on the vault there has been fare amount of downloads. I just wanted to see if anyone would like to give some feedback on the design of the library. With Best Regards Kasra

1 0

[msm] Gauging interest
by Christophe Henry 26 Jan '09

26 Jan '09

Hi, Msm has been in the Vault since a few months now and has been downloaded quite a few times, so it looks like there is interest in such a state machine framework, but I would prefer to be sure before requesting a formal review. So my question is, is there interest from the Boost community in Msm becoming part of Boost? Regards, Christophe

6 5

[threadpool] draft n2276 - launch_in_pool
by Oliver Kowalke 25 Jan '09

25 Jan '09

Hello, I did a look into draft n2276 - a launch_in_pool function is suggested (passing task to a system provided threadpool). Is it reasonable to have a static threadpool? How many worker-threads should this pool contain and how are the submitted tasks queued (FIFO, priority order ... unlimited/limited number of tasks can bes stored). What about applications which require a pool with different configuration than the static pool provides? Is it acceptable to pay for an unused pool? regards, Oliver -- Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger

5 7

[thread/interprocess] could we improve recursive_mutex constructor
by vicente.botet 24 Jan '09

24 Jan '09

Hi, the recursive_mutex constructor initialize/set/destroy the pthread_mutexattr_t every time. I'm wondering if we can improve the efficiency storing this on a static variable which will be initialized once. What could be the better way to initialize this static variable? Note: the same applies to interprocess mutexes. recursive_mutex() { // begin code that can be initialized only once pthread_mutexattr_t attr; int const init_attr_res=pthread_mutexattr_init(&attr); if(init_attr_res) { throw thread_resource_error(); } int const set_attr_res=pthread_mutexattr_settype(&attr,PTHREAD_MUTEX_RECURSIVE); if(set_attr_res) { throw thread_resource_error(); } // end code that can be initialized only once int const res=pthread_mutex_init(&m,&attr); if(res) { throw thread_resource_error(); } // begin code that can be removed BOOST_VERIFY(!pthread_mutexattr_destroy(&attr)); // end code that can be removed } Regards, Vicente

2 2

[sandbox] Is the sandbox open to anyone
by Sid Sacek 24 Jan '09

24 Jan '09

Is the sandbox open to anyone for code submission, or is there a more complicated process before being able to submit libraries? Regards, -Sid

4 4