- Boost-users - lists.boost.org

RE: [Boost-Users] boost::date_time::posix_time and Intel Compiler 7.0?
by Jim.Hyslop 22 May '03

22 May '03

adutoit [mailto:adutoit@stonethree.com] wrote: > I know I said I will not return soon, but I finally realised > that stupid > Visual C++ is to blame for my original compilation error, not > anyone from > Boost or the Intel compiler writer team. > > For some reason, the order in which you specify include paths > (for crying > out loud!) matters in Visual C++!!! Er, Visual C++ is not alone in this behaviour. The compilers I'm familiar with all behave that way - the directories are searched in the order they are specified. When a match is found, the search stops. The same logic applies when using LIB to find libraries, PATH to find executables, and so on. Why should INCLUDE behave differently? Think about it - you have two different header files with the same name: the standard ones shipped with VC, and the StlPORT. How else would you expect the compiler to behave? Pick the last one it finds? Pick one at random? Spit out an error? -- Jim

2 1

singleton
by sashan 22 May '03

22 May '03

Is there construct that supports the singleton idea in boost? I've searched through the docs but may have missed it. I find it odd that it's not there. -- sashan http://sashan.netfirms.com -------------------------------------------------- Brain: Here we are, Pinky--at the dawn of time! Pinky: Narf, Brain. Wake me at the noon of time.

2 1

HPUX aCC regex problems
by ilopanaj 21 May '03

21 May '03

Hello, Has anyone had any success building the regex library (1_26_0 - 1_30_0) using any of the recent aCC versions under HPUX 11.11? If so, are there any tricks or modifications necessary to get it to work? Thanks in advance, Jerry

2 1

boost::mutex::scoped_lock conventions
by Mark Sizer 21 May '03

21 May '03

Is there a convention about whether or not to explicitly call .unlock()? In the case where everything to the end of the scope should be locked, there is no NEED to do it, but isn't it a bit sloppy to leave locks locked? Much like not using braces on one-line 'if' statements, it could cause maintenance problems later. What's the current thinking? Thanks, - Mark P.S. I'm currently always unlocking, because sometimes I want to unlock before the scope ends. This makes it clear exactly what I intend.

6 25

Intel compiler, Boost and STLPort (3rd try)
by Andre du Toit 21 May '03

21 May '03

Ahem, could someone please answer my simple question: Is is possible to compile programs which use Boost and STLPort (instead of Microsoft Foundation Classes) with the Intel compiler, on Windows? I am getting all kinds of weird errors which relate to streaming operators, which makes me think that my usage of STLPort might be involved? On the other hand, if I use MSCV6 instead of Intel compiler (7.0) I do not get the same errors. It seems that some of our in-house software can't be compiled with MSVC6 because of problems this specific compiler has with templates. The same code compiles without problem on the latest GCC compilers. My latest source of joy is the following (about which I am totally clueless) : C:\PROGRAM FILES\BOOST_1_30_0\boost/lexical_cast.hpp(147): 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; ^ detected during: instantiation of "bool={bool} boost::detail::lexical_stream<Target, Source>::operator<<(const Source &) [with Target=unsigned short, Source=std::basic_string<char, std::char_traits<char>, std::allocator<char>>]" at line 192 instantiation of "Target boost::lexical_cast<Target,Source>(Source) [with Target=unsigned short, Source=std::basic_string<char, std::char_traits<char>, std::allocator<char>>]" at line 30 of "C:\PROGRAM FILES\BOOST_1_30_0\boost/date_time/ time_parsing.hpp" instantiation of "time_duration boost::date_time::parse_delimited_time_duration<time_duration>(const std::string &) [with time_duration=boost::posix_time::time_duration]" C:\PROGRAM FILES\BOOST_1_30_0\boost/lexical_cast.hpp(153): error: no operator ">>" matches these operands operand types are: std::basic_stringstream<char, std::char_traits<char>, std::allocator<char>> >> boost::int64_t stream >> output && ^ detected during: instantiation of "bool={bool} boost::detail::lexical_stream<Target, Source>::operator>>(InputStreamable &) [with Target=boost::int64_t={__int64}, Source=std::basic_string<char, std::char_traits<char>, std::allocator<char>>, InputStreamab le=boost::int64_t={__int64}]" at line 192 instantiation of "Target boost::lexical_cast<Target,Source>(Source) [with Target=boost::int64_t={__int64}, Source=std::basic_string<char, std::char_traits<char>, std::allocator<char>>]" at line 47 of "C:\PROGRAM FILES\BOOST_1_30_0\boost/ date_time/time_parsing.hpp" instantiation of "time_duration boost::date_time::parse_delimited_time_duration<time_duration>(const std::string &) [with time_duration=boost::posix_time::time_duration]" Greetings, Andre.

1 0

RE: [Boost-Users] boost::date_time::posix_time and Intel Compiler 7.0?
by Tom Matelich 21 May '03

21 May '03

One other thing I should point out to you about building, or actually lack there of, inside MSVC. Intel doesn't know how to generate the PDB files themselves, so they call MSVC's cl to do it for them. This is a problem because if cl can't build the file, it doesn't generate any dependencies for it. If you use templates that MSVC can't handle, you'll probably want to switch to makefiles. We did. Fortunately, qmake rocks :) > -----Original Message----- > From: adutoit [mailto:adutoit@stonethree.com] > Sent: Wednesday, May 21, 2003 7:16 AM > To: Boost-Users(a)yahoogroups.com > Subject: Re: [Boost-Users] boost::date_time::posix_time and Intel > Compiler 7.0? > > > Right; here are my compiler options, build configuration and the rest. > > Basically I am building a static library, which depends on > some in-house > software components, Qt and Boost. > Our own library S3FC (), uses templates in such a manner as > to make MSVC6 > very unhappy. Therefore we use the Intel compiler under M$. > Needless to say, our software compiles problemfree with GCC. For the > aforementioned and other reasons we do not make use of > Microsoft Foundation Classes when compiling under Windoze, but use the > latest version of STLPort (which has been at the same version > level for some > time now). > > Anyway; our Windows development work takes place under Visual > C++ but with > the Intel compiler (version 7.0) selected instead of the > MSVC6 compiler. > > OK; with this background then, here is the basic Visual C++ > project settings > for my build of the above-mentioned library. I have removed > include paths > etc. which point to in-house > software: > > 1) "Not Using MFCC" selected for general project settings (as > explained > above). > 2) Warning level => 3 > Optimizations => Maximise Speed > Debug info => None > 3) Project Options => > /nologo /ML /W3 /GR /GX /O2 /D "NDEBUG" /D "DEP_MS_WIN" > /D "WIN32" /D > "_WINDOWS" > /U "QT_NO_STL" /Fp"Release/libs3_qt.pch" /YX /Fo"Release/" > /Fd"Release/" /FD > /c > > The include and library paths for STLPort is set somewhere > else, but these > are basically the options. > > If anyone knows of any special project options, preprocessor > directives I am > perhaps missing for building Boost-related projects with the > Intel compiler, > please let me know! > I suspect that we will soon be using Boost for other > functionality besides > that provided by date_time at the moment. Besides, I like > the library and > works in our main development environment, > Linux with the GCC compiler. > > OK, I am forgetting about this problem for a day or two... > Thanks to everyone who has provided me with help so far, > especially Jeff > Garland. > > Greetings, > Andre. > > ----- Original Message ----- > From: "Jeff Garland" <jeff(a)crystalclearsoftware.com> > To: <Boost-Users(a)yahoogroups.com> > Sent: Wednesday, May 21, 2003 3:42 PM > Subject: RE: [Boost-Users] boost::date_time::posix_time and > Intel Compiler > 7.0? > > > > > > > Anyway; it just irks me that I should have issues with > 'standard' stuff, > > > like streaming operators. > > > And the fact that the same code compiles with MSVC6 and > NOT the Intel > > > compiler. > > > > Ok. > > > > > Back on the #define which started my woes. The fact of > the matter is, I > get > > > everything compiled when using MSVC6 and not the Intel compiler! > > > I.e. the MSVC6-specific code works, the 'other' compiler > code for the > > > supposedly more Boost-compliant/friendly Intel compiler does not. > > > > I guess I was thinking that what was happening is that when > compiling > > with Intel you were getting the MSVC defined and hence were > taking the > > non-generic code. Perhaps not... > > > > Have you tried to run the tests in libs/date_time/test with your > > Intel/STLPort configuration? That might help diagnose the issue. > > Also, it might be instructive to post your compile command. Perhaps > > someone with experience on Intel can figure out why your > configuration > > differs from the one that apparently passes the tests. > > > > > Could it be because I am using STLPort in conjunction > with the Intel > > > compiler? > > > > Might be a factor. There have been some issues before with > the library > > configuration assuming MSVC limitations which don't apply > with STLPort > > in the mix. > > > > > Aargh. Just give me Linux and GCC... > > > > Agreed :-) > > > > Jeff > > > > > > > > Info: <http://www.boost.org> > > Wiki: > <http://www.crystalclearsoftware.com/cgi-bin/boost_wiki/wiki.pl> > > Unsubscribe: <mailto:boost-users-unsubscribe@yahoogroups.com> > > > > > > Your use of Yahoo! Groups is subject to > http://docs.yahoo.com/info/terms/ > > > > > ------------------------ Yahoo! Groups Sponsor > ---------------------~--> > Get A Free Psychic Reading! > Your Online Answer To Life's Important Questions. > http://us.click.yahoo.com/aM1XQD/od7FAA/uetFAA/EbFolB/TM > -------------------------------------------------------------- > -------~-> > > Info: <http://www.boost.org> > Wiki: <http://www.crystalclearsoftware.com/cgi-bin/boost_wiki/wiki.pl> > Unsubscribe: <mailto:boost-users-unsubscribe@yahoogroups.com> > > > Your use of Yahoo! Groups is subject to > http://docs.yahoo.com/info/terms/ > > ----------------------------------------------------------------------- DISCLAIMER: Information contained in this message and/or attachment(s) may contain confidential information of Zetec, Inc. If you have received this transmission in error, please notify the sender by return email. -----------------------------------------------------------------------

1 0

Release builds and C++Builder
by Russell Hind 21 May '03

21 May '03

Does doing a release build of the boost libraries define NDEBUG. (don't know if this is standard) but in C++Builder, NDEBUG disables asserts so it is useful to define it when doing release builds. Thanks Russell

2 2

lambda library: How to access member variables?
by Chuck Messenger 21 May '03

21 May '03

I'm trying to figure out how to do something like this: for_each(c.begin(), c.end(), cout << _1.member << "\n"); which is obviously wrong, but hopefully you know what I mean... Experimenting with ways of accessing members inside a lambda, I wrote the following: #include <iostream> #include <boost/lambda/lambda.hpp> #include <vector> using namespace std; using namespace boost; using namespace lambda; struct XX { XX(int a, int b) { a_ = a; b_ = b; } int a_; int b_; }; int main() { XX xx(5, 6); XX *xxp = &xx; cout << "These should all be equivalent:\n"; cout << xxp ->* &XX::a_ << endl; cout << (_1 ->* &XX::a_)(xxp) << endl; //cout << (_1 ->* &XX::a_)(&xx) << endl; // Doesn't compile! cout << (&_1 ->* &XX::a_)(xx) << endl; cout << "Now, let's try with the vector:\n"; vector<XX> xxVec; xxVec.push_back(XX(3, 4)); cout << (&_1 ->* &XX::a_)(xxVec[0]) << endl; //cout << (_1 ->* &XX::a_)(&xxVec[0]) << endl; // Doesn't compile! cout << (_1 ->* &XX::a_)(xxp = &xxVec[0]) << endl; // Now it compiles... //cout << (_1 ->* &XX::a_)(xxVec.begin()) << endl; // Doesn't compile! //cout << (_1 ->* &XX::a_)(&*xxVec.begin()) << endl; // Still not... cout << (_1 ->* &XX::a_)(xxp = &*xxVec.begin()) << endl; // Now it compiles... exit(0); } I'm mystified by why some of these lines don't compile (gcc 3.2.2). Can anyone explain it? The compiler generates some horrific error messages -- I haven't tried to pick through them yet... - Chuck

1 0

MPL and apply_if trouble
by Tarjei Knapstad 21 May '03

21 May '03

I encountered the following problem today which I've reduced down to a simple example. Basically what I want to do is recurse through a typelist (mpl::vector) popping an element each time and end recursion by using apply_if with mpl::empty<List> as the condition. I've made a simple Reverse class template to illustrate the problem. (The Reverse class is of course intended to reverse the contents of a typelist....) --------------------- begin code --------------------- #include <boost/mpl/front.hpp> #include <boost/mpl/push_back.hpp> #include <boost/mpl/pop_front.hpp> #include <boost/mpl/apply_if.hpp> #include <boost/mpl/empty.hpp> #include <boost/mpl/size.hpp> #include <boost/mpl/vector.hpp> using namespace boost::mpl; template <typename List> struct Reverse { typedef typename front<List>::type FrontElem; typedef typename pop_front<List>::type Rest; typedef typename apply_if< empty<Rest>, vector<FrontElem>, typename push_back<typename Reverse<Rest>::Type, FrontElem>::type >::type Type; }; typedef vector<int,int,long> List; typedef Reverse<List>::Type RevList; --------------------- end code ----------------------- When attempting to create the RevList type however, gcc spits the following at me: reverse.cpp: In instantiation of `boost::mpl::pop_front<boost::mpl::vector0<boost::mpl::void_> >': reverse.cpp:15: instantiated from `Reverse<boost::mpl::vector0<boost::mpl::void_> >' reverse.cpp:21: instantiated from `Reverse<boost::mpl::vector1<long int> >' reverse.cpp:21: instantiated from `Reverse<boost::mpl::vector2<int, long int> >' reverse.cpp:21: instantiated from `Reverse<List>' reverse.cpp:25: instantiated from here reverse.cpp:15: base class ` boost::mpl::pop_front_traits<boost::mpl::aux::vector_tag<0> >::algorithm<boost::mpl::vector0<boost::mpl::void_> >' has incomplete type reverse.cpp: In instantiation of `Reverse<boost::mpl::vector0<boost::mpl::void_> >': reverse.cpp:21: instantiated from `Reverse<boost::mpl::vector1<long int> >' reverse.cpp:21: instantiated from `Reverse<boost::mpl::vector2<int, long int> >' reverse.cpp:21: instantiated from `Reverse<List>' reverse.cpp:25: instantiated from here reverse.cpp:15: no type named `type' in `struct boost::mpl::pop_front<boost::mpl::vector0<boost::mpl::void_> >' reverse.cpp:21: no type named `type' in `struct boost::mpl::pop_front<boost::mpl::vector0<boost::mpl::void_> >' reverse.cpp: In instantiation of `Reverse<boost::mpl::vector1<long int> >': reverse.cpp:21: instantiated from `Reverse<boost::mpl::vector2<int, long int> >' reverse.cpp:21: instantiated from `Reverse<List>' reverse.cpp:25: instantiated from here reverse.cpp:21: no type named `Type' in `struct Reverse<boost::mpl::vector0<boost::mpl::void_> >' reverse.cpp: In instantiation of `Reverse<boost::mpl::vector2<int, long int> >': reverse.cpp:21: instantiated from `Reverse<List>' reverse.cpp:25: instantiated from here reverse.cpp:21: no type named `Type' in `struct Reverse<boost::mpl::vector1<long int> >' reverse.cpp: In instantiation of `Reverse<List>': reverse.cpp:25: instantiated from here reverse.cpp:21: no type named `Type' in `struct Reverse<boost::mpl::vector2<int, long int> >' reverse.cpp:25: syntax error before `;' token I cannot see why it reaches the point where it tries to instantiate Reverse with an empty typelist - the apply_if should stop that (at least that's my intention. Am I being a complete ass somewhere in this code snippet? I've become blinded by now, so if anyone can point out what's wrong I would greatly appreciate it. Sincerely, -- Tarjei

2 5

BOOST_DEDUCED_TYPENAME error
by Pete Cilliers 20 May '03

20 May '03

I get the following error when trying to use the filesystem library on MSVC 6.0 : error C2061: syntax error : identifier 'BOOST_DEDUCED_TYPENAME' The line causing the problem is in the \detail\iterator.hpp file: template <class T> type_traits::yes_type is_mutable_iterator_helper(T const*, BOOST_DEDUCED_TYPENAME T::value_type*); I have run a config Test and both BOOST_DEDUCED_TYPENAME and BOOST_NO_DEDUCED_TYPENAME are defined but have no value. Since MSVC 6.0 supports the 'typename' keyword I would think that the declaration above in the iterator.hpp file should use 'typename' rather than BOOST_DEDUCED_TYPENAME. Anyone else experience this problem? ******************************************************************************************* <http://www.intec-telecom-systems.com/> This e-mail and any attachments are confidential and may also be privileged and/or copyright material of Independent Technology Systems Limited (or its affiliated companies). If you are not the intended or authorised recipient of this email or have received it in error, please delete it immediately and notify the sender by e-mail. In such a case reading, reproducing, printing or further dissemination of this e-mail is strictly prohibited and may be unlawful. Independent Technology Systems Limited does not represent or warrant that an attachment hereto is free from computer viruses or other defects. The opinions expressed in this e-mail and any of the attachments may be those of the author and are not necessarily those of Independent Technology Systems Limited. ******************************************************************************************

2 1