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

Date-time - How to handle mixed instances of floating, UTC and local times
by Mike Higginbottom 17 Jul '07

17 Jul '07

I have an application that needs to deal with floating time, UTC and local time. I can use ptime to represent floating and UTC but there's then no way to tell, for a given ptime instance, whether it represents a floating time or UTC. I could use local_time with a null tz to represent UTC or floating (seems like a hack and still only allows me one or the other representation) and a non-null tz for local times. Given only two 'time' classes (ptime and local_time) what's the best way to represent three different time concepts? Should I inherit from local_time to give me my three representations? -- Mike Higginbottom Paul Smith Computer Services Silk Mill House 196 Huddersfield Road Meltham Holmfirth HD9 4AW United Kingdom http://www.pscs.co.uk +44 (0)1484 855800

1 0

[interprocess] construct<> and find_or_construct<>
by "JOAQUIN LOPEZ MU?Z" 17 Jul '07

17 Jul '07

Are construct<> and find_or_construct<> self-synchronized? For instance, can several process do the following seg.find_construct<type>("name"); (same seg, type and name) without guarding the operation with a mutex? Thank you, Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

3 2

Re: [Boost-users] [regex] How to compile with desired versionwhenmultiple versions of boost library are installed
by Chandan Nilange 17 Jul '07

17 Jul '07

Also as suggested by David, I had to change LD_LIBRARY_PATH=/home/ChandanNilange/work/boost/lib:$LD_LIBRARY_PATH Thanks David! Rgds, Chandan --- Chandan Nilange <chandan_nilange(a)yahoo.com> wrote: > Hello John & Steven, > > Thanks for ur help. > I was able to resolve the issue. > > As per the link > http://gcc.gnu.org/onlinedocs/cpp/Search-Path.html > > "All the directories named by -I are searched, in > left-to-right order, before the default directories. > The only exception is when dir is already searched > by > default. In this case, the option is ignored and the > search order for system directories remains > unchanged." > > Since we have "boost" directory at default > path:/usr/include/boost, it used to look > /usr/include/boost before > -I<install_path>/boost_1_34_0/boost > > Workaround Done: used -I<install_path>/boost_1_34_0 > Now "boost_1_34_0" is not in default path hence > looked > first > > Though this workaround works, let me know if this is > the right way to go. > > Thanks & Regards, > Chandan > > > > > > ____________________________________________________________________________________ > Boardwalk for $500? In 2007? Ha! Play Monopoly Here > and Now (it's updated for today's economy) at Yahoo! > Games. > http://get.games.yahoo.com/proddesc?gamekey=monopolyherenow > > ____________________________________________________________________________________ Boardwalk for $500? In 2007? Ha! Play Monopoly Here and Now (it's updated for today's economy) at Yahoo! Games. http://get.games.yahoo.com/proddesc?gamekey=monopolyherenow

1 0

Re: [Boost-users] [regex] How to compile with desired version when multiple versions of boost library are installed
by Chandan Nilange 17 Jul '07

17 Jul '07

Hello, I have boost_1_32 version installed at /usr/include/boost Also, I have installed boost_1_34 at another path:/home/myname/work/boost/boost_1_34_0/ Now when I try to run with 1_34 version, it still points to 1_32 version at /usr/include (this is observed when I debug using gdb it refers to /usr/include/boost/regex/v4/match_results.hpp:118) I tried following things: 1] export LD_LIBRARY_PATH=/home/myname/work/boost/boost_1_34_0/boost:$LD_LIBRARY_PATH export PATH=/home/myname/work/boost/boost_1_34_0/boost:$PATH 2] I am using following command for compilation g++ -c -g -I/home/myname/work/boost/boost_1_34_0/boost ${TEST_FILES_PATH}/${TEST}.c g++ ${TEST}.o -L/home/myname/work/boost/lib -lboost_regex 3] I am including boost header in ${TEST}.c as below #include "boost/regex.hpp" Any help is most welcome. Thanks and Regards, Chandan ____________________________________________________________________________________ Pinpoint customers who are looking for what you sell. http://searchmarketing.yahoo.com/

5 7

tools/regression *.cpp files and test procedure
by Robert Ramey 17 Jul '07

17 Jul '07

http://www.boost.org/tools/regression/index.htm as well as the 1.34 release candidate refer to process_jam_log.cpp and compiler_status.cpp. Also there is a shell script run_tests.sh for invoking these programs. Is this information correct? Does this procedure, programs and scripts function with bjam V2 and whatever else has changed with 1.34 ? Robert Ramey

1 1

[BGL] filtered_graph and push_relabel_max_flow
by Leandro T. C. Melo 17 Jul '07

17 Jul '07

Hi all. I noticed the following comment on file push_relabel_max_flow.hpp: // This is a breadth-first search over the residual graph // (well, actually the reverse of the residual graph). // Would be cool to have a graph view adaptor for hiding certain // edges, like the saturated (non-residual) edges in this case. This comment is on top of function global_distance_update(), which actually implements the bfs mentioned above. Is there a particular reason for not filtering the graph (with filtered_graph) and avoiding the saturated edges? (Instead of reimplementing bfs.) Also, addition to the active and inactive lists could be done with a visitor. Thanks, Leandro.

1 0

compiler -Wshadow warnings
by Bryan Green 17 Jul '07

17 Jul '07

Hello, I'm reporting some warnings I'm getting from gcc when I compile with my code with -Wshadow (Boost 1.34). Not critical, just annoying (makes it harder to catch warnings in my own code). /usr/include/boost/signal.hpp:345: warning: declaration of 'combiner' shadows a member of 'this' /usr/include/boost/signals/signal_template.hpp:348: warning: declaration of 'result_type' shadows a member of 'this' /usr/include/boost/signals/detail/slot_call_iterator.hpp:51: warning: declaration of 'f' shadows a member of 'this' /usr/include/boost/program_options/parsers.hpp:34: warning: declaration of 'description' shadows a member of 'this' /usr/include/boost/variant/variant.hpp:1115: warning: declaration of 'which' shadows a member of 'this' /usr/include/boost/variant/variant.hpp:1120: warning: declaration of 'which' shadows a member of 'this' The variant ones are especially problematic, as the printout of the instantiation heirarchy is several pages long.

1 0

program_options: Are my options too complicated?
by Steven Mackenzie 16 Jul '07

16 Jul '07

Hello, I am writing an application that moves some data through a sequence of possibly optional processing steps, for instance (simplified) 1/ Read and Export Data, optionally exporting it to a text or binary file. 2/ Optionally Normalise the data, optionally exporting to file. 3/ Optionally reduce the size of the data set, optionally exporting the result. 4/ Create a score for the data set, and write the score to a file or socket. Each processing step 1-4 has a set of options, for example step 1 might export the data as a text file or as a binary, and might transpose the data (rows and columns) to make it easier to plot in a spreadsheet. Data output at each processing step 1-3 is optional, and processing steps 1-2 are optional. As described, this sounds like a pipeline of processes, but the customers expectations (and my ability) suggest that this should be a single application*, but with a consequently complicated set of options. I'd like to be able to use program_options to help me parse the command line or config file, and so my plan for the command line is that it would support 4 options (one for each step), for instance with <required options> and [optional options]: app <--export [optional file name [binary|text [transpose]]> [--normalize [optional file name]] [--reduce [optional file name]] <--score <file name or server address> [optional treshold number]> <input file name> I want to allow each option to be given more than once, so that for instance data could be exported as text and binary with app --export file1.bin binary --export file2.txt text transposed ... In another case the command line might be simply app --export --normalize --score file://score.txt input.bin where --export and --normalize are given as boolean switches, and --score has used a default value for the threshold number. In another case, I would like all of the options in a configuration file, and only the input file name would be given on the command line. So my questions: 1/ Could I make my command line simpler? 2/ Will boost::program_options be helpful in this case - I've only used it once before in a much simpler scenario? 3/ What program_options methods should I be looking at? Although the documentation has an excellent set of examples, I'm finding the reference section something of a maze. All sugestions will be gratefully received! Steven * The data set is large, and some processing steps might transform the data in-place. Other steps might depend on the output of more than one steps (for instance step 4 might depend on the results of steps 2 and 3). I hope to make much of the process multi-threaded.

1 0

[1.34.1] Release Candidate 3
by witt＠mailsnare.net 16 Jul '07

16 Jul '07

Hi, The 1.34.1 release candidate 3 is now available from http://www.boost.org/release/ please give it a try and report any problems to the developer list or directly to me. Thomas

1 0

Did not succeed to use algorithm/string on WinCE with MSVC 2005 and PocketPC2003 SDK
by Françoise CONIL 16 Jul '07

16 Jul '07

Hi, I successfully use replace_all function in a win32 "helloboost" application. My code has to work on Windows CE and when I tried a "helloboostpda" application, I had an error on boost/algorithm/string/compare.hpp because of the following include : #include <locale> This seems to be due to PocketPC2003 SDK that does not have a "locale" include (only a locale.h). Is there something I can do to use Boost algorithm/string library on Windows CE ? Thanks Francoise

1 0