- Boost - lists.preview.boost.org

[preprocessor] BOOST_PP_IS_UNARY for Borland
by Daniel James 16 Aug '04

16 Aug '04

I've written an implementation of BOOST_PP_IS_UNARY which works for Borland, and hopefully any other preprocessors which the current implementation doesn't. It is: #define EAT2(x,y) #define IS_UNARY_CHECK(x) ~, 1 BOOST_PP_RPAREN() \ EAT2 BOOST_PP_LPAREN() ~ #define IS_UNARY(x) IS_UNARY_1(IS_UNARY_CHECK x, 0) #define IS_UNARY_1(x, y) IS_UNARY_2(x, y) #define IS_UNARY_2(x, y) y For a non-unary argument, the expansion is simple: IS_UNARY(x) => IS_UNARY_1(IS_UNARY_CHECK x, 0) => IS_UNARY_2(IS_UNARY_CHECK x, 0) => 0 For a unary argument, it expands like this (I might have got the expansion order slightly wrong but, hopefully, this illustrates how it works): IS_UNARY((x)y) => IS_UNARY_1(IS_UNARY_CHECK(x)y), 0) => IS_UNARY_2(~, 1 BOOST_PP_RPAREN() EAT2 BOOST_PP_LPAREN() ~y, 0) => IS_UNARY_2(~, 1) EAT2(~y, 0) => 1 The same technique can be used for BOOST_PP_IS_NULLARY and BOOST_PP_IS_BINARY. So, if this is used as for borland, could these marcros be made 'public'? Also, with a full working BOOST_PP_IS_UNARY, I think it should be possible to make BOOST_PP_SEQ_NIL act as an empty sequence, if I write a patch to do that would it be accepted? Daniel

2 4

Boost License Permission
by Cromwell Enage 16 Aug '04

16 Aug '04

I, Cromwell Enage, give permission for all my past, present, and future contributions to Boost to be distributed under the terms of the Boost Software License Version 1. _______________________________ Do you Yahoo!? Express yourself with Y! Messenger! Free. Download now. http://messenger.yahoo.com

2 1

Boost License Permission
by Bruce Barr 16 Aug '04

16 Aug '04

I, Bruce Barr, give permission for all my contributions to Boost to be moved to the Boost Software License Version 1.

1 0

boost-python vector processing
by Neal D. Becker 16 Aug '04

16 Aug '04

I've posted a few times to the python-c++ list, but maybe this subject is of more general interest so I'm posting here. I'm interested in interfacing c++ algorithms (primarily for signal processing) with python via boost-python. I'm trying to develop a library of algorithms, but first the proper infrastructure is needed. Specifically, a choice of underlying container to be used for passing vectors between python and c++. Vector processing is in my view one of the primary interests for boost-python. By processing vectors, the overhead involved with python and the python-c++ interface becomes acceptable. I believe a suitable container for interfacing between python and c++ is of fundamental interest to the boost-python community. I'm sure there must be a lot of interest in this subject. I have tried to investigate 3 candidates. 1) std::vector 2) ublas 3) numarray So far the results are: 1) std::vector - pros: universal availability easily understood supports required operations (insert, erase...) vector_indexing_suite already implemented (could be optimized more) cons: lacks vector arithmetic - but I just implemented this and it isn't difficult even for an amateur like myself 2) ublas: pros: already has vector arithmetic cons: lacks required operations (e.g., erase) no indexing_suite (see above) 3) numarray pros: ? cons: I had a hard time finding documentation. Heavy-weight interface -> high learning curve Summary: It appears that std::vector is a good choice. Ublas might be better in the future, but at present it lacks some required functionality. A ublas vector does not fulfill all the requirements of Sequence. This topic is known to ublas developers and may be addressed in the future. Here is an initial version of vector arithmetic for std::vector:

1 0

enabling ADL even with namespace qualification
by Thorsten Ottosen 16 Aug '04

16 Aug '04

Dear All, I've put meself in a funny situation. I have a class with an begin() end() members, but I wan't to call boost::begin() boost::end() without the boost:: prefix so ADL is functional. Can that be done? Thanks Thorsten

7 25

random_test, GCC and minmax macros
by Michael Stevens 16 Aug '04

16 Aug '04

The 'random_test' has been failing on GCC-3.3 for quite some time... Looking a bit deeper the failure was rather nasty resulting in a infinite recursion. A lot of waist CPU and memory usage when running regression tests! The problem is GCC-3.3 specific and cause by a compiler bug. It was inadvertently introduced by Eric minmax workarounds. Specificly the 'max' member functions of class ruetti_gen in "random_test.cpp" and class rand48 in "linear_congruential.hpp" were defined: result_type max BOOST_PREVENT_MACRO_SUBSTITUTION () const { return (std::numeric_limits<result_type>::max)(); } Amazingly these are recursing, with max calling itseld rather then the correct max from numeric_limits! I have committed a fix which uses a different syntax thus: result_type max BOOST_PREVENT_MACRO_SUBSTITUTION () const { return std::numeric_limits<result_type>::max BOOST_PREVENT_MACRO_SUBSTITUTION (); } Eric, is this correct from a minmax macro point of view? -- ___________________________________ Michael Stevens Systems Engineering Navigation Systems, Estimation and Bayesian Filtering http://bayesclasses.sf.net ___________________________________

2 1

IMPORTANT: PLEASE READ
by John Maddock 16 Aug '04

16 Aug '04

Sorry for the loud subject line, but there are still a shockingly large number of *source files* with no copyright/licence information in current cvs. Please take a chance to scan through the file list below and add your moniker to any that belong to you - no-one can do this for you, if one of these files is your work, it's up to you to own up to it, no else can assign the copyright on your behalf. John. HEADERS: ~~~~~~~~ boost/format/detail/unset_macros.hpp boost/iterator/detail/categories.hpp boost/iterator/new_iterator_tests.hpp boost/pending/container_traits.hpp boost/pending/cstddef.hpp boost/pending/detail/disjoint_sets.hpp boost/pending/detail/property.hpp boost/pending/fenced_priority_queue.hpp boost/pending/fibonacci_heap.hpp boost/pending/property.hpp boost/pending/queue.hpp boost/pending/stringtok.hpp boost/utility/detail/result_of_iterate.hpp TEST FILES: ~~~~~~~~~ libs/any/any_test.cpp libs/format/example/sample_userType.cpp libs/graph/example/adjacency_list_io.cpp libs/graph/example/graph_property.cpp libs/graph/example/iohb.c libs/graph/example/iohb.h libs/graph/example/subgraph_properties.cpp libs/graph/src/graphviz_digraph_parser.hpp libs/graph/src/graphviz_graph_parser.hpp libs/graph/src/yystype.h libs/graph/test/bellman-test.cpp libs/graph/test/bidir_remove_edge.cpp libs/graph/test/subgraph.cpp libs/graph/test/transitive_closure_test2.cpp libs/iterator/example/permutation_iterator_example.cpp libs/iterator/example/reverse_iterator.cpp libs/iterator/test/is_convertible_fail.cpp libs/iterator/test/iterator_adaptor_cc.cpp libs/iterator/test/lvalue_concept_fail_expected.cpp libs/multi_array/test/generative_tests.hpp libs/property_map/example3.cpp libs/python/example/getting_started1.cpp libs/python/example/getting_started2.cpp libs/python/pyste/tests/abstract_test.h libs/python/pyste/tests/add_test.h libs/python/pyste/tests/basic.cpp libs/python/pyste/tests/basic.h libs/python/pyste/tests/code_test.h libs/python/pyste/tests/enums.h libs/python/pyste/tests/header_test.h libs/python/pyste/tests/inherit.cpp libs/python/pyste/tests/inherit.h libs/python/pyste/tests/inherit2.h libs/python/pyste/tests/inherit3.h libs/python/pyste/tests/inherit4.h libs/python/pyste/tests/nested.cpp libs/python/pyste/tests/nested.h libs/python/pyste/tests/opaque.h libs/python/pyste/tests/operators.cpp libs/python/pyste/tests/operators.h libs/python/pyste/tests/smart_ptr.h libs/python/pyste/tests/templates.h libs/python/pyste/tests/vars.cpp libs/python/pyste/tests/vars.h libs/python/pyste/tests/virtual.cpp libs/python/pyste/tests/virtual.h libs/python/pyste/tests/virtual2.h libs/python/pyste/tests/wrappertest.h libs/python/pyste/tests/wrappertest_wrappers.h libs/python/src/dict.cpp libs/python/src/str.cpp libs/python/test/ben_scott1.cpp libs/python/test/bienstman1.cpp libs/python/test/bienstman2.cpp libs/python/test/bienstman3.cpp libs/python/test/destroy_test.cpp libs/python/test/dict.cpp libs/python/test/exception_translator.cpp libs/python/test/indirect_traits_test.cpp libs/python/test/map_indexing_suite.cpp libs/python/test/multi_arg_constructor.cpp libs/python/test/pickle2.cpp libs/python/test/pickle3.cpp libs/python/test/pickle4.cpp libs/python/test/pointer_type_id_test.cpp libs/python/test/properties.cpp libs/python/test/register_ptr.cpp libs/python/test/select_arg_to_python_test.cpp libs/python/test/select_from_python_test.cpp libs/python/test/slice.cpp libs/python/test/str.cpp libs/python/test/string_literal.cpp libs/python/test/submod_subclass_api.cpp libs/python/test/vector_indexing_suite.cpp libs/utility/ref_ct_test.cpp libs/utility/ref_test.cpp

4 7

Boost License Permission
by Kresimir Fresl 16 Aug '04

16 Aug '04

John Maddock wrote: > Hi, if you are receiving this message it is because there are one or more > files in the Boost C++ libraries that contain your copyright declaration. Yes, I give permission for all my contributions to Boost to be moved to the Boost Software License Version 1". Kresimir Fresl

2 1

date_time test failure
by Rob Lievaart 16 Aug '04

16 Aug '04

L.S. The date_time test testfiletime_functions is failing on mingw 3.2 and 3.4 and on vc8.0 with the same error: ../libs/date_time/test/posix_time/testfiletime_functions.cpp:26: call of overloaded `pow(int, int)' is ambiguous The line in questions is: static_cast<int>(std::pow(10, time_duration::num_fractional_digits() - 3)); I changed the 10, to 10.0, to solve the ambiguity, locally and now the test compiles and passes. I attached a patch. Kind regards, Rob.

2 1

boost.regex v4 compilation issue on VC++ 6 (and correction suggestion)
by Baptiste Lepilleur 16 Aug '04

16 Aug '04

Compilation of boost regex v4 (from the CVS) fails with the following error under VC6: f:\projects\cpptool\cppparser_dependencies\cppparser\include\boost\regex\v4\ basic_regex.hpp(221) : error C2143: syntax error : missing ',' before '<' f:\projects\cpptool\cppparser_dependencies\cppparser\include\boost\regex\v4\ basic_regex.hpp(298) : see reference to class template instantiation 'boost::reg_expression<charT,traits,Allocator>' being compiled Looking at the sources (inside template reg_expression definition): bool BOOST_REGEX_CALL operator==(const reg_expression& e)const { return compare(e) == 0; } bool operator != (const basic_regex<charT, traits, Allocator>& e) // <<< *** error here *** { return compare(e) != 0; } basic_regex is defined later in the source, hence the compilation error. Also, the fact that operator == & != have different prototype is very suspicious... Using reg_expression instead or basic_regex would fix the error. Baptiste.

2 1