- Boost-users - lists.boost.org

[Serialization] 1.33 RC1 Problem linking void_cast_register
by Richard Jennings 04 Aug '05

04 Aug '05

My application that works with 1.32 is failing to link with 1.33 RC1 due to boost::serialization::void_cast_register (specialised for my classes) being an unresolved external. In my case the void_cast_register call and the BOOST_CLASS_EXPORT macro are in one module while the serialization is done in another module, with all modules linked in one application. The code below also shows this problem, however if I add an archive class and header to the example then it will compile and link ok. Obviously this is when serialization is in the same module as the void_cast_register call. Any suggestions about what I need to add to make the application link? Richard ************************************************************************ ******* #pragma hdrstop #include <boost/serialization/is_abstract.hpp> #include <boost/serialization/serialization.hpp> #include <boost/serialization/export.hpp> #pragma link "libboost_serialization-bcb-mt-d-1_33.lib" class Z { public: virtual void DoSomething() =0; }; BOOST_IS_ABSTRACT(Z) class A : public Z { public: void DoSomething(){}; private: friend class boost::serialization::access; template<class Archive> void serialize(Archive & ar, const unsigned intversion) { ar & boost::serialization::make_nvp("A", m_A); } int m_A; }; class B : public Z { public: void DoSomething(){}; private: friend class boost::serialization::access; template<class Archive> void serialize(Archive & ar, const unsigned intversion) { ar & boost::serialization::make_nvp("B", m_B); } int m_B; }; BOOST_CLASS_EXPORT(A) BOOST_CLASS_EXPORT(B) int main(int argc, char* argv[]) { boost::serialization::void_cast_register<A, Z>(0,0); boost::serialization::void_cast_register<B, Z>(0,0); return 0; } Errors: [Linker Error] Unresolved external 'const boost::serialization::void_cast_detail::void_caster& boost::serialization::void_cast_register<A, Z>(const A *, const Z *)' referenced from D:\PROJECTS\...\SOURCE\TEST\BUILD\MAIN.OBJ [Linker Error] Unresolved external 'const boost::serialization::void_cast_detail::void_caster& boost::serialization::void_cast_register<B, Z>(const B *, const Z *)' referenced from D:\PROJECTS\...\SOURCE\TEST\BUILD\MAIN.OBJ

3 3

Boost.Spirit question
by Brad Retzlaff 04 Aug '05

04 Aug '05

I've having a hard time getting my parser to work correctly. I'm trying to create a script parser to create tests, actions, and groups defined in a file. I have the grammer working except for one small issue. I can't get rid of the closing quote on my sentence. It skips the first one just fine. I'm using spirit 1.6.2 The script is below named script.txt: ---------------------- Groups {G100, "This is group G100", G200, "This is group G200" } Actions {A100, "This is an action" } Tests {T100, "This is a test", 0, 5, "VDC" } TestFlow {a } ---------------------------------- I want to have the option of using double quotes (") around strings for the discriptions in Groups, Actions, and Tests section to make it easier to read. I use comma as a delimiter. Here is my spirit code below: ---------------------------------- #include <iostream> #include <fstream> #include <vector> #if defined(_DEBUG) //#define BOOST_SPIRIT_DEBUG #endif // defined(_DEBUG) #include "boost/spirit.hpp" #include <boost/spirit/core.hpp> #include <boost/spirit/utility.hpp> #include <boost/spirit/symbols.hpp> //////////////////////////////////////////////////////////////////////////// /// // used namespaces using namespace boost::spirit; using namespace std; namespace { void my_action(char const* first, char const* last) { std::string str(first, last); std::cout << str << std::endl; } void my_number(float val) { std::cout << val << std::endl; } } struct script_grammar : public grammar<script_grammar> { template <typename ScannerT> struct definition { definition(script_grammar const& self) { Group_Composite = Group >> BeginBrace >> +Group_Action_Parms >> EndBrace; Action_Composite = Action >> BeginBrace >> +Group_Action_Parms >> EndBrace; Test_Composite = Test >> BeginBrace >> +Test_Parms >> EndBrace; TestFlow_Composite = TestFlow >> BeginBrace >> +TestFlow_Parms >> EndBrace; Group = as_lower_d[str_p("groups")]; Group_Action_Parms = Token[&my_action] >> Comma >> Token[&my_action] >> !Comma; Action = as_lower_d[str_p("actions")]; Test = as_lower_d[str_p("tests")]; Test_Parms = Token[&my_action] >> Comma >> Token[&my_action] >> Comma >> real_p[&my_number] >> Comma >> real_p[&my_number] >> Comma >> Token[&my_action] >> !Comma; TestFlow = as_lower_d[str_p("testflow")]; TestFlow_Parms = Token; BeginBrace = ch_p('{'); EndBrace = ch_p('}'); Comma = ch_p(','); Token = +Token_Sub; Token_Sub = alnum_p; //(alnum_p - ch_p(34)); // ^ ch_p('\"')); first = *( Group_Composite | Action_Composite | Test_Composite ) >> TestFlow_Composite; BOOST_SPIRIT_DEBUG_RULE(Group_Composite); BOOST_SPIRIT_DEBUG_RULE(Action_Composite); BOOST_SPIRIT_DEBUG_RULE(Test_Composite); BOOST_SPIRIT_DEBUG_RULE(TestFlow_Composite); BOOST_SPIRIT_DEBUG_RULE(Group); BOOST_SPIRIT_DEBUG_RULE(Group_Action_Parms); BOOST_SPIRIT_DEBUG_RULE(Action); BOOST_SPIRIT_DEBUG_RULE(Test); BOOST_SPIRIT_DEBUG_RULE(Test_Parms); BOOST_SPIRIT_DEBUG_RULE(TestFlow); BOOST_SPIRIT_DEBUG_RULE(TestFlow_Parms); BOOST_SPIRIT_DEBUG_RULE(BeginBrace); BOOST_SPIRIT_DEBUG_RULE(EndBrace); BOOST_SPIRIT_DEBUG_RULE(Comma); BOOST_SPIRIT_DEBUG_RULE(Token); BOOST_SPIRIT_DEBUG_RULE(first); BOOST_SPIRIT_DEBUG_RULE(Token_Sub); } rule<ScannerT> Group_Composite, Action_Composite, Test_Composite, TestFlow_Composite, Group, Group_Action_Parms, Action, Test, Test_Parms, TestFlow, TestFlow_Parms, BeginBrace, EndBrace, Comma, Token, Token_Sub; rule<ScannerT> first; rule<ScannerT> const& start() const { return first; } }; }; struct skip_grammar : public grammar<skip_grammar> { template <typename ScannerT> struct definition { definition(skip_grammar const& /*self*/) { skip = space_p | ch_p('\"') ; BOOST_SPIRIT_DEBUG_RULE(skip); } rule<ScannerT> skip; rule<ScannerT> const& start() const { return skip; } }; }; template<typename GrammarT> void parse(GrammarT const& g, char const* filename) { ifstream in(filename); if (!in) { cerr << "Could not open input file: " << filename << endl; return; } in.unsetf(ios::skipws); // Turn off white space skipping on the stream vector<char> vec; std::copy( istream_iterator<char>(in), istream_iterator<char>(), std::back_inserter(vec)); vector<char>::const_iterator start = vec.begin(); vector<char>::const_iterator end = vec.end(); skip_grammar skip; parse_info<vector<char>::const_iterator> result = parse(start, end, g, skip); if (result.full) cerr << filename << " Parses OK" << endl; else { cerr << filename << " Fails Parsing" << endl; for (int i = 0; i < 50; i++) { if (result.stop == end) break; cerr << *result.stop++; } cerr << endl; } } // main entrypoint int main(int argc, char* argv[]) { // Start grammar definition cerr << "Start of Parsing ..." << endl; // main driver code script_grammar g; if (2 == argc) parse(g, argv[1]); else cerr << "No filename given" << endl; return 0; } The output looks like this: Start of Parsing ... G100 This is group G100" G200 This is group G200" A100 This is an action" T100 This is a test" 0 5 VDC" c:\script.txt Parses OK I'm trying to get rid of the quote on the end. Please help. Thanks, Brad Brad Retzlaff Design Engineer Functional Test Development Plexus Technology Group 55 Jewelers Park Dr. PO Box 677 Neenah, WI 54957 Phone: (920) 720-6733 Fax: (920) 751-5366 http://www.plexus.com <http://www.plexus.com/>

1 0

program options config file format?
by Matthias Kaeppler 04 Aug '05

04 Aug '05

Hi, the program_options reference talks about being able to parse config files, but doesn't mention a thing about its layout. No examples are shown how a file has to look like to be parsable by program_options. Any ideas? Besides the layout, which characters are treated as comments? -- Matthias Kaeppler

1 1

[signals] 2 (and a half?) bugs: slot leaks, access violation
by Ames Andreas 04 Aug '05

04 Aug '05

Hi, I'm a newbie so please be forbearing when I have made wrong assumptions. I have attached two simple test programs simple.cc and simple1.cc to illustrate the (presumable) bugs. I currently use VC 7.1 and Boost 1.32.0 on WinXP. The access violation in simple.cc (when built with NDEBUG) occurs when I try to emit a signal without slots. Documentation seems to state that in this case the return value of the emission is undefined, which seems to imply that the actual call should work (which it should anyway, IMHO). When I compile with _DEBUG defined I get the following assertion thrown at me: <assertion> Assertion failed: first != last, file boost/boost/last_value.hpp, line 23 </assertion> simple1.cc shows a very basic slot leakage, you will see 9 constructor calls but only 8 destructor calls for the handler. This could be caused by having pos.impl_->group->second.erase(pos.impl_->slot_); commented out in named_slot_map.cpp:230. The half bug I mentioned in the subject is the one which I am least sure about. simple1.cc shows that my callback functor is copied eight times during connect (that obviously implies seven destructor calls). Isn't that a performance issue? TIA, aa -- Andreas Ames | Programmer | Comergo GmbH | Voice: +49 69 7505 3213 | andreas . ames AT comergo . com

2 1

[OT] Information regarding template (instantiation) and compiler/linker performance
by Ames Andreas 04 Aug '05

04 Aug '05

Hi, although not directly boost related, I think the needed expertise is certainly here and the answer to my question might be of common interest. Can someone point me to information resources about differences in handling (removal of duplicated class instantiations, name resolution rules for identifiers in template definitions etc.) of and compiler/linker performance regarding templates? I'm mainly interested in gcc and vc7; I've already read the discussion about frepos in the gcc manual but found nothing about vc7. For both of them but also for other tool chains I would be happy about further and more detailed resources. TIA, aa -- Andreas Ames | Programmer | Comergo GmbH | Voice: +49 69 7505 3213 | andreas . ames AT comergo . com

1 0

Notes on installing Boost with Mac OS X
by Graeme Mathieson 04 Aug '05

04 Aug '05

Hi, I'm pretty new to using Boost. Actually, I haven't really used it at all yet. :-) But I've managed to get it installed on Mac OS X 10.4 and usable with Boost.Build v2 and I thought I'd share my experiences in case it's of any use to others. You can find them here: http://woss.name/2005/08/03/boosting-mac-os-x/ In particular, I'm curious to know if the boost.jam file I created is even vaguely the right way to go about getting Boost to work with Boost.Build or if I've just missed something obvious. Cheers, Graeme. -- Mail: mathie(a)woss.name | Web: http://woss.name/ AIM: Math1e | PGP: 1024D/D72F2737

1 0

optional + serialize
by Jasper, Alexander 03 Aug '05

03 Aug '05

Hi Jeff, All! thanks a lot for the reply. I assume the bug fix is in 1.33? I'm still having issues with boost.optinal and boost.serialize working together (in 1.32). Is for deserialization of boost::optional<T> T required to have default ctor?. This prevents boost::optional<boost::posix_time::time_period> from being serialized. The extraction code fails to compile. I would an ugly way around this (please see my last email). Does anybody have ideas for better solutions? I've attached a modified version of #include <boost/serialization/optional.hpp> to this email, that contains code changes to make to work with types w/o T having a default ctor. But I'm really unhappy with that solution and I don't know what I broke with this change... thanks in advance Alex > -----Ursprüngliche Nachricht----- > Von: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org]Im Auftrag von > Jeff Garland > Gesendet: Freitag, 29. Juli 2005 15:40 > An: boost-users(a)lists.boost.org > Betreff: Re: [Boost-users] questions concerning optional + date_time > +serialize > > > On Fri, 29 Jul 2005 15:21:38 +0200, Jasper, Alexander wrote > >... > > Another thing is that I'm unable to serialize not_a_date_time > > ptimes. The extractions fails here. I'm using the binary > archive. Is > > that supported? The documentation of date time only states > > compatibility with text and XML archive... > > There was a recent (jun 21) bug-fix in date-time that was > preventing correct > serialization of special values -- even with text archives -- > so it's likely > that's what you are seeing. I haven't tried the binary > archive, but there's > no reason it shouldn't work. I believe you should be able to > just pickup the > latest version of gregorian/greg_serialize.hpp and > posix_time/time_serialize.hpp to try it out. > > Jeff > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > http://lists.boost.org/mailman/listinfo.cgi/boost-users >

2 1

date_time | VC71 | dynamic link
by John Smith 03 Aug '05

03 Aug '05

I have been trying to use Boost Date_Time library with my code. I used boostjam to compile the source; the command used was: bjam -s"TOOLS=vc-7_1" --with-date_time install. The following libraries were built (among others): boost_date_time-vc71-mt-1_32.dll 45,056bytes boost_date_time-vc71-mt-1_32.lib 26,164bytes libboost_date_time-vc71-mt-1_32.lib 521,764bytes boost_date_time-vc71-mt-gd-1_32.dll 77,824bytes boost_date_time-vc71-mt-gd-1_32.lib 26,312bytes libboost_date_time-vc71-mt-gd-1_32.lib 1,380,694bytes My project is setup as follows: Runtime Library: Multi-threaded Debug DLL (/MDd) Additional Include Directories: $(BOOSTHOME)\include\boost-1_32 Additional Library Directories: $(BOOSTHOME)\lib Additional Dependencies: boost_date_time-vc71-mt-gd-1_32.lib Using the above setup I could only link if the static library (libboost_date_time-vc71-mt-gd-1_32.lib) was also available. If not, I kept getting LINK : fatal error LNK1104: cannot open file 'libboost_date_time-vc71-mt-gd-1_32.lib' However, when this file is available, I am able to link and use the DLL (checked DLL usage using depends.exe). Does this make sense? I was under the impression that I should only need the import library. Also, how does it know the name if the library? Thanks.

3 4

problem with float or double serialization with binary archive VC 7.1 boost1.32 and 1.33
by Stephane Martineau 03 Aug '05

03 Aug '05

Hye, this little program fail in serialization of a float with binary archive but success with xml or text archive ?? as i am not an expert, i have now idea why ??? i have the save problem with double and like with float, only depending of the value .... it fails under windows XP, VC++7.1 but success under Linux + gcc thanks for helping , Stéphane. // problemeserialisation.cpp // #include <iostream> #include <fstream> #include <boost/archive/text_oarchive.hpp> #include <boost/archive/text_iarchive.hpp> #include <boost/archive/binary_oarchive.hpp> #include <boost/archive/binary_iarchive.hpp> #include <boost/archive/xml_oarchive.hpp> #include <boost/archive/xml_iarchive.hpp> void test_binary (float & f) { using namespace std ; std::ofstream ofs("val.bin"); boost::archive::binary_oarchive oa(ofs,std::ios::binary); oa<< f ; ofs.close(); std::cout << "Valeur serialisee binary " << f << std::endl ; std::ifstream ifs("val.bin"); boost::archive::binary_iarchive ia(ifs,std::ios::binary); float f1; ia >> f1; if (ifs.fail()) { cout << "badbit " << ( ifs.rdstate( ) & ios::badbit ) << endl; cout << "failbit " << ( ifs.rdstate( ) & ios::failbit ) << endl; cout << "eofbit " << ( ifs.rdstate( ) & ios::eofbit ) << endl; } std::cout << "Valeur deserialisee binary "<< f1 << std::endl ; ifs.close(); return ; } void test_text (float & f) { std::ofstream ofs("val.txt"); boost::archive::text_oarchive oa(ofs); oa << f ; ofs.close(); std::cout << "Valeur serialisee Texte " << f << std::endl ; std::ifstream ifs("val.txt"); boost::archive::text_iarchive ia(ifs); float f2 ; ia >> f2; std::cout << "Valeur deserialisee Texte "<< f2 << std::endl ; ifs.close(); return ; } void test_xml (float & f) { std::ofstream ofs("val.xml"); boost::archive::xml_oarchive oa(ofs); oa << BOOST_SERIALIZATION_NVP(f) ; ofs.close(); std::cout << "Valeur serialisee Xml " << f << std::endl ; std::ifstream ifs("val.xml"); boost::archive::xml_iarchive ia(ifs); float f2 ; ia >> BOOST_SERIALIZATION_NVP(f2); std::cout << "Valeur deserialisee Xml "<< f2 << std::endl ; ifs.close(); return ; } int main (int argc, const char * argv[]) { float f1 = (float)2.411667 ; test_text(f1); test_xml(f1); test_binary(f1); return 0; } output : Valeur serialisee Texte 2.41167 Valeur deserialisee Texte 2.41167 Valeur serialisee Xml 2.41167 Valeur deserialisee Xml 2.41167 Valeur serialisee binary 2.41167 badbit 0 failbit 2 eofbit 1 Valeur deserialisee binary -1.07137e+008

2 2

Re: [Boost-users] [1.33.0] Release candidate #1 is available
by Richard Jennings 03 Aug '05

03 Aug '05

The date_time library fails to compile with Borland C++ 5.6.4 for want of the recursive functions such as localtime_r etc. Borland needs adding to the list of compilers not supporting these functions in date_time/compiler_config.hpp. I built RC1 by replacing Spirit 1.8.x supplied with RC1 with Spirit 1.6 and then did: > bjam "-sTOOLS=borland" --without-wave stage The wave library requries Spirit 1.8.x so I chose to exclude it from the build. Richard -----Original Message----- From: boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Doug Gregor Sent: 01 August 2005 18:04 To: boost-users(a)lists.boost.org Subject: [Boost-users] [1.33.0] Release candidate #1 is available Boost 1.33.0 release candidate #1 is now available here: http://www.osl.iu.edu/~dgregor/boost-1.33.0/ There are two sets of files important for this release: - boost_1_33_0_rc1.*: The actual release candidate - boost_1_33_0_(docbook|fo|man).*: The documentation in other formats Please download and unpack the archives, browse the documentation, try the release with your favorite compiler, etc. Thanks! Doug Gregor 1.33.0 Release Manager _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

4 5