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

[program_options] How to extract option value?
by Krzysztof 03 May '11

03 May '11

In order to get the option value I have this code: options_description opd; string in; opd.add_options() ("help","Display help") ("input_file,I",value<string>(),"Input file with group division"); variables_map vm; store(parse_command_line(argc,argv,opd),vm); notify(vm); if(!vm["help"].empty()) cout<<opd<<'\n'; else in = vm["input_file"].as<string>(); However the last line issues this exception: terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::bad_any_cast> >' what(): boost::bad_any_cast: failed conversion using boost::any_cast What do I wrong? -- Regards Krzysztof J.

1 0

[spirit] parsing keyword or identifier
by Brian Budge 03 May '11

03 May '11

HI all - I have what I think is a simple problem: I'm trying to parse IES files, and there is a line that can have three options: TILT=NONE -or- TILT=INCLUDE -or- TILT=<filename> The way I'm trying to parse this line is: // in the case of TILT=INCLUDE or TILT=<filename> int lampToLuminaireGeom; int numPairsWithMulFactors = 0; std::string tiltFileName; BOOST_AUTO(keywordSym, (qi::lit("NONE") | qi::lit("INCLUDE"))); BOOST_AUTO(fileName, *char_ - keywordSym); BOOST_AUTO(initial, ( "TILT" >> char_('=') >> ( "NONE" | ( "INCLUDE" >> int_[ref(lampToLuminaireGeom) = _1] >> int_[ref(numPairsWithMulFactors) = _1] ) | fileName[ref(tiltFileName)] ) ) ); if(!phrase_parse(first, last, initial, space)) { return IES_INVALID; } The code works with NONE or INCLUDE, but not with files. As far as I know, there are no real restrictions on the filenames. At this point, the code posted above can't even get simple file names, but really I think what is required is that I grab anything non-whitespace after the '=' until it reaches an EOL. Can anyone provide some insight about what I may be doing wrong? Thanks, Brian

2 2

[wave] Custom I/O handling (include paths, etc.)?
by Anteru 03 May '11

03 May '11

Hi, I'm trying to adopt Wave as my custom preprocessor for a project. So far, things work fine, but there is one problem with Wave: I need to override all I/O functions, in particular, reading from files and opening files. Reading is easily changed by the input policy, but I couldn't find a way to register an include handler hook. There's found_include_directive, but nothing that allows me to get in-between wave and the filesystem. In my case, I on-demand construct some data which I want to be able to #include (i.e. #include <generated>) and some files are stored in resources/compressed files (#include <zip/file.h>). My include handler can open them, but how can I tell Wave to ask my include handler whether it can find a file instead of using boost::filesystem? Cheers, Anteru

2 4

[Review] Boost.Convert library has ended
by Edward Diener 03 May '11

03 May '11

The review period for the Boost.Convert library has officially ended. I will continue to read posts about the library while I make my review decision, so please do not stop discussing the library as appropriate because the review period has ended. I have received one personal request for a late review, and I am willing to accept any other requests for a late review to be made through Wednesday and posted to the mailing list, but I will not consider any other late review in my decision unless someone requests it of me personally. I know this is a fine line between an official review and just comments about what others have said before, but I need to make my decision based on some finite set of reviews and their subsequent discussion. I would like to thank everyone who has officially reviewed Boost.Convert as well as all who have made subsequent comments. The more input received, the easier it becomes for me as a reviewer to make a final decision. I would also like to thank the implementer of the Boost.Convert library, Vladimir Batov, for his willingness to address issues, answer criticism, and engage in discussion about his library. My review decision should be made and posted to the mailing list no later than by the end of Sunday, May 8.

1 0

Pass data to states, in boost state chart
by jusva2010 03 May '11

03 May '11

Hi All, Is there any way I can pass data to state event handler? Any pointers really appreciated. Thanks in advance Justin -- View this message in context: http://boost.2283326.n4.nabble.com/Pass-data-to-states-in-boost-state-chart… Sent from the Boost - Users mailing list archive at Nabble.com.

2 5

Adapt rule's attribute to my own Boost::Spirit::Qi
by Egor Popov 03 May '11

03 May '11

Hello, everyone. There is a problem of attribute transfomation: I need to transfom rule's generated attribute to my own structure. I tried to parse mathematical formula and store it in std::vector in reverse Polish notation. Formula have form: math = as_string(*digit) >> (alpha) >> +(char_('+' | '-') >> math); rule<Iterator, std::string, space_type> math; Question #1: what type is it? I think that fusion::vector<std::string, char, std::vector<fusion::vector<char, std::string> > > but it seems it is not so. Question #2: how can I convert this structure, to mine (std::vector<std::string>)? -- View this message in context: http://boost.2283326.n4.nabble.com/Adapt-rule-s-attribute-to-my-own-Boost-S… Sent from the Boost - Users mailing list archive at Nabble.com.

1 0

[Multi-index] : code fail to compile with VS2010 and boost 1.46.1. Proposed workaround
by Mathieu Peyréga 03 May '11

03 May '11

Hello, I had some code using boost 1.46.1 Multi-index library that used to compile and work very well with VS2008. I recently turned to VS2010 and some code is not compiling anymore. The problem is located in the boost_1_46_1\boost\multi_index\composite_key.hpp file and the compiler complains about not being able to distinguish between ambiguous overloads... I had to modify the composite_key.hpp file and have following changes : line 1001 : //return operator()(x,make_tuple(cref(y))); return operator()(x,make_tuple(boost::cref(y))); line 1036 : //return operator()(make_tuple(cref(x)),y); return operator()(make_tuple(boost::cref(x)),y); In order to explicitely add the boost namespace for cref. With those changes, it do compile and works very well. Can those changes in composite_key.hpp break something else ? Is there another workaround I would have missed ? I'm suspecting some conflict with new TR1 things i'm not very familiar with... Best regards, Mathieu Peyréga

3 7

[Spirit][Date_Time] Parsing of boost date_time (segfault)
by Vitaly Budovski 03 May '11

03 May '11

Hi, I had a go at building a binary parser to output a date/time object. Unfortunately, I ran into some serious issues. One of my grammars causes the application to segfault when compiled with gcc, but not in clang. I'm not sure if this is a bug in gcc, boost, or simply a programming error. Please see attached file. Is there a better way to achieve what I need (final output should be ptime object)? All suggestions welcome :) Thanks, Vitaly

3 3

[Serialization - 1.46.1] : Suggestion
by Mathieu Peyréga 03 May '11

03 May '11

Hello, Here is a small feature suggestion : I've been modifying the nvp.hpp file and added after line 142 the following macro definition : // Added by Mathieu Peyréga #define BOOST_SERIALIZATION_BASE_OBJECT_TEMPLATE_NVP(name,templateparameter) \ boost::serialization::make_nvp( \ BOOST_PP_STRINGIZE(name)BOOST_PP_STRINGIZE(templateparameter), \ boost::serialization::base_object<name<templateparameter> >(*this) \ ) // Which enables "easier" serialization for case like the following where the is multiple heritage and one of the base class is a template. Do you think this is the good way to go ? Best regards, Mathieu Peyréga /*************************************************************************************************** Short example of the BOOST_SERIALIZATION_BASE_OBJECT_TEMPLATE_NVP macro ***************************************************************************************************/ class C_Battery : public C_PhysicalElement, public C_GenericDatabaseObject<C_Battery> { public: C_Battery(void); C_Battery(C_Battery const& obj); C_Battery& operator=(C_Battery const& obj); virtual ~C_Battery(void); Boolean operator==(C_Battery const& other) const; Float64 getTensionPerElement(void) const; Float64 getCapacityPerElement(void) const; Float64 getFaradicEfficiency(void) const; Float64 getUnloadDeepness(void) const; Float64 getVolumicInstallationCost(void) const; Float64 getNumberOfCycles(void) const; Float64 getMonthlySelfLosses(void) const; void setTensionPerElement(Float64 const& value); void setCapacityPerElement(Float64 const& value); void setFaradicEfficiency(Float64 const& value); void setUnloadDeepness(Float64 const& value); void setVolumicInstallationCost(Float64 const& value); void setNumberOfCycles(Float64 const& value); void setMonthlySelfLosses(Float64 const& value); void loadFromCSVDatabase(C_CSVFileParser const& parser, Int32 recordIndex); protected: friend class C_GenericDatabaseObject<C_Battery>; Float64 m_TensionPerElement; // Tension par élément en Volts Float64 m_CapacityPerElement; // Capacitée par élément en A*h Float64 m_FaradicEfficiency; // Rendement faradique Float64 m_UnloadDeepness; // Profondeur de décharge Float64 m_VolumicInstallationCost; // Cout d'installation en euro/dm3 Float64 m_NumberOfCycles; // Nombre de cycles à la profondeur autorisée Float64 m_MonthlySelfLosses; // Auto décharge mensuelle friend class boost::serialization::access; template<class Archive> void serialize(Archive & ar, const unsigned int version) { ar & BOOST_SERIALIZATION_BASE_OBJECT_NVP(C_PhysicalElement); ar & BOOST_SERIALIZATION_BASE_OBJECT_TEMPLATE_NVP(C_GenericDatabaseObject,C_Battery); ar & BOOST_SERIALIZATION_NVP(m_TensionPerElement); ar & BOOST_SERIALIZATION_NVP(m_CapacityPerElement); ar & BOOST_SERIALIZATION_NVP(m_FaradicEfficiency); ar & BOOST_SERIALIZATION_NVP(m_UnloadDeepness); ar & BOOST_SERIALIZATION_NVP(m_VolumicInstallationCost); ar & BOOST_SERIALIZATION_NVP(m_NumberOfCycles); ar & BOOST_SERIALIZATION_NVP(m_MonthlySelfLosses); } }; BOOST_CLASS_VERSION(C_Battery, 1)

1 0

Re: [Boost-users] Thread Safety of shared_ptr
by Kevin Frey 03 May '11

03 May '11

> shared_ptr< Session >* is not a shared ptr, it is a RAW ptr to shared_ptr< Session>. Yes, I know this. The pointer you call the RAW pointer is owned only by one object. It doesn't make the implementation wrong. My issue concerns the addref/decref behaviour that occurs simultaneously within two different threads.

1 0