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

Using boost::lambda on AIX with xlC version 6
by Jerry Jeremiah 26 Sep '06

26 Sep '06

> Hello, I would appreciate any help with this. I am trying to compile this test program on AIX with xlC (VisualAge C++ Professional / C for AIX Compiler, Version 6): #include <iostream> // cout #include <vector> // vector #include <algorithm> // for_each #include "boost/lambda/lambda.hpp" using namespace boost::lambda; main() { std::vector<int> a; a.push_back(1); std::for_each(a.begin(), a.end(), std::cout << _1 << ' '); } And I get: "./boost/lambda/detail/operator_lambda_func_base.hpp", line 212.1: 1540-0219 (S) The call to "detail::select" has no best match. "./boost/lambda/detail/operator_lambda_func_base.hpp", line 212.1: 1540-1228 (I) Argument number 1 is an lvalue of type "const boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda: :bitwise_action<boost::lambda::leftshift_action>,boost::tuples::tuple<std::basi c_ostream<char,std::char_traits<char> > &,boost::lambda::lambda_functor<boost::lambda::placeholder<1> >,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,bo ost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost: :tuples::null_type,boos...". "./boost/lambda/detail/operator_lambda_func_base.hpp", line 212.1: 1540-1228 (I) Argument number 2 is an lvalue of type "int". "./boost/lambda/detail/operator_lambda_func_base.hpp", line 212.1: 1540-1228 (I) Argument number 3 is an lvalue of type "const boost::tuples::null_type". "./boost/lambda/detail/operator_lambda_func_base.hpp", line 212.1: 1540-1228 (I) Argument number 4 is an lvalue of type "const boost::tuples::null_type". "./boost/lambda/detail/operator_lambda_func_base.hpp", line 212.1: 1540-1228 (I) Argument number 5 is an lvalue of type "const boost::tuples::null_type". "./boost/lambda/detail/select_functions.hpp", line 27.1: 1540-1202 (I) No candidate is better than "boost::lambda::detail::select<boost::lambda::lambda_functor_base<boost::l ambda::bitwise_action<boost::lambda::leftshift_action>,boost::tuples::tuple<std ::basic_ostream<char,std::char_traits<char> > &,boost::lambda::lambda_functor<boost::lambda::placeholder<1> >,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,bo ost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost: :tuples::null_type,boost::tuples::null_type>...". "./boost/lambda/detail/operator_lambda_func_base.hpp", line 212.1: 1540-1231 (I) The conversion from argument number 1 to "const boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda: :bitwise_action<boost::lambda::leftshift_action>,boost::tuples::tuple<std::basi c_ostream<char,std::char_traits<char> > &,boost::lambda::lambda_functor<boost::lambda::placeholder<1> >,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,bo ost::tuples::null_type,boost::tuples::null_type,boost::tuples::nu..." uses "the identity conversion". "./boost/lambda/detail/operator_lambda_func_base.hpp", line 212.1: 1540-1231 (I) The conversion from argument number 2 to "int &" uses "the identity conversion". "./boost/lambda/detail/operator_lambda_func_base.hpp", line 212.1: 1540-1231 (I) The conversion from argument number 3 to "const boost::tuples::null_type &" uses "the identity conversion". "./boost/lambda/detail/operator_lambda_func_base.hpp", line 212.1: 1540-1231 (I) The conversion from argument number 4 to "const boost::tuples::null_type &" uses "the identity conversion". "./boost/lambda/detail/operator_lambda_func_base.hpp", line 212.1: 1540-1231 (I) The conversion from argument number 5 to "const boost::tuples::null_type &" uses "the identity conversion". "./boost/lambda/detail/select_functions.hpp", line 22.13: 1540-1202 (I) No candidate is better than "boost::lambda::detail::select<const boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda: :bitwise_action<boost::lambda::leftshift_action>,boost::tuples::tuple<std::basi c_ostream<char,std::char_traits<char> > &,boost::lambda::lambda_functor<boost::lambda::placeholder<1> >,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,bo ost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost: :tuples:...". "./boost/lambda/detail/operator_lambda_func_base.hpp", line 212.1: 1540-1231 (I) The conversion from argument number 1 to "const boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda: :bitwise_action<boost::lambda::leftshift_action>,boost::tuples::tuple<std::basi c_ostream<char,std::char_traits<char> > &,boost::lambda::lambda_functor<boost::lambda::placeholder<1> >,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,bo ost::tuples::null_type,boost::tuples::null_type,boost::tuples::nu..." uses "the identity conversion". "./boost/lambda/detail/operator_lambda_func_base.hpp", line 212.1: 1540-1231 (I) The conversion from argument number 2 to "int &" uses "the identity conversion". "./boost/lambda/detail/operator_lambda_func_base.hpp", line 212.1: 1540-1231 (I) The conversion from argument number 3 to "const boost::tuples::null_type &" uses "the identity conversion". "./boost/lambda/detail/operator_lambda_func_base.hpp", line 212.1: 1540-1231 (I) The conversion from argument number 4 to "const boost::tuples::null_type &" uses "the identity conversion". "./boost/lambda/detail/operator_lambda_func_base.hpp", line 212.1: 1540-1231 (I) The conversion from argument number 5 to "const boost::tuples::null_type &" uses "the identity conversion". "./boost/lambda/detail/operator_lambda_func_base.hpp", line 212.1: 1540-0700 (I) The previous message was produced while processing "boost::lambda::lambda_functor_base<class boost::lambda::bitwise_action<boost::lambda::leftshift_action>,class boost::tuples::tuple<boost::lambda::lambda_functor<boost::lambda::lambda_functo r_base<boost::lambda::bitwise_action<boost::lambda::leftshift_action>,boost::tu ples::tuple<std::basic_ostream<char,std::char_traits<char> > &,boost::lambda::lambda_functor<boost::lambda::placeholder<1> >,boost::tuples::null_type,boost::tuples::null_t...". "./boost/lambda/detail/lambda_functors.hpp", line 145.3: 1540-0700 (I) The previous message was produced while processing "boost::lambda::lambda_functor<class boost::lambda::lambda_functor_base<boost::lambda::bitwise_action<boost::lambda: :leftshift_action>,boost::tuples::tuple<boost::lambda::lambda_functor<boost::la mbda::lambda_functor_base<boost::lambda::bitwise_action<boost::lambda::leftshif t_action>,boost::tuples::tuple<std::basic_ostream<char,std::char_traits<char> > &,boost::lambda::lambda_functor<boost::lambda::placeholder<1> >,boost::tuples::null_ty...". "/usr/vacpp/include/algorithm", line 77.13: 1540-0700 (I) The previous message was produced while processing "std::for_each<std::_Ptrit<int,long,int *,int &,int *,int &>,boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lamb da::bitwise_action<boost::lambda::leftshift_action>,boost::tuples::tuple<boost: :lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::bitwi se_action<boost::lambda::leftshift_action>,boost::tuples::tuple<std::basic_ostr eam<char,std::char_traits<char> > &,boost::lambda::lambda_functor<...". "test.cpp", line 13.3: 1540-0700 (I) The previous message was produced while processing "main()".

2 2

[asio] error code 11001
by Christian Henning 26 Sep '06

26 Sep '06

Hi there, I'm having problems to figure out what error code 11001 means. I have an boost::asio::error exception that is thrown inside tcp::resolver::resolve( query ) . So how can I translate this error code into something descriptive. Thanks ahead, Christian

1 1

[asio] demultiplexing non-socket file descriptors
by Bill Somerville 26 Sep '06

26 Sep '06

Hi Having a look at asio as a possible solution for a cleanup of an existing app. It would be nice to extend asio to include non-socket file descriptors. I realise that this would not be portable to Windows, but does asio provide extension points to add this functionality, also adding PF_LOCAL sockets would be handy as well although these could be switched to a PF_INET implementation with an acceptable performance penalty. Has anyone experimented with extensions like these? TIA -- Bill Somerville This message has been scanned by MailController - www.MailController.altohiway.com

1 0

[Boost Test] 1.35 - setting up VC 7 IDE to link with Boost.Test
by Robert Ramey 26 Sep '06

26 Sep '06

Using VC 7.1 I have a VC Solution with all my test programs. These use the serialization library and boost test - test_exec_monitor. I've recently wanted to make some changes in 1.35 and now none of my projects link anymore. They build with bjam but I can't get them linked with VC 7 IDE. I don't have autolink suppressed. There is no message indicating that it can't find file test.....lib. What I get is undefined symbols. This i od to me as I don't use any symbosl unit_test .... I've also tried including the library unit_test_framework. That doesn't seem to help either. Any suggestions would be appreciated. Robert Ramey test_simple_class.obj : error LNK2019: unresolved external symbol "void __cdecl boost::test_tools::tt_detail::check_impl(class boost::test_tools::predicate_result const &,class boost::basic_wrap_stringstream<char> &,class boost::unit_test::basic_cstring<char const >,unsigned int,enum boost::test_tools::tt_detail::tool_level,enum boost::test_tools::tt_detail::check_type,unsigned int,...)" (?check_impl@tt_detail@test_tools@boost@@YAXABVpredicate_result@23@AAV?$basic_wrap_stringstream@D@3@V?$basic_cstring@$$CBD@unit_test@3@IW4tool_level@123@W4check_type@123@IZZ) referenced in function "int __cdecl test_main(int,char * * const)" (?test_main@@YAHHQAPAD@Z) test_simple_class.obj : error LNK2019: unresolved external symbol "public: void __thiscall boost::unit_test::unit_test_log_t::set_checkpoint(class boost::unit_test::basic_cstring<char const >,unsigned int,class boost::unit_test::basic_cstring<char const >)" (?set_checkpoint@unit_test_log_t@unit_test@boost@@QAEXV?$basic_cstring@$$CBD@23@I0@Z) referenced in function "int __cdecl test_main(int,char * * const)" (?test_main@@YAHHQAPAD@Z) test_simple_class.obj : error LNK2001: unresolved external symbol "public: virtual void __thiscall boost::unit_test::unit_test_log_t::exception_caught(class boost::execution_exception const &)" (?exception_caught@unit_test_log_t@unit_test@boost@@UAEXABVexecution_exception@3@@Z) test_simple_class.obj : error LNK2001: unresolved external symbol "public: virtual void __thiscall boost::unit_test::unit_test_log_t::assertion_result(bool)" (?assertion_result@unit_test_log_t@unit_test@boost@@UAEX_N@Z) test_simple_class.obj : error LNK2001: unresolved external symbol "public: virtual void __thiscall boost::unit_test::unit_test_log_t::test_unit_aborted(class boost::unit_test::test_unit const &)" (?test_unit_aborted@unit_test_log_t@unit_test@boost@@UAEXABVtest_unit@23@@Z) test_simple_class.obj : error LNK2001: unresolved external symbol "public: virtual void __thiscall boost::unit_test::unit_test_log_t::test_unit_skipped(class boost::unit_test::test_unit const &)" (?test_unit_skipped@unit_test_log_t@unit_test@boost@@UAEXABVtest_unit@23@@Z) test_simple_class.obj : error LNK2001: unresolved external symbol "public: virtual void __thiscall boost::unit_test::unit_test_log_t::test_unit_finish(class boost::unit_test::test_unit const &,unsigned long)" (?test_unit_finish@unit_test_log_t@unit_test@boost@@UAEXABVtest_unit@23@K@Z) test_simple_class.obj : error LNK2001: unresolved external symbol "public: virtual void __thiscall boost::unit_test::unit_test_log_t::test_unit_start(class boost::unit_test::test_unit const &)" (?test_unit_start@unit_test_log_t@unit_test@boost@@UAEXABVtest_unit@23@@Z) test_simple_class.obj : error LNK2001: unresolved external symbol "public: virtual void __thiscall boost::unit_test::unit_test_log_t::test_aborted(void)" (?test_aborted@unit_test_log_t@unit_test@boost@@UAEXXZ) test_simple_class.obj : error LNK2001: unresolved external symbol "public: virtual void __thiscall boost::unit_test::unit_test_log_t::test_finish(void)" (?test_finish@unit_test_log_t@unit_test@boost@@UAEXXZ) test_simple_class.obj : error LNK2001: unresolved external symbol "public: virtual void __thiscall boost::unit_test::unit_test_log_t::test_start(unsigned long)" (?test_start@unit_test_log_t@unit_test@boost@@UAEXK@Z) MSVCRTD.lib(crtexe.obj) : error LNK2019: unresolved external symbol _main referenced in function _mainCRTStartup

3 3

autolink include guard ?
by Robert Ramey 26 Sep '06

26 Sep '06

I notice that when my tests build I get Linking to lib file: libboost_serialization-vc71-mt-gd-1_35.lib Linking to lib file: libboost_serialization-vc71-mt-gd-1_35.lib I was curious as to why I go two such messages. Looking at auto_link.hpp I see that there is no include guard no a #pragma once. Is there a reason for this? Robert Ramey

2 1

Re: [Boost-users] [iostreams] Implementing a block cipher as a filter
by Pfligersdorffer, Christian 26 Sep '06

26 Sep '06

Hello all! Seems I am the first one to reply to my own post :-) I am not so much surprised however, since this stuff is kinda weird and complicated. Nevertheless I got some news for you: after replacing the gzip- with bzip2-compression filters everything worked fine!! This means there is some (very subtle) bug or incompatibility in the gzip filters, which I of course did not expect (but rather was looking in my code of course). For the protocoll: gzip_decompressor raises a gzip_error exception with internal error_ = -3 when reaching the end of the stream. Unfortunately this behaviour could not be reproduced without actual encrypting/decrypting. Simply doing a null-transformation by replacing encrypt() and decrypt() with memcpy() does not yield the error. I did some tests: reading a file, writing it to a filtering_ostream using filter X into some file, again reading through filtering_istream using Y and comparing with the original file. X = block_crypter, Y = block_crypter ok, identity X = gzip_compressor, Y = gzip_decompressor ok, identity X = block_crypter|bzip2_compressor, Y = block_crypter|bzip2_decompressor ok, identity X = block_crypter|gzip_compressor, Y = block_crypter|gzip_decompressor error, see above and now get yourself a good seat: X = gzip_compressor|block_crypter, Y = gzip_decompressor|block_crypter ok, identity Of course compressing an encrypted file is not the same as encrypting the compressed file, which is much faster and results in smaller files. So I tried this just to see what happens the other way round. Throughout the test I used file_sink and file_source in binary-mode as devices. Have fun fixing this ;-) -- Christian Pfligersdorffer Dipl.-Ing. Bakk.rer.nat. Software Engineering EOS GmbH - Electro Optical Systems Robert-Stirling-Ring 1 D-82152 Krailling / Munich Phone +49 89 893 36-229 Fax +49 89 893 36-287 christian.pfligersdorffer(a)eos.info http://www.eos.info

1 0

[smart_ptr] comparison operators: shared_ptr == weak_ptr?
by Matt.Sullivan＠leica-geosystems.com 26 Sep '06

26 Sep '06

Hi, Probably a newbie question, but what's the best way to test if a shared_ptr and weak_ptr point to the same thing? My current code uses: if (shared_ptr != weak_ptr.lock()) but it feels wrong to create a temporary with some small locking overhead - even though I realise it will make absolutely no difference to performance. So, my question is really why is there no operator==(shared_ptr, weak_ptr)? Google provided little explanation other than this: http://std.dkuug.dk/jtc1/sc22/wg21/docs/papers/2004/n1590.html which approaches the subject but isn't exactly authoritative. thanks, Matt

3 4

boost serialization
by Anna Kloper 25 Sep '06

25 Sep '06

Hi all, I'm new to BOOST and need help with this kind of problem of pointers serialization: class A{ public: A(int *anInt):m_pi(anInt){} ~A(){} private: int *m_pi; }; class B{ public: B(int *anInt):m_a1(anInt),m_a2(anInt){} ~B(){} private: A m_a1; A m_a2; }; int main() { int i=1; B b(&i); //serialize b i=2; //serialize b //de-serialize b expected i = 1 and b.m_a1=b.m_a2=1 //de-serialize b expected i = 2 and b.m_a1=b.m_a2=2 } Now, assuming that there are serialization functions for class A and B I'd like to serialize object b swice with track never so that when de-serializing b I'd like b to contain a pointer to the location of i. The problem is that when I de-serializing b I notice that b doesn't pointer to the location of i anymore but to another location. I need this for serializing of communication, so I need to save all the data trough a pointer and read the data back step by step for preprocessing to the same location in the memory. Is there anything I can do to overcome this problem with pointers? Thank you in advance, Anna. --------------------------------- Do you Yahoo!? Everyone is raving about the all-new Yahoo! Mail.

2 1

newbie [boost::test] linking in MSVC6
by Brian Hall 25 Sep '06

25 Sep '06

I have been using boost and STLPort for sometime and I have built up unit tests for my projects that have worked fine up until now. However, I've been lazy and used the #include unit_test_framework.hpp route instead linking to libraries. Now I'm stuck. My tests won't compile with STLPort 5.0.x, apparently because the complier needs more memory (I'm using MS VC++6(SP5) and I've set the complier option /Zm to extend to its maximum). So I decided to build the boost libraries (boost 1_33_1). Unfortunately, now I can't get my testing code to link with these libraries! Could anyone tell me which of the following I should be linking to (I am building in 'release' mode with multithreading)? libboost_unit_test_framework-vc6-mt-gdp-1_33_1.lib libboost_unit_test_framework-vc6-mt-gdp.lib libboost_unit_test_framework-vc6-mt-p-1_33_1.lib libboost_unit_test_framework-vc6-mt-p.lib libboost_unit_test_framework-vc6-mt-sgdp-1_33_1.lib libboost_unit_test_framework-vc6-mt-sgdp.lib libboost_unit_test_framework-vc6-mt-sp-1_33_1.lib libboost_unit_test_framework-vc6-mt-sp.lib In fact, I've tried them all without success. Here is an example error message: libboost_unit_test_framework-vc6-mt-sp-1_33_1.lib(framework.obj) : error LNK2001: unresolved external symbol "class boost::unit_test::test_suite * __cdecl init_unit_test_suite(int,char * * const)" (?init_unit_test_suite@@YAPAVtest_suite@unit_test@boost@@HQAPAD@Z) Release/mst_gum_tree_real_dev.exe : fatal error LNK1120: 1 unresolved externals Error executing link.exe. Also, I simply removed the #include of unit_test_framework.hpp in my original source code. Is that correct? The remaining includes are: unit_test.hpp and floating_point_comparison.hpp. As an alternative to linking to the libraries, I have tried to include the source files in my project, as suggested in the unit test documentation, but that doesn't work either! The documentation does not appear to be up to date. What is a poor boy to do?!! Please give me some ideas

3 3

reference in new- and old-style iterators
by Jens Theisen 25 Sep '06

25 Sep '06

Hello, I'm wondering what the reference member in the iterator_traits of an iterator is required to be. I couldn't find any requirement at all in the C++98 standard, and more surprisingly, I can't see any requirement in the new iterator proposal either. In particular, operator* does not seem to be required to return the iterator_traits< Iterator >::reference for lvalue iterators. At one point, however, the proposal suggests that this was the intention: "...would have a return type of reference; the same as operator*." where reference has a font style indicating that it's the iterator_traits's notion of reference. I'm looking at the proposal version currently published along in the documentation of the boost iterator library. So my questions: - Am I right in my suspicion that in the STL, the reference iterator_trait is entirely useless if taken strictly? - Should the proposal not better require the reference to match with operator*'s return type for lvalue iterators? If not, what's its use? - Is this off-topic here? :) Regards, Jens

2 1