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

feature request: date_time module: date_iterator--
by Erik Thiele 22 May '03

22 May '03

hi the date iterator only has ++ but no --. please add the -- cu & thx erik -- Erik Thiele

2 1

date_time local to UTC conversion
by Erik Thiele 22 May '03

22 May '03

hi. i am using boost::date_time i am using ptime always in UTC. but some time i have to interact with user. therefore i need to convert the ptime to the local ptime back and forth. int foo () { ptime mytime_asutc = some_UTC_time; ptime mytime_aslocal = XXX (mytime_asutc); ptime histime_aslocal = some_local_time; ptime histime_asutc = YYY (histime_aslocal); } i am in germany, so i'd like to use germany local settings. best would be to get all information from unix TZ variable. but i found out, only one direction of conversion works with unix TZ. the other one needs manual input. i don't understand the eu_dst_trait stuff. i'd very much appreciate to have XXX and YYY. cu & thx erik -- Erik Thiele

1 0

VC7.1 and ublas
by Witz 22 May '03

22 May '03

hi, When i try to compile the code in listing 1 below using MSVC7.1 i get a whole host of errors of the same form as that given in listing 2. I've looked around on google but either i'm not concentrating or this issue hasn't come up yet. I've also had a quick look in boost/format but would rather not hack around with stuff i don't know. Does anyone know what i need to do to get this working? Thanks in advance, Ian Whittley Listing 1: #include <boost/numeric/ublas/triangular.hpp> int main() { boost::numeric::ublas::triangular_matrix<int> m; } Listing 2: 'C:\Developer\boost_1_30_0\boost\numeric\ublas\matrix_expression.hpp(781): error C2027: use of undefined type 'boost::numeric::ublas::vector_matrix_binary<E1,E2,F>::const_iterator2'

4 4

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

22 May '03

Hi Andre, this is not only behavior of VC, all compilers, as far as I know have some include/lib paths preconfigured, to prevent you from specifying them always on command lines. You have two options how to use stlport: 1) #include <stlport/string> + STLport allows it and it does not clash with the VC STL and you can do also some benchmarks... ;-) - your code has hard-coded includes of STL headers and it is not easy to switch STL then 2) #include <string> + your includes look standard for any compiler/STL - your compiler must support replacing of its own ST with the alternative one (STLport) The 2) option you can achieve with VC by two ways: a) do not rely on the built-in header/lib paths and provide them always on the command line or environment (I'd recommend the latter...) - it is turned on by the switch /useenv (VC7) or /env (VC6) and then you have to provide your own paths e.g. in environment: INCLUDE=D:\STLport-4.5.3;D:\STLport-4.5.3\stlport;D:\Program Files\Microsoft Visual Studio .NET\Vc7\ATLMFC\INCLUDE;D:\Program Files\Microsoft Visual Studio .NET\Vc7\INCLUDE;D:\Program Files\Microsoft Visual Studio .NET\Vc7\PlatformSDK\include;D:\Program Files\Microsoft Visual Studio .NET\FrameworkSDK\include;D:\Program Files\Microsoft Visual Studio .NET\Vc7\PlatformSDK\include\prerelease LIB=D:\STLport-4.5.3\lib;D:\Program Files\Microsoft Visual Studio .NET\Vc7\LIB;D:\Program Files\Microsoft Visual Studio .NET\Vc7\ATLMFC\LIB;D:\Program Files\Microsoft Visual Studio .NET\Vc7\PlatformSDK\lib;D:\Program Files\Microsoft Visual Studio .NET\FrameworkSDK\lib;D:\Program Files\Microsoft Visual Studio .NET\Vc7\PlatformSDK\lib\prerelease b) modify the paths in the VC's configuration - see the menu Tools/Options Projects/VC++ Directories and put the path(s) to STLport into the three of them: Include (for compiler), Library (for linker), Source (for debugger - necessary only in VC6, VC7 uses absolute paths n PDBs) I personally prefer 2) a) because if I do not want to compile everything on my machine with STLport, it prevents me from still reconfiguring of VC system paths and I can set the variables simply in a build batch for devenv /build, and in a IDE-runing batch for tho work. Then I can easily test also more versions of STLport. You can choose your favorite way, rgds, Ferda -----Original Message----- From: adutoit [mailto:adutoit@stonethree.com] Sent: Wednesday, May 21, 2003 16:41 To: Boost-Users(a)yahoogroups.com Subject: Re: [Boost-Users] boost::date_time::posix_time and Intel Compiler 7.0? 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++!!! That means I must specify STLPort include path first, then stupid VC98 include path. Now I am down to one compilation error, using my much-reported compilation setup : Compiling... graph_qt.cpp C:\PROGRAM FILES\BOOST_1_30_0\boost/lexical_cast.hpp(147): error: no operator "<<" matches these operands operand types are: _STL::basic_stringstream<wchar_t, _STL::char_traits<wchar_t>, _STL::allocator<wchar_t>> << const _STL::basic_string<char, _STL::char_traits<char>, _STL::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=_STL::basic_string<char, _STL::char_traits<char>, _STL::allocator<char>>]" at line 192 instantiation of "Target boost::lexical_cast<Target,Source>(Source) [with Target=unsigned short, Source=_STL::basic_string<char, _STL::char_traits<char>, _STL::allocator<char>>]" at line 30 of "C:\PROGRAM FILES\BOOST_1_30_0\boost/date_ti me/time_parsing.hpp" instantiation of "time_duration boost::date_time::parse_delimited_time_duration<time_duration>(const _STL::string &) [with time_duration=boost::posix_time::time_duration]" compilation aborted for C:\home\adutoit\work\s3_qt\s3_qt\graph_qt.cpp (code 2) Error executing cl.exe. libs3_qt.lib - 1 error(s), 0 warning(s) Any ideas? (Except for checking my include path specs again :) ) Greetings, Andre ----- Original Message ----- From: "adutoit" <adutoit(a)stonethree.com> To: <Boost-Users(a)yahoogroups.com> Sent: Wednesday, May 21, 2003 4:16 PM 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/ > > > > > > 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/Lj3uPC/Me7FAA/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/

2 1

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

22 May '03

I think you might be getting bit by the way wchar_t == unsigned short on MSVC, and when Intel uses MSVC compatibility. If you look, its using a basic_stringstream<wchar_t...> You could try /Zc:wchar_t to make wchar_t an intrinsic type. > -----Original Message----- > From: adutoit [mailto:adutoit@stonethree.com] > Sent: Wednesday, May 21, 2003 7:41 AM > To: Boost-Users(a)yahoogroups.com > Subject: Re: [Boost-Users] boost::date_time::posix_time and Intel > Compiler 7.0? > > > 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++!!! > > That means I must specify STLPort include path first, then stupid VC98 > include path. Now I am down to one compilation error, using my > much-reported compilation setup : > > Compiling... > graph_qt.cpp > C:\PROGRAM FILES\BOOST_1_30_0\boost/lexical_cast.hpp(147): error: no > operator "<<" matches these operands > operand types are: _STL::basic_stringstream<wchar_t, > _STL::char_traits<wchar_t>, _STL::allocator<wchar_t>> << const > _STL::basic_string<char, _STL::char_traits<char>, > _STL::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=_STL::basic_string<char, > _STL::char_traits<char>, _STL::allocator<char>>]" at line 192 > instantiation of "Target > boost::lexical_cast<Target,Source>(Source) [with > Target=unsigned short, > Source=_STL::basic_string<char, _STL::char_traits<char>, > _STL::allocator<char>>]" at line 30 of "C:\PROGRAM > FILES\BOOST_1_30_0\boost/date_ti > me/time_parsing.hpp" > instantiation of "time_duration > boost::date_time::parse_delimited_time_duration<time_duration>(const > _STL::string &) [with time_duration=boost::posix_time::time_duration]" > compilation aborted for > C:\home\adutoit\work\s3_qt\s3_qt\graph_qt.cpp (code > 2) > Error executing cl.exe. > > libs3_qt.lib - 1 error(s), 0 warning(s) > > > Any ideas? (Except for checking my include path specs again :) ) > > Greetings, > Andre > ----- Original Message ----- > From: "adutoit" <adutoit(a)stonethree.com> > To: <Boost-Users(a)yahoogroups.com> > Sent: Wednesday, May 21, 2003 4:16 PM > 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/ > > > > > > > > > > > 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/Lj3uPC/Me7FAA/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. -----------------------------------------------------------------------

2 1

RE: [Boost-Users] Intel compiler, Boost and STLPort (3rd try)
by Tom Matelich 22 May '03

22 May '03

We've used Intel 6-7.1, with boost and STLPort for the last 9 months. I also make sure to use the latest Platform SDK. There were a few issues here and there, but things mostly went fine. Is your STLPort built with Intel or MSVC? Here are our instructions for building STLPort from our wiki: * edit stlport/stl_user_config,uncomment the macro _STLP_NEW_PLATFORM_SDK defined. * on the command line, go to the src subdirectory * run nmake -f intel50.mak clean all (make sure in your global include path that the SDK inlclude path comes before the VC98 path otherwise you will get build errors) * If successful, run nmake -f intel50.mak all install * In MSVC, go to tools/options/Directories, and make [path to msvc]/VC98/include/stlport the first entry in the list. After that: What command line options are you using? Are you using MSVC or Makefiles? I just went and looked at your errors again... It says std::. That implies you are not using STLPort, because theirs comes up saying STLP:: (or something like that). > -----Original Message----- > From: Andre du Toit [mailto:adutoit@stonethree.com] > Sent: Wednesday, May 21, 2003 11:45 AM > To: boost-users > Subject: [Boost-Users] Intel compiler, Boost and STLPort (3rd try) > > > 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. > > > ------------------------ Yahoo! Groups Sponsor > ---------------------~--> > Get A Free Psychic Reading! Your Online Answer To Life's > Important Questions. > http://us.click.yahoo.com/Lj3uPC/Me7FAA/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. -----------------------------------------------------------------------

2 1

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 21 May '03

21 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