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

#define BOOST_ASSERT_MSG_OSTREAM std::cout - message is not displayed
by asif saeed 03 Aug '11

03 Aug '11

Hi, After I have #defined BOOST_ASSERT_MSG_OSTREAM std::cout, using BOOST_ASSERT_MSG with a customized message does not display the message and, instead, I get the following message from Visual C++ 2010 Express: R6010 Abort() has been called What can I do to display the customized message? Best, Asif

1 0

Boost Book - comments?
by Robert Jones 03 Aug '11

03 Aug '11

Morning All Does anyone have any knowledge of this book? http://www.amazon.co.uk/Boost-C-Libraries/dp/3639942310/ref=sr_1_7?s=books&… <http://www.amazon.co.uk/Boost-C-Libraries/dp/3639942310/ref=sr_1_7?s=books&…>It's genesis, currency, provenance, and possibly a few review-like comments? Thx - Rob.

2 2

Re: [Boost-users] boost.regex with ICU memory cleanup on windows
by Alex Perry 03 Aug '11

03 Aug '11

John Maddock wrote on Tue, 2 Aug 2011 12:14:53 +0100 > There are a number of issues here: > > 1) Your call to u_cleanup() occurs while a u32regex object is still in existence, > so any ICU data being cached is actually still being used at that point. I couldn't get u_cleanup() to work anywhere - ie BOOST_AUTO_TEST_CASE( u32_regex ) { { boost::u32regex re( boost::make_u32regex("\\d{3}")); } u_cleanup(); } Or having u_cleanup() in a fixture teardown (which is how it was in the original code) doesn't seem to make any difference > 2) Boost.Regex does cache some internal data for improved performance - > this is relatively small and gets cleared after main() exits. > 3) Point (2) means that a call to _CrtDumpMemoryLeaks() before main exits > will report leaks, where as using something like: > > struct cleanup > { > ~cleanup() > { > _CrtDumpMemoryLeaks(); > } > }; > > cleanup c; The boost unit test framework does appear to do the memory dump in a destructor of a static object - I guess whether the regex library statics are destructed first depends on the order of loading - not sure if there is any easy way of ensuring that the unit test framework is destructed last (perhaps if I link to UTF as a static library?). > 4) Other leak detectors such as valgrind and VLD report no errors (and give > much more useful reports than the brain-dead MS ones IMO). > > HTH, John. :-) yes I agree - my current solution is --detect_memory_leaks=0 when running the unit tests - which at least stops the report. I was hoping that this was a reasonably common issue and there was some clean up function (like u_cleanup()) specifically for the regex library but if not can live with switching off memory loss detection. Thanks a lot for the help here though - it is much appreciated. Alex

2 1

Re: [Boost-users] [Repost][Boost][Serialization] ASSERTtriggered during reading 1.40 binary archive w/ Boost 1.47
by marc.viala＠sfr.fr 03 Aug '11

03 Aug '11

> De la part de Pfligersdorffer, Christian > > We were facing similar problems jumping from 1.36 to 1.45. > Binary archive backwards compatibility is broken in a few places. > > But: it is fixable. We may provide a patch Thanks Christian for your reply to this annoying issue. If you confirm that the backward compatibility is broken for Boost.Serialization #1.40 to #1.47 then *Yes* I would really appreciate any king of patch to address this issue. Looking the Boost.Serialization code, my first feeling would be to patch the implementation of basic_binary_iarchive::load_override(class_id_type & t, int version) for the library_version_type(5) ('5' stands for the library version for the release #1.40) but maybe this patch is too naïve and insufficient. If you can send me back a patch for this issue, I'll use it ASAP. > is there a TRAK ticket? I'm not sure but the ticket #5567 (https://svn.boost.org/trac/boost/ticket/5567) seems to address this bug. Thanks in advance and best regards, Marc Viala

1 0

Re: [Boost-users] [Repost][Boost][Serialization] ASSERT triggeredduring reading 1.40 binary archive w/ Boost 1.47
by Pfligersdorffer, Christian 03 Aug '11

03 Aug '11

We were facing similar problems jumping from 1.36 to 1.45. Binary archive backwards compatibility is broken in a few places. But: it is fixable. We may provide a patch - is there a TRAK ticket? Regards, -- Christian Pfligersdorffer Software Engineering www.eos.info > -----Ursprüngliche Nachricht----- > Von: boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] Im Auftrag von > Marc Perso > Gesendet: Mittwoch, 3. August 2011 07:30 > An: boost-users(a)lists.boost.org > Betreff: [Boost-users] [Repost][Boost][Serialization] ASSERT triggeredduring reading 1.40 binary archive > w/ Boost 1.47 > > Let me forward this message posted few days ago since nobody has confirmed > that the issue described hereafter exists. I would really appreciate if > someone could take a look (maybe Mr Robert Ramey) and give some advice on > this subject. > > Best regards, > > Marc Viala > > ------------------------------------------------------------------------ > > Hello Booster, > > We are trying to jump from Boost 1.40 to Boost 1.47 but we are facing an > issue: an ASSERT is raised in debug mode when reading back binary archive > generated by Boost.Serialization 1.40 with the Boost.Serialization 1.47. > This ASSERT is at line 116 in basic_archive.hpp: > > BOOST_ASSERT(t_ <= boost::integer_traits<base_type>::const_max) > > And it occurs with the following platform: MSVC 8.0 and Windows XP/32bits or > Win7/64bits. > > Looking at the load_override and save_override implementations for > class_id_type in #1.40, they seem loading and saving an 'int_least16_t' > (equiv. to a short for our platform) while load_override(class_id_type) for > #1.47 attempts to read an 'int' (file: basic_binary_iarchive.hpp @ line 98). > > My questions are: > - This assert suggests that we can't read back previous binary archives > (#1.40 at least) with Boost.Serialization 1.47, is this a known pending > issue for Boost.Serialization? > > - If yes, how we can manage that and how we can complete the migration to > 1.47 in our case (it should be noted that we must be able to read back our > 1.40 binary archives)? Is there any known patch for this problem? > > Any assistance will be greatly appreciated. > > Best regards, > > Marc Viala > > PS: I'm not sure but ticket #5567 seems already opened on this issue but has > not been yet fixed (https://svn.boost.org/trac/boost/ticket/5567) > > > > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > http://lists.boost.org/mailman/listinfo.cgi/boost-users

1 0

Boost.Tokenizer / Sep - Compile-time errors ...
by asif saeed 03 Aug '11

03 Aug '11

Hi, Here is a piece of code that _only_ works when I provide it a hard-coded constant ";": typedef boost::char_separator<char_type_t> sep_type_t; typedef boost::tokenizer<sep_type_t> tokenizer_t; sep_(pa_->separator_.c_str()), t_(messageString,sep_), i_(t_.begin()) It wouldn't work with the separator passed in a variable (pa_->separator.c_str()). Tokenizer wouldn't work even if I initialize a const char* with a ";" and then pass that const char *variable to sep_ above. It gives me the following errors on if I pass separator in a variable: error C2780: 'bool boost::char_separator<Char>::operator ()(InputIterator &,InputIterator,Token &)' : expects 3 arguments - 1 provided Any idea how I can pass it a separator in a variable? Best, Asif

2 2

[Repost][Boost][Serialization] ASSERT triggered during reading 1.40 binary archive w/ Boost 1.47
by Marc Perso 03 Aug '11

03 Aug '11

Let me forward this message posted few days ago since nobody has confirmed that the issue described hereafter exists. I would really appreciate if someone could take a look (maybe Mr Robert Ramey) and give some advice on this subject. Best regards, Marc Viala ------------------------------------------------------------------------ Hello Booster, We are trying to jump from Boost 1.40 to Boost 1.47 but we are facing an issue: an ASSERT is raised in debug mode when reading back binary archive generated by Boost.Serialization 1.40 with the Boost.Serialization 1.47. This ASSERT is at line 116 in basic_archive.hpp: BOOST_ASSERT(t_ <= boost::integer_traits<base_type>::const_max) And it occurs with the following platform: MSVC 8.0 and Windows XP/32bits or Win7/64bits. Looking at the load_override and save_override implementations for class_id_type in #1.40, they seem loading and saving an 'int_least16_t' (equiv. to a short for our platform) while load_override(class_id_type) for #1.47 attempts to read an 'int' (file: basic_binary_iarchive.hpp @ line 98). My questions are: - This assert suggests that we can't read back previous binary archives (#1.40 at least) with Boost.Serialization 1.47, is this a known pending issue for Boost.Serialization? - If yes, how we can manage that and how we can complete the migration to 1.47 in our case (it should be noted that we must be able to read back our 1.40 binary archives)? Is there any known patch for this problem? Any assistance will be greatly appreciated. Best regards, Marc Viala PS: I'm not sure but ticket #5567 seems already opened on this issue but has not been yet fixed (https://svn.boost.org/trac/boost/ticket/5567)

1 0

Time management using posix time
by Sarkar, Arup 03 Aug '11

03 Aug '11

Hi: This is what is I am trying to achieve. I would like to run the program for 6 minutes, within the six minutes I would like to toggle for 2 minutes data operation and for 1 minute trade operation, so there will be 2 cycle of data operation and 2 cycle of trade operation. I am setting and getting the ptime outside the main program, but what is happening is that the getPtime of the template class is always return the +2 minutes of the current time, that is why diff is never reducing less than 2 minutes, why is that happening, the setter have been instantiated only once. I would really appreciate if someone can help me out. [code] // boost_example.cpp : Defines the entry point for the console application. // #include "boost/date_time/posix_time/posix_time.hpp" #include <iostream> #include <stdio.h> #include <stdio.h> #include "windows.h" using namespace std; template <typename ptime_type> class timeManagement { private: ptime_type tradingTime; public: timeManagement(){}; void setPtime (const ptime_type& _val){tradingTime = _val; } ptime_type const& getPtime() {return (tradingTime);} ~timeManagement(){}; }; int main() { bool btradingIndicator = false; std::ostringstream msg; using namespace boost::posix_time; const ptime start = second_clock::local_time(); time_duration td = minutes(6); time_duration tdDataCollection = minutes(2); time_duration tdTrading = minutes(1); bool bTradingIndicator = false; const ptime end = start + td; const ptime tTimeWindow = start + tdDataCollection; int i = 0; int switchTime = 0; timeManagement <ptime> tradingWindow; tradingWindow.setPtime(tTimeWindow); //std::cout << tradingWindow.getPtime() << std::endl; while(second_clock::local_time() <= end){ ptime currentTime = second_clock::local_time(); time_duration diff = tradingWindow.getPtime() - currentTime; if(diff.total_seconds() >= 0 && !bTradingIndicator){ std::cout << "Data.) " << currentTime << "|" << tradingWindow.getPtime() << "|" << diff << std::endl; }else{ const ptime tTimeWindow1 = currentTime + tdTrading; tradingWindow.setPtime(tTimeWindow1); bTradingIndicator = true; } if(diff.total_seconds() >= 0 && bTradingIndicator){ std::cout << "Trade.) " << diff << std::endl; }else{ const ptime tTimeWindow2 = currentTime + tdDataCollection; tradingWindow.setPtime(tTimeWindow2); bTradingIndicator = false; } } std::cout << "Start Time: " << start << std::endl; std::cout << "End Time: " << end << std::endl; std::cout << "Time Now: "<< end << std::endl; return 0; } [/code] Regards, Arup *"I don't need to know everything, I just need to KNOW where to find it, when I need it"*. -*Albert Einstein *

1 0

Re: [Boost-users] What's wrong with this simple multithreaded function that uses regex?
by Andrew Yancy 03 Aug '11

03 Aug '11

>I don't see anything obviously wrong with that. My only question, is you >say BOOST_HAS_THREADS is defined, are you defining it, or is Boost.Config >defining it (if Boost.Config *isn't* setting it, then your project >settings >are wrong for multithreaded code)? Are you selecting the regex lib to >link >to manually or letting the auto-linking code do it's work (for minimum >chances of bad things happening you should let the auto-linking code >select >the correct binary)? >HTH, John. >You should use _beginthread or _beginthreadex to start C++ thread when >using >MSVC. >CreateThread is too low level and does not do the per thread >initialization >required. If you read MSDN documentation it explain why CreateThread >cannot >be use with C++ program. >Daniel Anderson Thanks for the replies John and Daniel. I've reinstalled boost 1.47 making sure that all the multithreaded options were built and am using _beginthreadex() now, but the exact same problem seems to occur where the code snippet below crashes if and only if boost::regex_match() is called. I am not defining BOOST_HAS_THREADS in my code, it is defined automatically although I'm not sure how exactly. Also, as far as I know I am not manually linking to the necessary libraries; all I do is tell MSVC to look in "C:\Program Files\boost\boost_1_47_0\stage\lib" for additional libraries so presumably it chooses whichever one it needs. There are no thread or boost-related warnings in the build. Any other ideas? I really appreciate the help~ ... static const boost::regex expression("^[0-9]+"); ifstream myfile(x); //x is a different file name for every thread string line; if(myfile.is_open()) { while(myfile.good()) { getline(myfile, line); if(boost::regex_match(line, expression)) { //do stuff } } myfile.close(); } ...

2 2

[program_options] Best practices, esp. for multi-app-projects?
by Carlos Franke 02 Aug '11

02 Aug '11

I am wondering if there is a recommended way how the boost::program_options library should be integrated in a (relatively) complex project. To be more specific, these are my situation and my requirements: – A C++ project consisting of several applications, which are to share many, but not all options. – The interface to the options used in each app's code should be as boost-unspecific (i. e. abstract) as possible, so that I could later switch to another option library without having to edit much more than one file. – The option data should be somehow encapsulated. After pondering on this task for quite some time, I came up with this: – A single header file "options.h" shared by all the applications, providing a function read_options(int argc, char* argv[], const po::options_description& local_options = 0) , which scans the command line and the usual configuration files* for the common options (which are defined in the same header file, of course) as well asoptional app-specific options, and saves them (next paragraph). *(There is of course the problem of each app's name being part of its config-file's name. I found a solution for this, but I am not sure if it is relevant here. Or is it?) – Regarding the encapsulation, I found any kind of class or struct containing the options (possibly with get and set methods) unsuitable or overkill, as I would have to deal with instantiation and possible problems of multiple instantiation (singleton?). Also, I did not feel the need for the security provided by get and set methods. So what I did is: put all option variables in one namespace, like this: namespace options { int option1; std::string option2; ///... } A namespace has the further great advantage of being extendable after creation. Programme-specific options can be added easily. So in the end, in each programme I only have to do: //optional: define local options namespace options { /* . . . */ } po::options_description my_options /* . . . */ ; //read and save options: options::read_options(argc, argv, my_options) //from now on access the options' values by //options::option1; As I see it, this approach has only two drawbacks: – In each programme's code I have to deal with options twice: 1) declare the storage variables in the options namespace (globally); 2) declare local options_description and call read_options (in the main function). – There is no way to tell if the option variables are in a valid state, unless one is sure that read_options has been called and has set all values (at least to valid default values). I am inclined to tolerate the first issue and resolve the second by: – not using "default_value" in any po::options_description – instead intializing the option variables with their default values. That way, at any time each option variable either stores its default value or the assigned to it from the command line or a configuration file. Oh my, that ended up much longer than I expected. Those of you who read this far: What are your thoughts about using boost::program_options in general and about my particular approach? Regards! Carlos Franke

1 0