April 2005 - Boost-users - lists.preview.boost.org

Re: Another KCC issue...
by Stephen Gross 07 Apr '05

07 Apr '05

>> When including "boost/iterator/indirect_iterator.hpp", I get: >> >> "/usr/local/sagedev/apis/include/boost_1_32_0/boost/detail/is_incrementa >> ble.hpp", >> line 56: error: >> >> expression must have arithmetic, enum, or pointer type >> >> BOOST_STATIC_CONSTANT( >> >> ^ >> >> "/usr/local/sagedev/apis/include/boost_1_32_0/boost/detail/is_incrementa >> ble.hpp", > > Please try compiling with -DBOOST_NO_INCLASS_MEMBER_INITIALIZATION and let me know if that helps. If that works, I'll know just what fix to make. Alas, it still produces the same error message... --Steve

4 4

boost::filesystem -- "invalid name" error
by Matthias Kaeppler 07 Apr '05

07 Apr '05

Hello, I'm using the boost filesystem library to implement a gtkmm widget which represents a view on the local filesystem. However, while browsing through the files (they are displayed in a TreeView), the application now and then crashs with the following error message: [mkay][~/devel/projects/fb]: ./fb.elf glibmm-ERROR **: unhandled exception (type std::exception) in signal handler: what: boost::filesystem::path: invalid name "lost+found" in path: "lost+found" aborting... Aborted Of course the path names differ, but lost+found is a typical directory found on Linux machines, so this is a representative example for the error I guess. I have no idea what is causing this, any ideas?

1 1

string_algo split iterator
by Martin 07 Apr '05

07 Apr '05

I have a problem with the string_algo split_iterator. Background is that I have a function that finds a string in a range of other strings. template <typename CollectionT, typename RangeT, typename PredicateT> inline unsigned int find_first_in_range(const CollectionT& Input, const RangeT& Search, PredicateT Comp) { typename boost::range_const_iterator<RangeT>::type first = boost::begin(Search), last = boost::end(Search); for (unsigned int index = 1; first != last; ++first, ++index) if (Comp(Input, *first)) return index; return 0; } This function works fine if I send in a std::vector like std::vector<std::string> vec; vec.push_back("Item1"); vec.push_back("Item2"); find_first_in_range(std::string("Item2"), vec, equals_pred()); equals_pred is just a functor version of the equals predicate that don't require the template arguments struct equals_pred { template<typename T1, typename T2> bool operator()(const T1& arg1, const T2& arg2) const { return boost::equals (arg1, arg2); } }; But if I do the same thing with the split_iterator find_first_in_range( std::string("item2"), make_split_iterator( std::string("Item1,Item2,Item3,Item4"), first_finder(",") ), iequals_pred() ); I get an error (VC70) boost\range\detail\const_iterator.hpp(34) : error C2039: 'const_iterator' : is not a member of 'boost::algorithm::split_iterator<IteratorT>' with [ IteratorT=boost::range_result_iterator<std::basic_string<char,std::char_traits< char>,std::allocator<char>>>::type ] boost\range\detail\const_iterator.hpp(118) : see reference to class template instantiation 'boost::range_detail::range_const_iterator_<T>::pts<C>' being compiled with [ T=boost::range_detail::std_container_, C=boost::algorithm::split_iterator<boost::range_result_iterator<std::basic_stri ng<char,std::char_traits<char>,std::allocator<char>>>::type> ]

1 1

How to install only a few libraries
by Marcel Loose 07 Apr '05

07 Apr '05

Hi, Maybe I haven't searched well enough in the installation docs, but I couldn't find an answer to the following. Is is possible to install only one or two libraries. For example, suppose I only want to use boost::smart_ptr. How can I arrange that only the files I really need are being downloaded and installed? Nothing more, nothing less? I've seen the option to bjam --with-<library>, but that only works for libraries, not for header files. When I do an install, I still get all the header files copied to my install directory. Regards, Marcel Loose.

2 1

question of program_options : validator function
by Suresh T 07 Apr '05

07 Apr '05

hello boosters, An old boost library that i was using, provided a validator function (in the value_sematic.hpp file) that could be used for creating user defined parsers and it was handy The signature was something like : void validator<T, char>::operator() (any& v, const std::vector<std::string>& xs); I had a working code that used it and when i tried to recompile my old code with a new boost release it did not compile. I then realized that the validator function is no longer there. Can someone please let me know if this has been substituted by something else (what?) or what i would have to use now in such cases. Thanks in advance. --------------------------------------------------------------------------------------------------------- Warm Regards, Suresh.T ---------------------------------------------------------------------------------------------------------

2 2

minor "enhancement" (?) to boost/test/auto_unit_test.hpp
by Oliver Schoenborn 07 Apr '05

07 Apr '05

I like the auto test feature of Boost.test because it's quick and simple to use. Unfortunately, when BOOST_AUTO_TEST_MAIN is #define'd, the auto suite name is hardcoded. Changing auto_unit_test.hpp so user can, *if desired*, change it, can be done with following patch: $ diff -u ~/downloads/boost_1_32_0/boost/test/auto_unit_test.hpp /c/Boost/inclu de/boost-1_32/boost/test/auto_unit_test.hpp --- boost_1_32_0/boost/test/auto_unit_test.hpp Mon Jul 19 09:12:40 2004 +++ /c/Boost/include/boost-1_32/boost/test/auto_unit_test.hpp Wed Apr 6 12:46:07 2005 @@ -19,6 +19,10 @@ // Boost.Test #include <boost/test/unit_test.hpp> +#ifndef BOOST_AUTO_TEST_SUITE_NAME +#define BOOST_AUTO_TEST_SUITE_NAME "Auto Unit Test" +#endif + // ************************************************************************** // // ************** auto_unit_test_registrar ************** // // ************************************************************************** // @@ -27,10 +31,17 @@ namespace unit_test { namespace ut_detail { +inline const char* +suiteName(const char* name = NULL) +{ + return name ? name : BOOST_AUTO_TEST_SUITE_NAME; +} + inline boost::unit_test::test_suite* auto_unit_test_suite() { - static boost::unit_test::test_suite* inst = BOOST_TEST_SUITE( "Auto Unit Test" ); + static boost::unit_test::test_suite* inst + = BOOST_TEST_SUITE( suiteName(BOOST_AUTO_TEST_MAIN) ); return inst; } This allows you to do any of: 1) Like current (default suite name is "Auto Unit Test"): #define BOOST_AUTO_TEST_MAIN 2) Change from default suite name to what you want: #define BOOST_AUTO_TEST_MAIN "Your suite name" 3) Same, but doesn't "overload" the BOOST_AUTO_TEST_MAIN: #define BOOST_AUTO_TEST_MAIN #define BOOST_AUTO_TEST_SUITE_NAME "Your suite name" This enhancement maintains backward compatibility but allows automated test suites to be distinguishable. Oliver

2 1

Regex trouble (compiling a simple expression fails)
by Bogdan Harjoc 06 Apr '05

06 Apr '05

Hi, I've looked at replacing the pcre library with boost regex,mainly because the C++ interface seems more usable than the plain C functions from pcre. The trouble is, I'm wasn't able to adjust regular expressions to the format boost regex uses. For instance, while pcre and others seem to like the expression "\?", boost throws bad_expression. The same goes for "\(", "\+" and others I'm using. So, I suppose the question is, is there a flag that can be set for the regex constructor that enables compatibility with a certain regex specification or should the regexp I gave as an example not be accepted ? Any hints would be kindly appreciated. Thanks, Bogdan.

3 3

is_same_impl
by Gottlob Frege 06 Apr '05

06 Apr '05

template <typename T> ::boost::type_traits::yes_type BOOST_TT_DECL is_same_tester(T*, T*); ::boost::type_traits::no_type BOOST_TT_DECL is_same_tester(...); template <typename T, typename U> struct is_same_impl { static T t; static U u; BOOST_STATIC_CONSTANT(bool, value = (::boost::type_traits::ice_and< (sizeof(type_traits::yes_type) == sizeof(detail::is_same_tester(&t,&u))), (::boost::is_reference<T>::value == ::boost::is_reference<U>::value), (sizeof(T) == sizeof(U)) >::value)); }; Would it be any better to do is_same_tester with just one arg, like this: template <typename T> ::boost::type_traits::yes_type BOOST_TT_DECL is_same_tester(T*); template <typename T> ::boost::type_traits::no_type BOOST_TT_DECL is_same_tester(...); and then the call is:. (sizeof(type_traits::yes_type) == sizeof(detail::is_same_tester<T>(&u))), (and then not need a 'static T t' at all?) And does it make any difference to declare the U as a pointer: static U *u; // and/or leave off the static and then not pass it in by address: (sizeof(type_traits::yes_type) == sizeof(detail::is_same_tester<T>(u))), Or not bother with a U at all, but just cast 0 into a U*: (sizeof(type_traits::yes_type) == sizeof(detail::is_same_tester<T>(static_cast<U *>(0)))), Or does none of it really make a difference? And while I am at it, what would the value of 'same' be: struct A { int x; }; struct B : A; static bool same = boost::type_traits::is_same<A, B>::value; I suspect same == true, as B is castable to an A, and sizeof(B) == sizeof(A). checking both is_same_tester<T>(u) and is_same_tester<U>(t) might be better?

3 2

[Regex] Is it possible to assign an alias to a subexpression (to use later instead of its index)?
by jordi 06 Apr '05

06 Apr '05

Hi, I would like to know if it's possible to assign an alias/name to a sub-expression. When using short regex there is no problem nor confusion but when using a long regex then I get lost looking at the correct index to use. It would be much easier if I can assign an alias. So, instead to use a regex like this: "\s*(\d+)\s+(\d+)\s+(\d+)\s+" I would like to be able to use something like: "\s*([$VALUE1]\d+)\s+([$VALUE2]\d+)\s+([$VALUE3]\d+)\s+" I don't know if this feature exists in regex but I haven't found it but maybe I dind't know where to find... Thanks in advance, Jordi

5 9

mpl, for_each, KCC incompatibility
by Stephen Gross 06 Apr '05

06 Apr '05

Hi all... I have a file that includes 'boost/mpl/for_each.hpp'. When compiled with KCC 4.0 on an x86 machine running Redhat Linux (8, I think), I get the following compile error: "boost_1_32_0/boost/mpl/aux_/preprocessed/no_ttp/arg.hpp", line 27: error: more than one instance of overloaded function "boost::mpl::assert_not_arg" matches the argument list: function template "mpl_::assert_not_arg(void (*)(Pred), mpl_::assert_arg_pred<Pred>::type)" function template "mpl_::assert_not_arg(void (*)(Pred), mpl_::assert_arg_pred_not<Pred>::type)" argument types are: (void (*)(boost::mpl::is_na<U1>), int) BOOST_MPL_AUX_ASSERT_NOT_NA(type); Any ideas? Troubleshooting this one is a bit beyond my abilities... Thanks, --Steve (sgross(a)darwin.cwru.edu)

2 1