- Boost - lists.boost.org

[Integer] Mac OS X: WCHAR_MIN != std::numeric_limits<wchar_t>::min()
by Douglas Gregor 06 May '05

06 May '05

The title says it all: the Mac OS X system headers are inconsistent about the minimum value of a wchar_t. The C++ <limits> header has it right, but the definition of WCHAR_MIN in <cwchar>/<wchar.h> is wrong (0). If there are no complains, I'm going to commit the following patch. I don't believe this will affect CodeWarrior on the Mac, but I can't test against it. Index: integer_traits.hpp =================================================================== RCS file: /cvsroot/boost/boost/boost/integer_traits.hpp,v retrieving revision 1.26 diff -u -r1.26 integer_traits.hpp --- integer_traits.hpp 17 Dec 2004 11:56:15 -0000 1.26 +++ integer_traits.hpp 6 May 2005 15:46:36 -0000 @@ -88,7 +88,9 @@ template<> class integer_traits<wchar_t> : public std::numeric_limits<wchar_t>, -#if defined(WCHAR_MIN) && defined(WCHAR_MAX) + // Don't trust WCHAR_MIN and WCHAR_MAX with Mac OS X's native + // library: they are wrong! +#if defined(WCHAR_MIN) && defined(WCHAR_MAX) && !defined(__APPLE__) public detail::integer_traits_base<wchar_t, WCHAR_MIN, WCHAR_MAX> #elif defined(__BORLANDC__) || defined(__CYGWIN__) || defined(__MINGW32__) || (defined(__BEOS__) && defined(__GNUC__)) // No WCHAR_MIN and WCHAR_MAX, whar_t is short and unsigned: Doug

1 0

building boost
by Stefan Seefeld 06 May '05

06 May '05

I'm using some of the recent features of boost, and so I updated regularly from cvs and recompile. However, as was noted before, a simple 'bjam' will take a *lot* of time, and consume a *lot* of disk space. Right now I'm seeing almost 900 MB in my boost tree and that doesn't even count all the space taken by boost once 'bjam install' has finished. I'd really like to see an option to instruct boost.build only to produce one set of libraries, such as release-multithread-shared (falling back to static if shared isn't available). I don't care how such an option would be spelled, and whether that would become the default build target or not. But the current situation is quite wastefull, IMO. Thanks, Stefan

2 2

[program_option] allow_unregistered now works
by Vladimir Prus 06 May '05

06 May '05

Since this was the most requested change for program_options, I though I'd post specific announcement. I've committed a change that finally makes command_line_parser::allow_unregistered to work as expected. Assuming you get command line like: --foo=10 --bar=15 --biz 5 -cd -d10 and registered options are "foo" and "-c", where "-c" takes no value, parsing that command line will give you the following list of options: ("foo", "10") ("bar", "15") * ("biz", ) * ("5") (positional) ("-c", ) ("-d", ) * ("-d", "10) * The 'option' instances corresponding to option marked with '*' will have 'unregistered' member set to true. With that information it's possible to: 1. Collect all unregistered option as process them separately. 2. Construct a new command line from unregistered options and pass it to some application. In the above example, reconstructed command like would be --bar=15 --biz 5 -d -d10 There are some notes of interest. First, the option class don't keep the original tokens it was created from. The unregistered option can technically arrive from user-provided 'additional parser' where 'original tokens' are not even present. Second, for 'sticky' short options, like '-cd' above, the library can break them in parts. Again, in example we get: ("-c", ) ("-d", ) * The 'c' letter is recognized, and the 'd' letter is not. I find this behaviour better than marking the entire '-cd' as unrecognised. Finally, the new functionality might not work nice with long options that start with a single dash (allow_long_disguise style option): -foo will be considered as short option '-f' with value 'oo', and never as long option 'foo'. Feedback is appreciated! I was also asked for 'allow_unregistered' support for config file. I agree this might be good, but given that config file never supported it in any form, it's clearly a new feature, and will have to wait till 1.33 is released. - Volodya

3 3

[policy_ptr]std_ptrs.hpp's include target missing & incomplete shared_ptr emulation
by Larry Evans 06 May '05

06 May '05

The file: std_ptrs.hpp contains: #include "policy/boost.hpp" yet there's no policy/boost.hpp. However, there is: boost_policies.hpp However, in that file, the shared_storage class, contains: detail::shared_count count_; IOW, count_, unlike that in shared_ptr, contains no information about the type of pointee_; hence, I can't understand how policy_ptr's smart_ptr<...>, can emulate boost's shared_ptr with existing policies. What have I missed?

2 3

[patch] typo in more/getting_started.html
by Jonathan Wakely 06 May '05

06 May '05

Simple typo

2 1

[filesystem] Operations predicates
by Beman Dawes 06 May '05

06 May '05

I've completed an analysis of expectations for the exists() and is_xxx() family of functions, and the previously suggested status() and symlink_status() functions. See http://www.esva.net/~beman/filesystem_operations_predicates.htm Thanks to Peter Dimov, Rob Stewart, and Jeff Garland for their suggestions. Errors are mine alone. Comments? --Beman

7 41

Re: Boost filesystem documentation
by James Gregory 06 May '05

06 May '05

> You are right that there is a clash. But it seems to me std::runtime_error > should be the base class, so it is the implementation that is wrong. > > Comments? > > --Beman 1. The boost guidelines at http://www.boost.org/more/error_handling.html say "Derive your exception class from std::exception. Except in *very* rare circumstances where you can't afford the cost of a virtual table, std::exception makes a reasonable exception base class" 2. But runtime_error does derive from std::exception, and the error is a run time error 3. Whilst I'm here, I would also like to point out the following silly code I need to use boost filesystem for a program designed to run in Linux and Windows: #ifdef __linux__ fs::path::default_name_check(fs::windows_name); #else //ie we are compiling for Windows fs::path::default_name_check(fs::native); #endif If I use fs::native at all times then I cannot use paths with spaces in under Linux, but if I use fs::windows_name at all times then I cannot use a colon to specify drive names in Windows (e.g. C:\). James

2 1

boost configuration issue
by François Dumont 06 May '05

06 May '05

Hello I think I found a configuration issue while building boost 1.32.0 with VC .Net 2003 (VC71) using STLport 5.0 beta (latest from cvs STLPORT_5_0 branch). Maybe someone already notive this problem but the latest boost CVS version still show it. With the STLport lib the macro configuration is : - BOOST_NO_INTRINSIC_WCHAR_T defined - BOOST_NO_STD_WSTRING _not_ defined, wstring are supported Thanks to the BOOST_NO_STD_WSTRING macro the date_time lib instanciate code for wstring specific type. For instance in libs/date_time/src/gregorian/greg_month.cpp you will find a block of code in a #ifndef BOOST_NO_STD_WSTRING block. The date_time lib use the lexical_cast tool. But the lexical_cast tool do not care about BOOST_NO_STD_WSTRING and rather check, among other macros, BOOST_NO_INTRINSIC_WCHAR_T and so do not grant the necessary specialization for wchar_t and wstring. The error message is then something like: D:\boost_1_32_0\boost/lexical_cast.hpp(137): error: no operator "<<" matches these operands operand types are: std::basic_stringstream<wchar_t, std::char_traits<wchar_t> , std::allocator<wchar_t> > << const std::basic_string<char, std::char_traits<char> , std::allocator<char>> return stream << input; Sorry for not having the accurate message but I have the compiler on an other computer. I see 2 possible solutions to this problem: - concider that there is no wstring support if there is no intrinsic wchar_t support. - make lexical_cast less strict and do not require intrinsic wchar_t support. Bests

2 2

RE: [boost] Re: [MPL] is_sequence problem
by Brian Braatz 06 May '05

06 May '05

This is not my problem (just piqued my interest :) ) But for grins I tried this on 7.1 boost::mpl::is_sequence< list<int> >; // compiles boost::mpl::is_sequence< int_<0> >; // compiles boost::mpl::is_sequence< int<0> >; // doesnt compile boost::mpl::is_sequence< int_<0> >::value; // doesnt compile so replacing with int didn't work > -----Original Message----- > From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] > On Behalf Of Joel > Sent: Thursday, May 05, 2005 10:25 PM > To: boost(a)lists.boost.org > Subject: [boost] Re: [MPL] is_sequence problem > > Brian Braatz wrote: > > Could it be as simple as missing the namespace on the is_sqeuence<> > > call? > > Have you tried it? If it was, I wouldn't have bothered the list ;-) > Try replacing int_<0> with int. > > Regards, > -- > Joel de Guzman > http://www.boost-consulting.com > http://spirit.sf.net > > _______________________________________________ > Unsubscribe & other changes: > http://lists.boost.org/mailman/listinfo.cgi/boost

2 1

RE: [boost] Re: [MPL] is_sequence problem
by Brian Braatz 06 May '05

06 May '05

Hehehe There are others out there either on another timezone, or not sleeping :) I put the code into VC71 and have been playing with it. I got the same error. (it WASN'T namespace weirdness with VC) (I get soo grouchy with VC I tend to blame the compiler too quickly) I then degenerated into digging through the MPL reference and trying different examples in the project. As of yet, though nothing useful to report. I think I am going to bed. I > -----Original Message----- > From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] > On Behalf Of Joel > Sent: Thursday, May 05, 2005 10:54 PM > To: boost(a)lists.boost.org > Subject: [boost] Re: [MPL] is_sequence problem > > Joel wrote: > > Brian Braatz wrote: > > > >> Could it be as simple as missing the namespace on the is_sqeuence<> > >> call? > > > > > > Have you tried it? If it was, I wouldn't have bothered the list ;-) > > Try replacing int_<0> with int. > > I think the problem is the way mpl::is_sequence is implemented. > It tries to detect the presence of a "tag" typedef and a "begin" > typedef and concludes that a type is an mpl::sequence if it > has both. I've complained a long time ago about this. I think > this behavior is error prone. It's quite easy to come up with > a situation where I have a type T with a "tag" and a "begin" > but is not an MPL sequence. There must be a better way. MPL > should not monopolize on the usage of "tag" and a "begin" > in a type. > > Anyway, in any case, is_sequence<int_<0> >::value should never > fail to compile. > > Regards, > -- > Joel de Guzman > http://www.boost-consulting.com > http://spirit.sf.net > > _______________________________________________ > Unsubscribe & other changes: > http://lists.boost.org/mailman/listinfo.cgi/boost

1 0