- Boost-users - lists.boost.org

Re: [Boost-users] [Proto] callable_context
by Hossein Haeri 05 Jan '11

05 Jan '11

Dear Erik, > > lit(1) >> &f >> &g >> &h > > > > So, what about this new one in Proto? > > Yes, that should be doable. OK, that's good news. Here is my attempt to get it done (assuming that we only pipe integers into series of functions): struct FuncStreamCtx: callable_context<const FuncStreamCtx> { FuncStreamCtx() {} typedef int result_type; int operator () (tag::terminal, int i) const {return i;} template<typename L, typename R> int operator () (tag::shift_right, const L& l, const R& r) const { int arg = eval<L, const FuncStreamCtx>(l, *this);//*** int (*f) (int) = value(r); return f(arg); } }; (I know you told me that contexts make life hard. But, I'm not still comfortable with transforms...) Now, when I try to compile this code (GCC 4.5.1, MinGW32, WinXP, SP3), I get the error in the P.S. for trying it with: cout << eval(lit(51) >> &plus2, ctx); >From what I understand, from line ***, GCC mistakenly thinks that I'm trying to instantiate eval<> and fails to find an appropriate ctor -- it only nags about finding the default and the copy one. Strangely enough, when I remove the template arguments from the same line, I get: error: missing template arguments before '(' token Any ideas? TIA, --Hossein P.S. -------------- Build: Debug in ProtoGame3 --------------- Compiling: main.cpp D:\My Documents\My Programmes\Tutorial\Proto\ProtoGame3\main.cpp: In member function 'int FuncStreamCtx::operator()(boost::proto::tag::shift_right, const L&, const R&) const [with L = boost::proto::utility::literal<const int&, boost::proto::domainns_::default_domain>, R = boost::proto::exprns_::expr<boost::proto::tag::terminal, boost::proto::argsns_::term<int (* const&)(int)>, 0l>]': D:\Sources\Boost\boost_1_42_0/boost/proto/context/callable.hpp:313:21: instantiated from 'boost::proto::context::callable_eval<Expr, Context, 2l>::result_type boost::proto::context::callable_eval<Expr, Context, 2l>::operator()(Expr&, Context&) const [with Expr = const boost::proto::exprns_::expr<boost::proto::tag::shift_right, boost::proto::argsns_::list2<const boost::proto::utility::literal<const int&, boost::proto::domainns_::default_domain>&, boost::proto::exprns_::expr<boost::proto::tag::terminal, boost::proto::argsns_::term<int (* const&)(int)>, 0l> >, 2l>, Context = const FuncStreamCtx, boost::proto::context::callable_eval<Expr, Context, 2l>::result_type = int]' D:\Sources\Boost\boost_1_42_0/boost/proto/eval.hpp:100:62: instantiated from 'typename boost::proto::result_of::eval<Expr, Context>::type boost::proto::eval(Expr&, const Context&) [with Expr = const boost::proto::exprns_::expr<boost::proto::tag::shift_right, boost::proto::argsns_::list2<const boost::proto::utility::literal<const int&, boost::proto::domainns_::default_domain>&, boost::proto::exprns_::expr<boost::proto::tag::terminal, boost::proto::argsns_::term<int (* const&)(int)>, 0l> >, 2l>, Context = FuncStreamCtx, typename boost::proto::result_of::eval<Expr, Context>::type = int]' D:\My Documents\My Programmes\Tutorial\Proto\ProtoGame3\main.cpp:38:37: instantiated from here D:\My Documents\My Programmes\Tutorial\Proto\ProtoGame3\main.cpp:23:50: error: no matching function for call to 'boost::proto::context::callable_context<const FuncStreamCtx>::eval<boost::proto::utility::literal<const int&, boost::proto::domainns_::default_domain> >::eval(const boost::proto::utility::literal<const int&, boost::proto::domainns_::default_domain>&, const FuncStreamCtx&)' D:\Sources\Boost\boost_1_42_0/boost/proto/context/callable.hpp:223:17: note: candidates are: boost::proto::context::callable_context<const FuncStreamCtx>::eval<boost::proto::utility::literal<const int&, boost::proto::domainns_::default_domain> >::eval() D:\Sources\Boost\boost_1_42_0/boost/proto/context/callable.hpp:223:17: note: boost::proto::context::callable_context<const FuncStreamCtx>::eval<boost::proto::utility::literal<const int&, boost::proto::domainns_::default_domain> >::eval(const boost::proto::context::callable_context<const FuncStreamCtx>::eval<boost::proto::utility::literal<const int&, boost::proto::domainns_::default_domain> >&) Process terminated with status 1 (0 minutes, 19 seconds) 3 errors, 0 warnings

1 1

Boost.Iostreams devices and unsigned char character types
by laanan fisher 05 Jan '11

05 Jan '11

Hi, I'm having some trouble using boost::iostreams::basic_file (and other devices) with unsigned char character types. It's likely a lack of understanding on my part, so any help is greatly appreciated. Here is what I'd like to do, and the results from my g++ v4.5.0 compilation. Thanks for your time. # include <boost/iostreams/device/file.hpp> # include <boost/iostreams/get.hpp> int main() { namespace io = boost::iostreams; io::basic_file_source< unsigned char > file( "us.cpp" ); int ch = io::get( file ); return 0; } /* In file included from d:/boost_1_45_0/boost/iostreams/detail/adapter/non_blockin g_adapter.hpp:12:0, from d:/boost_1_45_0/boost/iostreams/close.hpp:19, from d:/boost_1_45_0/boost/iostreams/operations.hpp:16, from d:/boost_1_45_0/boost/iostreams/device/file.hpp:23, from us.cpp:1: d:/boost_1_45_0/boost/iostreams/read.hpp: In static member function 'static type name boost::iostreams::int_type_of<T>::type boost::iostreams::detail::read_devic e_impl<boost::iostreams::input>::get(T&) [with T = boost::iostreams::basic_file_ source<unsigned char>, typename boost::iostreams::int_type_of<T>::type = long un signed int]': d:/boost_1_45_0/boost/iostreams/read.hpp:47:60: instantiated from 'typename bo ost::iostreams::int_type_of<T>::type boost::iostreams::get(T&) [with T = boost:: iostreams::basic_file_source<unsigned char>, typename boost::iostreams::int_type _of<T>::type = long unsigned int]' us.cpp:10:28: instantiated from here d:/boost_1_45_0/boost/iostreams/read.hpp:180:42: error: incomplete type 'boost:: iostreams::detail::read_device_impl<boost::iostreams::input>::get(T&) [with T = boost::iostreams::basic_file_source<unsigned char>, typename boost::iostreams::i nt_type_of<T>::type = long unsigned int]::traits_type' used in nested name speci fier d:/boost_1_45_0/boost/iostreams/read.hpp:180:42: error: incomplete type 'boost:: iostreams::detail::read_device_impl<boost::iostreams::input>::get(T&) [with T = boost::iostreams::basic_file_source<unsigned char>, typename boost::iostreams::i nt_type_of<T>::type = long unsigned int]::traits_type' used in nested name speci fier d:/boost_1_45_0/boost/iostreams/read.hpp:180:42: error: incomplete type 'boost:: iostreams::detail::read_device_impl<boost::iostreams::input>::get(T&) [with T = boost::iostreams::basic_file_source<unsigned char>, typename boost::iostreams::i nt_type_of<T>::type = long unsigned int]::traits_type' used in nested name speci fier */

2 1

Local_date_time constructor question
by qplace 05 Jan '11

05 Jan '11

Documentation for local_date_time constructor local_date_time(...) Parameters: date time_duration time_zone_ptr bool states that the last parameter, "The DST flag", "must be passed to indicate whether the time is in daylight savings or not." My question is: Isn't the combination of the first parameter, "date" and third parameter, "time_zone_ptr" determine if the resulted local_date_time will be either in the daylight saving time period or not?

3 3

filtering stream fpos
by Christian Meesters 05 Jan '11

05 Jan '11

Hi, is there something like fpos for boost's filtering streams? If so, I must have overlooked it in the docs. Or, if this fpos-thing does not work out: I would like to remember the position where I left a (potentially gzipped) file and resume work (reading only) on that file in subsequent function calls. Is this somehow possible? TIA Christian PS Happy New Year everybody! (Better late than never ...)

1 0

Moving my Boost installation
by Robert Jones 05 Jan '11

05 Jan '11

I have Boost installed under Fedora13 in /usr/include, not installed by me, but I imagine done as part of installing Fedora. I have a codebase that uses Boost and builds perfectly, using gcc 4.5.1 Now, if I move my Boost installation mv /usr/include/boost ~rgj/xx and add an appropriate include directive to my compile lines, I get compile errors from Boost headers /home/rgj/xx/boost/date_time/gregorian/conversion.hpp: In function ‘tm boost::gregorian::to_tm(const boost::gregorian::date&)’: /home/rgj/xx/boost/date_time/gregorian/conversion.hpp|44 col 23| error: missing initializer for member ‘tm::tm_sec’ etc, etc Obviously I'm having a minor aberration here...what am I doing wrong? Thx, - Rob.

2 2

[property_tree] Parsing JSON
by Olivier Tournaire 05 Jan '11

05 Jan '11

Hi all, I am currently trying to parse a JSON file, but cannot figure how to achieve this task (see for instance http://ax.itunes.apple.com/WebObjects/MZStoreServices.woa/wa/wsSearch?term=… ). Here is a piece of code: #ifndef ITUNES_JSON_STRUCTURE_HPP #define ITUNES_JSON_STRUCTURE_HPP #include <boost/property_tree/ptree.hpp> #include <string> class itunes_json_structure { public: void load(const std::string &filename); boost::property_tree::ptree m_ptree; }; #endif // ITUNES_JASON_STRUCTURE_HPP #include "itunes_jason_structure.hpp" #include <boost/property_tree/json_parser.hpp> #include <iostream> using namespace std; void itunes_json_structure::load(const string &filename) { using boost::property_tree::ptree; try { // Load the JSON file into the property tree. If reading fails // (cannot open file, parse error), an exception is thrown. read_json(filename, m_ptree); cout << "resultCount = " << m_ptree.get<string>("resultCount") << endl; ptree all_results = m_ptree.get_child("results"); // HERE!!! How can I read the content of the "results" node???? } catch(exception &e) { throw e; } } I am unable to read the content of the "results" node. Could you please give me some help? Regards, Olivier

6 18

[math] fpclassify.hpp fails to compile with Intel icc 11.1
by Gabriel Redner 05 Jan '11

05 Jan '11

Hi all, The following code fails to compile with icc 11.1 under Linux: ========== #include <boost/math/special_functions/fpclassify.hpp> int main() {} ========== The full error is: ========== /usr/include/c++/4.4.5/cmath(500): error: identifier "__builtin_fpclassify" is undefined return __builtin_fpclassify(FP_NAN, FP_INFINITE, FP_NORMAL, ^ detected during: instantiation of "__gnu_cxx::__enable_if<std::__is_arithmetic<_Tp>::__value, int>::__type std::fpclassify(_Tp) [with _Tp=long double]" at line 104 of "/usr/include/boost/math/special_functions/fpclassify.hpp" instantiation of "bool boost::math_detail::is_nan_helper(T, const boost::true_type &) [with T=long double]" at line 137 of "/usr/include/boost/math/special_functions/fpclassify.hpp" instantiation of "int boost::math::detail::fpclassify_imp(T, const boost::math::detail::generic_tag<true> &) [with T=long double]" at line 242 of "/usr/include/boost/math/special_functions/fpclassify.hpp" compilation aborted for main.cpp (code 2) ========== The same code compiles fine under icc 12.0. I also tried explicitly adding: #define BOOST_MATH_DISABLE_STD_FPCLASSIFY before including the header, but got the same error. The math library docs say that icc 10.0 and later are fully supported with no serious caveats, so I presume this is a bug. Should I file a ticket? Please let me know if there is any other information about my system which could be useful to know. Thanks, -Gabe

3 5

Visualizer for boost::tuple
by Mohamed Bana 05 Jan '11

05 Jan '11

Hello, I can't seem to find a visualizer for boost::tuple, does anyone have one lying around somewhere? I'm using Visual Studio 2005, if that's of any help. I appreciate the help. —Mohamed

3 2

Re: [Boost-users] Mingw64 Boost Threads Build
by Dustin T. Clifford 04 Jan '11

04 Jan '11

Jim, The build worked! It's the first successful MinGW64 build that I have had. This build was performed from within Cygwin using the mingw64 toolset. I am attempting a build with the MinGW build you pointed me to. Thank again! However, when I attempt to compile the archive into my library I get the below error. Isdmain.o:Isdmain.cpp:(.text+0x16c3): undefined reference to `boost::thread::start_thread()' Isdmain.o:Isdmain.cpp:(.text+0x9982): undefined reference to `boost::thread::~thread()' Isdmain.o:Isdmain.cpp:(.text+0x9d1a): undefined reference to `boost::thread::~thread()' Isdmain.o:Isdmain.cpp:(.text+0x9dee): undefined reference to `boost::thread::~thread()' Isdmain.o:Isdmain.cpp:(.text+0x9e65): undefined reference to `boost::thread::~thread()' Isdmain.o:Isdmain.cpp:(.text+0xbbc3): undefined reference to `boost::thread::start_thread()' Isdmain.o:Isdmain.cpp:(.text+0xbc7e): undefined reference to `boost::thread::~thread()' Isdmain.o:Isdmain.cpp:(.text+0xbc96): undefined reference to `boost::thread::~thread()' Isdmain.o:Isdmain.cpp:(.text+0xca96): undefined reference to `boost::thread::~thread()' Isdmain.o:Isdmain.cpp:(.text+0xe23a): undefined reference to `boost::thread::thread()' Isdmain.o:Isdmain.cpp:(.text+0xe252): undefined reference to `boost::thread::thread()' Isdmain.o:Isdmain.cpp:(.text+0x10): undefined reference to `boost::thread::~thread()' Isdmain.o:Isdmain.cpp:(.text+0x30): undefined reference to `boost::thread::~thread()' Isdmain.o:Isdmain.cpp:(.text$_ZN5boost6threadaSENS_6detail13thread_move_tIS0_EE[boost::thread::operator=(boost::detail::thread_move_t<boost::thread>)]+0x131): undefined reference to `boost::thread::~thread()' I have examined the library symbols and, indeed, I cannot find the appropriate externs. I jumped from 1.35.0 to 1.45.0. I was just wondering if you have any idea why this would start happening? Am I missing something? Any help would be greatly appreciated. Dustin P.S. I will let you know if this changes with the new MinGW64 build. From: Jim Bell [mailto:Jim@JC-Bell.com] Sent: Tuesday, January 04, 2011 12:04 PM To: Dustin T. Clifford Subject: Re: [Boost-users] Mingw64 Boost Threads Build I did run the regression test last night, FYI... http://www.boost.org/development/tests/trunk/developer/thread.html Last column. All tests pass but one. HTH. -Jim On 1/4/2011 10:39 AM, Dustin T. Clifford wrote: Jim, Thank you. I am going to try your patch now. I will let you know how things work out. Thanks again! Dustin From: Jim Bell [mailto:Jim@JC-Bell.com] Sent: Friday, December 31, 2010 10:35 AM To: boost-users(a)lists.boost.org<mailto:boost-users@lists.boost.org> Cc: Dustin T. Clifford Subject: Re: [Boost-users] Mingw64 Boost Threads Build I have a trunk regression-test platform that runs Mingw64 on Win7-64. It's experimental and isn't in the regression matrix right now, but works as well as any MinGW platform (or pretty close). I use GCC 4.6 from here <http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20W…><http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20W…>. CygWin's not installed on this machine. I've attached my complete set of patches. A little cryptic (and patches a pretty recent trunk revision), but should give you a set of changes that ought to get you close. You should be able to use the pre-built bjam (32-bit). <http://www.boost.org/doc/libs/1_45_0/more/getting_started/windows.html#get-…><http://www.boost.org/doc/libs/1_45_0/more/getting_started/windows.html#get-…> boostrap.bat needs a little hacking for gcc. Good luck! -Jim On 1:59 PM, Dustin T. Clifford wrote: Good Afternoon, We have been using boost-threads for our native APIs and, thus far, Boost has been a godsend! We had a recent request to build a 64-bit version of this API. To accomplish this we have attempted to build using MinGW64. Unfortunately, I have had zero luck getting boost-threads to build. I can build the 32-bit address model without a problem but 64-bit continues to elude me. I first tried Boost 1.35.0 and have now moved on to 1.45.0. I believe that the environment is set up correctly (see below). This build is being performed on a Windows 7 64-bit using MinGW64 from Cygwin. export CC=x86_64-w64-mingw32-gcc.exe export CXX=x86_64-w64-mingw32-g++.exe export LD=x86_64-w64-mingw32-ld.exe I have, also, modified my PATH to use the appropriate 64-bit bintools and aliased gcc, g++ and ld to the 64-bit MinGW64 compilers and linkers. To build Boost I have used the following with no success. boostrap.sh address-model=64 -prefix=<install> --with-libraries=thread; bjam -a install; boostrap.sh -prefix=<install> --with-libraries=thread; bjam -a address-model=64 install; boostrap.sh -prefix=<install> --with-libraries=thread; bjam -a install; The last build attempt succeeds but appears to have built 32-bit binaries. The previous two fail in building boost-threads complaining that 'address-model-64' is not found for certain build artifacts. I have, also, tried the above with a prebuilt bjam with the same results. I have tried much more than what I have cited here (including MSVC builds) with no success (some built but resulted in 32-bit binaries). I have scoured Google and found many talking about this but most either had no resolution or contained instructions that conflicted or made no sense. Does anybody have any insight into how I can produce a 64-bit boost-threads archive? Any help would be greatly appreciated. Thanks in advance, Dustin P.S. If I have missed any information or you need more (build logs are too big to attach), please, let me know.

2 3

Re: [Boost-users] [Proto] Vector Example Compilation Failure
by Hossein Haeri 04 Jan '11

04 Jan '11

Hi Erik, > This is the same problem as last time, although you would need to dig > into BOOST_PROTO_DEFINE_OPERATORS to know that. I see. Would it be too much trouble to ask for an explanation on how you got there from the compiler spew? > I don't think gcc-4.5 was available when Boost 1.42 was released, so > it's not surprising there are problems. Would it be possible for you to > use a more recent version of Boost? It would be a pain 'cause I need to port a lot of things. (Proto is not the only part of Boost that we use.) Anyhow, the bigger pain is that I have no much clue about Proto error messages and our company is committed to be a long-term user of Proto. Therefore, learning how to demystify Proto error messages is of much importance to me and I'm ready to pay the porting price if that's what it takes. :D But, seriously, have you ever thought of including a section or two on how to do that in the Proto documentation? The other (sort of related) thing is that it's come to my attention that Fusion knowledge comes very handy in Proto development. This is though not encouraged at all and I don't really think that the documentations of Fusion and Proto are that nicely tied. TIA, --Hossein

4 7