- Boost - lists.preview.boost.org

[filesystem] version 3 use of std::mbstate_t
by Edward Diener 18 Aug '10

18 Aug '10

I believe that the version 3 filesystem headers which use std::mbstate_t need to include cwchar, but that they do not. This gives an error when I compile using Comeau with a VC9 backend, although compiling directly with VC9 is OK. This probably happens because of the assumption in filesystem that cwchar is included by some other C++ header, but rather than make such an assumption it would be better if cwchar were included directly by any header file which uses std::mbstate_t.

2 1

[1.44] PDF build of documentation is now available
by John Maddock 18 Aug '10

18 Aug '10

The PDF build of the documentation for Boost-1.44 is now available for download from https://sourceforge.net/projects/boost/files/ The direct links are: https://sourceforge.net/projects/boost/files/boost-docs/1.44.0/boost_1_44_p… https://sourceforge.net/projects/boost/files/boost-docs/1.44.0/boost_1_44_p… https://sourceforge.net/projects/boost/files/boost-docs/1.44.0/boost_1_44_p… https://sourceforge.net/projects/boost/files/boost-docs/1.44.0/boost_1_44_p… As usual please note that this only includes the subset of Boost documentation that is authored in quickbook/boostbook/docbook and so has an automatic conversion to PDF format. Enjoy! Regards, John.

1 0

I want to submit a patch
by Grizzly(Francis Smit) 18 Aug '10

18 Aug '10

Hello I would like to submit some changes to boost i.e. I have implemented an extension to boost to support extra conversion chars like %B for printing bool's symbolically i.e. switching on boolalpha, and %b to print out a integer type in binary (base 2) and %b(base) to print out and integer in base "base" 2<= base <= 36 and the uppercase flag controlling whether or not we use 'A' to 'Z' or 'a' to 'z' for digits above 9 Also I have implemented a printf, fprintf etc that uses C++0x's vardic template parameters to type safely print, this uses boostformat as the format string anyway I would like to submit this stuff to boost for hopefully inclusion in the boost libraries how do I go about that I cannot find it on the web page -- In my life God comes first.... but Linux is pretty high after that :-D Grizzly(Francis Smit) http://www.google.com/profiles/grizzlysmit

3 2

[Boost][website] SSL certificate
by admin＠thefireflyproject.us 18 Aug '10

18 Aug '10

I recently switched from Firefox to Chromium, and I've been having issues accessing [1]https://svn.boost.org. It seems that the SSL certificate used for [2]svn.boost.org is either not properly configured, or not issued by one of the major SSL certificate providers (e.g. VeriSign, GoDaddy). Examination of the certificate indicates that it's issued by the Computer Science Department of Indiana University, and the certificate doesn't have a chain that leads back to a well known CA (the chain is just '[3]svn.boost.org => [4]cs.indiana.edu', and most browsers I've tried don't recognize [5]cs.indiana.edu as a legitimate CA by default). If this isn't just a matter of improper configuration (or, for that matter, just a matter of my browsers being screwy), I'd be happy to offer my own SSL certificate to Boost. The certificate is a standard SSL certificate issued by GoDaddy (domain controlled validation, certificate signing algorithm is RSA 2048 bits), and it's paid through 02/20/2011. I'm currently using my cert for my Debian mirror, so I would have to revoke the current certificate, and then submit a CSR from [6]boost.org's server. Ideally, then I would generate a CSR request, and the boost server would sign it; I'd end up with a cert chain of 'mysite => [7]boost.org => GoDaddy'. [8]boost.org and subdomains would have a cert signed directly by GoDaddy, so the [9]svn.boost.org cert would be verify by most browsers automatically. If there's any interest in this, please let me know. - Bryce Lelbach References 1. https://svn.boost.org/ 2. http://svn.boost.org/ 3. http://svn.boost.org/ 4. http://cs.indiana.edu/ 5. http://cs.indiana.edu/ 6. http://boost.org/ 7. http://boost.org/ 8. http://boost.org/ 9. http://svn.boost.org/

9 12

[1.45] release branch open for merges
by Eric Niebler 17 Aug '10

17 Aug '10

Now that 1.44 is tagged and bagged, the release branch is open once again for (well-tested!) merges from trunk. Let me use this as an opportunity to remind folks that the release process works best when merges from trunk are done continuously instead of in a mad rush at the end just before freeze. Thanks for listening! -- Eric Niebler BoostPro Computing http://www.boostpro.com

1 0

[website] Moving guidelines back to main site
by Daniel James 17 Aug '10

17 Aug '10

Hi, I'm no longer working on transferring pages to the wiki. It's a bit silly having a few pages on there, and possibly adds to the performance problems on trac, so I'm moving the pages back to the main site. Daniel

1 0

[1.44.0] Release 1.44.0 is now available
by Beman Dawes 17 Aug '10

17 Aug '10

Release 1.44.0 of the Boost C++ Libraries is now available. These open-source libraries work well with the C++ Standard Library, and are usable across a broad spectrum of applications. The Boost license encourages both commercial and non-commercial use. This release contains two new libraies (Meta State Machine & Polygon) and numerous enhancements and bug fixes for existing libraries. For details, including download links, see http://www.boost.org/users/download/version_1_44_0 The release can also be downloaded directly from SourceForge. See http://sourceforge.net/projects/boost/files/ To install this release on your system, see http://www.boost.org/doc/libs/release/more/getting_started/index.html Thanks, --The Boost release team Beman Dawes Daniel James Eric Niebler Rene Rivera Vladimir Prus

4 3

boost_1_44_0 strange build problem
by Neal Becker 17 Aug '10

17 Aug '10

I thought build was working OK on fedora f13 x86_64. But then I noticed something strange: I'm building like this: bjam -sHAVE_ICU=1 -sEXPAT_INCLUDE=/usr -sEXPAT_LIBPATH=/usr/lib64 -- layout=tagged threading=single,multi stage Running 1st time, I got no errors....updated 1353 targets... But then I reran in the same directory and got: ...patience... ...patience... ...patience... ...found 7771 targets... ...updating 96 targets... [ rebuilt release/link-static/libboost_math_c99f.a and release/link- static/libboost_math_c99.a ] ...updated 96 targets... Trying a 3rd time, nothing happens.

2 2

[Boost]boost_1_32_00 solaris /1.32.0/include/boost/iterator/iterator_facade.hpp"
by pradheep shrinivasan 17 Aug '10

17 Aug '10

Hi i am using boost 1.32 on the sun solaris. Machine: *SunOS etbf27 5.9 Generic_122300-13 sun4u sparc SUNW,Sun-Fire-V440* Compiler: *CC: Sun C++ 5.8 2005/10/13* And i am getting the following error when i use the tokenizer <> Error : "*/usr/include/boost/iterator/iterator_facade.hpp", line 837: Error: Could not find a match for boost::iterator_core_access::equal*" I googled and found out that its a bug in the boost 1_32_00 version of boost but could not find anything concrete except to upgrade to the next version. I cannot upgrade because 1_32 is already used in many parts of project and i have to go through a long chain of approval. Can you please provide me links to the workaround if there is one available. P.S : Its my first post ... Feel free to point out the mistakes i made in posting and i would be happy to correct them. Thanking you -- Programmers are in a race with the Universe to create bigger and better idiot-proof programs, while the Universe is trying to create bigger and better idiots. So far the Universe is winning. – Rich Cook. J ------- regards Pradheep

2 1

[preprocessor] check if a token is a keyword (was "BOOST_PP_IS_UNARY()")
by Lorenzo Caminiti 17 Aug '10

17 Aug '10

Hello all, I asked this question before but received no answer: Is there any problem in using `BOOST_PP_UNARY()` to check if a token matches a predefined keyword as indicated by the code below? The following `IS_PUBLIC(token)` macro expands to 1 if `token` is `public`, to 0 otherwise: #define PUBLIC_public (1) #define IS_PUBLIC(token) BOOST_PP_IS_UNARY(BOOST_PP_CAT(PUBLIC_, token)) IS_PUBLIC(public) // Expand to 1. IS_PUBLIC(abc) // Expand to 0. This works just fine on both GCC and MSVC. However, `BOOST_PP_UNARY()` is only part of Boost.Preprocessor private API because: Paul Mensonides mentioned in http://lists.boost.org/Archives/boost/2004/08/70238.php > Paul Mensonides wrote: > I know. They (and other types of detection macros) are very useful. Right now, > the Borland configuration is used by the IBM preprocessor and the Sun > preprocessor also. I'd like to know whether or not those macro definitions work > correctly on those preprocessors before I add it. Though those macros aren't > part of the public interface, they are part of the internal interface. I.e. > they are used internally as if they were a public interface (though they are > used carefully on some preprocessors). They are stable, and the worst thing > that might happen in the future is that they will be moved to a different > directory. Thus, you can use them, but beware of VC and versions of MWCW prior > to v9. They in particular have severe problems with expansion order. E.g. VC > will even fail this test: (Boost.Preprocessor, Boost.Typeof, and Boost.Spirit already use `BOOST_PP_UNARY()` internally.) Thank you very much. -- Lorenzo

3 5

[DateTime] Converting ptime to real POSIX Time
by Artyom 17 Aug '10

17 Aug '10

Hello, I want to provide some integration between boost::posix_time::ptime and boost::locale::date_time - make transparent conversion between two. I have following point I either miss in ptime design or it has design flaws: 1. POSIX Time (see http://en.wikipedia.org/wiki/Unix_time) is always considered Time in seconds from 1970-JAN-1 00:00:00 UTC not including leap seconds. However ptime can be constructed from "local_time" which is totally contradicts a well known definition of POSIX time. 2. I can't find any way to convert it to "number" POSIX time. I can convert it to time_t and from time_t but if I need a better accuracy -milli-seconds, nano-seconds etc. it seems to be impossible according to docs. How can I convert it to more accurate representation? Is there any way to get a notice about how ptime was created, with universal time scale or local time scale, also I there a way to get UTC POSIX time from ptime even if it was created from local time. Artyom

2 1

WCHAR_MAX not defined on openbsd
by Nick Owens 17 Aug '10

17 Aug '10

hi there, i'm using openbsd 4.7 with g++ 4.2.4 installed from openbsd packages. i've tried building both boost 1.43 and 1.44rc, and both have several libraries fail due to WCHAR_MAX not being defined. this appears to be because __STDC_LIMIT_MACROS is not defined while processing /usr/include/stdint.h. i built boost with ./bjam cxxflags='-D__STDC_LIMIT_MACROS' and there are no more errors about WCHAR_MAX not being defined. perhaps this define should be added to boost/cstdint.hpp, or is there a deeper reason why WCHAR_MAX is not being defined correctly?

4 7

[DateTime] Cannot handle 64bit seconds
by Roland Bock 16 Aug '10

16 Aug '10

Hi, when transforming a unix time into a boost::posix_time::ptime, the value of the unix time is truncated to long in for method boost::posix_time::from_time_t. As a result, -4260211200 is represented by some ptime in the year 1971, but it should be 1835. Or, in other words Boost.DateTime has the year 2038 problem. Regards, Roland

2 2

[filesystem][lexical_cast] Lexical cast of filenames containing spaces
by Daniel James 16 Aug '10

16 Aug '10

Hi, An issue has come up in program options. With filesystem v3, this throws: lexical_cast<boost::filesystem::path>("file name") The problem is that filesystem v3's stream extractor treats spaces as separators (which is the right thing to do IMO), so it only extracts "file", which causes lexical cast to throw an exception - because the whole string hasn't been extracted. Would it be possible to create a special case in lexical_cast to deal with this? How does it deal with this problem for strings? Daniel

3 6

outer class `this` in local classes
by Lorenzo Caminiti 16 Aug '10

16 Aug '10

Hello all, Is there a way to access the outer class `this` from a local class but without using inheritance? Let me explain with an example: class x { // outer class public: void g() {} void f() { this->g(); // (1) struct y: x { // local class *** using inheritance *** y(x* super): x(*super) {} // (2) void h() { this->g(); // (3) } }; y(this).h(); } }; *** Is there a way to do this but without inheriting `y` from `x`? *** At line (3), the local class `y` can access the outer class `x::g()` simply using `this` because `y` inherits from `x`. However, this inheritance requires to construct another object `x` when `y` is constructed as in line (2) adding runtime overhead and requiring `x` to have an accessible copy constructor. In my application, I need line (3) to essentially look like line (1) so you can program code inside `y` members as if it were inside `x` members. A part from that, the local class `y` could look as it is needed to solve this problem -- with some member variables, other member functions, etc. (For example, I tried to redefine `y::operator->()`/`y::operator*()` to return a pointer/reference to `x` but this does not work because `this->`/`*this` always retain its pointer semantics and they do not use the user defined operators...) Thank you very much. -- Lorenzo

2 3

Re: [boost] [exception] ostringstream like
by fabien.castan＠free.fr 16 Aug '10

16 Aug '10

> exception are just here to gather and carry diagnostic info, not full fledged error message If you throw a bad_alloc, you don't need to add a full fledged error message, I agree that the localization and the exception type is sufficient. When you throw a logic_error, more the message is clear, precise and detailed better it is. > may fail to allocate the needed memory for the string and stream, thus maskign the initial exception with some bad_alloc. I agree for bad_alloc exception, but as before you don't really need a message in this particular case. If you throw a logic_error, you don't have more chance to encounter a bad_alloc than everywhere in your application.

2 1

Re: [boost] [chrono] [dependence of common_type on Boost.TypeOf]
by Adam Merz 16 Aug '10

16 Aug '10

vicente.botet <vicente.botet <at> wanadoo.fr> writes: > Hi again, > I have reached to manage with the ambiguous overloads and all the tests works > as before. > I have do it as follows: <snip code> That doesn't seem very robust in the case that there is no common type (in terms of the compiler error anyway). Maybe I'm missing something regarding the required semantics, but couldn't something like the following be used, so at least you get a reasonable static assertion error instead? #include <boost/mpl/if.hpp> #include <boost/type_traits/is_base_of.hpp> #include <boost/type_traits/is_same.hpp> #include <boost/static_assert.hpp> template<typename T1, typename T2> struct common_type { typedef typename boost::mpl::if_< boost::is_base_of<T1, T2>, T1, typename boost::mpl::if_< std::is_base_of<T2, T1>, T2, void >::type >::type type; // no common type BOOST_STATIC_ASSERT((!boost::is_same<type, void>::value)); }; template<typename T1> struct common_type<T1, void> { // void is not a valid type BOOST_STATIC_ASSERT(sizeof(T1) != sizeof(T1)); }; template<typename T2> struct common_type<void, T2> { // void is not a valid type BOOST_STATIC_ASSERT(sizeof(T2) != sizeof(T2)); }; (Apologies for messing up the message threading. I post via Gmane, and this thread isn't showing up there, presumably because of the encoding issues in the message subject.)

3 4

Detection of 64bit using macro
by Kim Kuen Tang 16 Aug '10

16 Aug '10

Hi all, the question might be not directly related to boost. But i just want to be sure that i am not reventing the wheel. I am searching for a macro that is able to detect that a system is 32bit or 64bit no matter what compiler is used. Is there something similar already implemented in boost? Perhaps some background about this feature. Template specialization for std::size_t is not needed, when the specialization already exists for unsigned int. But on a 64bit system this is not true. So you need explicitly added the specialization whenever a 64bit compiler is used. See the following example. # include <cstddef> template<typename T> struct Null; template<> struct Null<unsigned int> {}; template<> struct Null<std::size_t> {}; // compile only on a 64bit compiler int main() { return 0; }; Thx for any comments, help or suggestions Kim

5 6

[chrono] v0.4.5 Documentation update + warnings removal + bug fixes
by vicente.botet 16 Aug '10

16 Aug '10

Hi, I have made some minor modifications to the Boost.Chrono library as requested on these mailing lists. The implementaton is stable. Waiting for the review I plan to add yet a lightweight stopwatch, as suggested by Tom Tan on a personal mail, which stores a reference to a generalization of the Clock duration or an accumulator of the Clock duration. I'll concentrate also in improving the documentation and the tests. Anthony Williams will be the review manager and I hope we could find a date soon. Even if the review's date is not annonced yet, it will be great if some of you make a pre-review, so the conflicting issues are managed before the review. 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…. New Features since v0.4.3: Version 0.4.5, July 6, 2010 Documentation update Documentation a.. Overview rewriting b.. Added missing thread_clock reference. c.. How to implement a thread_clock tutorial removed. d.. References section renamed to External Resources. e.. Added links to source examples. f.. Added links between Models and Concepts. g.. Added macros descriptions. h.. Cleanup. Bug Fixes a.. Valgrind fixes: "Conditional jump or move depends on uninitialised value(s)" b.. Take care of Boost.System break on version 1.44 c.. gcc.4.4 "warning: suggest parentheses around '&&' within '||' " removal. Version 0.4.4, February 22, 2010 Warning fixes Bug Fixes a.. scoped_suspend warning removal b.. error_code management completed _____________________ Vicente Juan Botet Escribá http://viboes.blogspot.com/

5 20

[config] _mingw.h
by Edward Diener 16 Aug '10

16 Aug '10

The config platform file win32.hpp has: # include <_mingw.h> when __MINGW32__ is defined. I do not see _mingw.h anywhere. Where is this header supposed to be ?

2 2

[log] Wide Character Backend file problems
by Sivaram Kannan 15 Aug '10

15 Aug '10

Hi, I was trying to create a log file with wide character support. Similar code with normal character support works well, where as for wide character support the log file itself is not getting created. Here is the code for both types. Can someone tell me, what am I missing with the wide character type. The code compiles, but the log file alone is not getting created when the program is run. //Wide Character version void Log_Init() { boost::function< void (std::wostream&, boost::log::wrecord const&) > formatter = boost::log::formatters::wstream << boost::log::formatters::date_time< boost::posix_time::ptime >(L"TimeStamp") << L" *" << boost::log::formatters::attr< int >(L"Severity") << L"* " << boost::log::formatters::wmessage(); boost::shared_ptr< sinks::synchronous_sink<boost::log::sinks::wtext_file_backend> > sink = boost::log::winit_log_to_file( keywords::file_name = L"C:\\BMR\\Logs\\bmr.log", // file name pattern keywords::rotation_size = 1 * 1024 * 1024, // rotate files every 1 MiB... keywords::open_mode = std::ios_base::app, keywords::auto_flush = true ); sink->locked_backend()->set_formatter(formatter); // Register common attributes boost::log::add_common_attributes(); } //Normal Character version void Log_Init() { boost::function< void (std::ostream&, boost::log::record const&) > formatter = boost::log::formatters::stream << boost::log::formatters::date_time< boost::posix_time::ptime >("TimeStamp") << " *" << boost::log::formatters::attr< int >("Severity") << "* " << boost::log::formatters::message(); boost::shared_ptr< sinks::synchronous_sink<boost::log::sinks::text_file_backend> > sink = boost::log::init_log_to_file( keywords::file_name = "C:\\BMR\\Logs\\bmr.log", // file name pattern keywords::rotation_size = 1 * 1024 * 1024, // rotate files every 1 MiB... keywords::open_mode = std::ios_base::app, keywords::auto_flush = true ); sink->locked_backend()->set_formatter(formatter); // Register common attributes boost::log::add_common_attributes(); }

2 8

Re: [boost] : [chrono] v0.4.5 Documentation update + warnings + removal + bug fixes
by Tan, Tom (Shanghai) 15 Aug '10

15 Aug '10

>Date: Tue, 10 Aug 2010 20:00:15 +0200 >From: "vicente.botet" <vicente.botet(a)wanadoo.fr> >Subject: [boost] [chrono] v0.4.5 Documentation update + warnings removal + bug fixes > >Waiting for the review I plan to add yet a lightweight stopwatch, as suggested by Tom Tan on a personal mail, >which stores a reference to a generalization of the Clock duration or an accumulator of the Clock duration. > I'll concentrate also in improving the documentation and the tests. Hi Vincente, Thanks for the feature. One more request, can you make this following specialization work? //typedef stopclock_accumulator< boost::chrono::process_cpu_clock > process_cpu_stopclock_accumulator; It's commented out in your source code, I assume it does not compile yet. In general, I'd like to see process_cpu_clock to be supported as the first-class citizen like process_real_cpu_clock, process_user_cpu_clock and so on. -Tom

2 2

[bind] [patch] support for result_of
by Stefan Strasser 15 Aug '10

15 Aug '10

Hi, would a full implementation of this patch: https://svn.boost.org/trac/boost/raw-attachment/ticket/4542/bind.patch be accepted to Boost.Bind? it provides support for bind()ing generic function objects and for boost::result_of<F(...)> where F is a result of bind(). for example: struct F{ template<typename T> T operator()(T const &t, int) const{ return t; } template<typename Args> struct result; }; the result type depends on the argument type, so instead of "result_type", "result" is defined according to boost::result_of: template<typename T> struct F::result<F(T const &,int)>{ typedef T type; } this function object can not be used with bind(), because bind() requires F::result_type to be defined. with the patch, you can bind() the function object, and determine the result of the bound function object using result_of: int main(){ g(bind(F(),_1,5)); } template<typename F> void g(F const &f){ double doubleres=f(1.234); //F(1.234,5) -> double boost::result_of<F(int const &)>::type intres=f(1); // F(1,5) -> int } C++ TR1 includes result_of and bind(). it doesn't seem to say anything about result_of<bind()-result> though.

1 0

[DateTime] posix_time_zone incorrect sign?
by Roland Bock 15 Aug '10

15 Aug '10

Hi, I think that posix_time_zone in Boost.DateTime is using the wrong sign for offsets from GMT: According to the documentation, posix_time_zone is modeled after IEEE Std 1003.1. The documentation gives several examples, for instance <cite> "MST-7" This zone is as simple as it gets. This zone lies seven hours west of GMT and has no daylight savings. </cite> But all other sources for IEEE Std 1003.1 I found so far say that negative offsets indicate *east* of GMT, see for instance: http://www.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap08.html <cite> If preceded by a '-' , the timezone shall be east of the Prime Meridian; otherwise, it shall be west (which may be indicated by an optional preceding '+' ). </cite> http://tools.ietf.org/html/draft-ietf-dhc-timezone-01 <cite> The format of the IEEE 1003.1 POSIX timezone specification is defined as follows:[...]If preceded by a '-', the timezone is east of the Prime Meridian, otherwise it is west ('+' is optional) </cite> http://www.twinsun.com/tz/tz-link.htm <cite> Numeric time zone abbreviations typically count hours east of UTC, e.g., +09 for Japan and -10 for Hawaii. However, the POSIX TZ environment variable uses the opposite convention. For example, one might use TZ="JST-9" and TZ="HST10" for Japan and Hawaii, respectively. </cite> IMO, the implementation or the documentation should be changed. Personally, I'd prefer a change in the implementation, even though this would be a rather nasty breaking change. Regards, Roland

1 0

[1.44] Release imminent
by Beman Dawes 14 Aug '10

14 Aug '10

Unless someone objects right away, I plan to start building the release at 1PM, US Eastern Daylight Time. Thanks, --Beman

9 11