October 2004 - Boost-users - lists.boost.org

How to inherit from boost::multi_array
by Thomas Mensch 02 Oct '04

02 Oct '04

Dear List, I am using boost 1.31.0 on Linux (with gcc 3.3.2) I would like to create a 2D array class, which inherits from boost::multi_array<double, 2> class. However I have problems with the copy constructor of my class Array. Below is the code, which I am trying to run. #include <boost/multi_array.hpp> class Array : public boost::multi_array<double,2> { public: Array (void) : boost::multi_array<double, 2> () {} Array (const int nrow, const int ncol) : boost::multi_array<double, 2> (boost::extents[nrow][ncol]) {} Array (const Array& other) : boost::multi_array<double, 2> (other) {} ~Array (void) {} Array& operator= (const Array& rhs) { if (&rhs != this) { boost::multi_array<double, 2>::operator= (rhs); } return *this; } }; /* class Array */ I guess that I forget to provide some information to my derived class, but I cannot find which one. Is there a way to simply inherits from boost::multi_array? Many thanks in advance, Thomas

2 1

[serialization1.32/vc7.1]: What's wrong with this class??
by Francis ANDRE 02 Oct '04

02 Oct '04

Hi I got a access violation on 0x00000000 with the class DDD but I cannot figure out what's wrong When the symbol NO_EXCEPTION is defined, the member acccode is set to an instance of ACCCODE and the serialization is working fine. But when this symbol is undefined, one gets the exception. I am suspecting the input serialization to bypass the loading of the member FIELD* field (which is following the "acccode" member) which leads to an exception when the next member DISP* disp is loaded but I have no way to check it out any idea?? Francis Source code below and also joined in annex ---------------------------------------------------------------------- #include <iostream> #include <fstream> #include <boost/archive/text_iarchive.hpp> #include <boost/archive/text_oarchive.hpp> using namespace std; class FIELD : public string { private: friend class boost::serialization::access; friend std::ostream & operator<<(std::ostream &os, const FIELD&); template<class Archive> void serialize(Archive &ar, const unsigned int version) { ar & boost::serialization::base_object<string>(*this); ar & member; } private: string member; FIELD(){} public: FIELD(const string& name): string(name){} }; class DDD { private: friend class boost::serialization::access; friend std::ostream & operator<<(std::ostream &os, const DDD& dd); template<class Archive> void serialize(Archive &ar, const unsigned int version) { ar & acccode; ar & field; ar & disp; } public: DDD(): acccode(0), disp(0), field(0) {} class ACCCODE { private: friend class boost::serialization::access; friend std::ostream & operator<<( std::ostream &os, const ACCCODE& ); template<class Archive> void serialize(Archive &ar, const unsigned int version) { ar & acccode; } public: string acccode; ACCCODE(){} ACCCODE(const string& s) : acccode(s) {} }; class DISP { private: friend class boost::serialization::access; friend std::ostream & operator<<( std::ostream &os, const DISP& ); template<class Archive> void serialize(Archive &ar, const unsigned int version) { ar & disp; } public: string disp; DISP(){} DISP(const string& s) : disp(s) {} }; public: ACCCODE* acccode; FIELD* field; DISP* disp; }; int main(int argc, char* argv[]) { DDD ddd; #ifdef NO_EXCEPTION ddd.acccode = new DDD::ACCCODE("a"); #endif ddd.field = new FIELD("BAR"); ddd.disp = new DDD::DISP(); const char* file = "TEST.txt"; { std::ofstream os(file); boost::archive::text_oarchive oa(os); oa << ddd; } { std::ifstream is(file); boost::archive::text_iarchive ia(is); ia >> ddd; } } ---------------------------------------------------------------------------- -- A good friend will come bail you out of jail.......... but, a true friend....will be sitting next to you saying: "...that was fun." begin 666 test_serialization.cpp M(VEN8VQU9&4@/&EO<W1R96%M/@T*(VEN8VQU9&4@/&9S=')E86T^#0HC:6YC M;'5D92 \8F]O<W0O87)C:&EV92]T97AT7VEA<F-H:79E+FAP<#X-"B-I;F-L M=61E(#QB;V]S="]A<F-H:79E+W1E>'1?;V%R8VAI=F4N:'!P/@T*=7-I;F<@ M;F%M97-P86-E('-T9#L-"@T*8VQA<W,@1DE%3$0@.B!P=6)L:6,@<W1R:6YG M('L-"@EP<FEV871E.@T*"0EF<FEE;F0@8VQA<W,@8F]O<W0Z.G-E<FEA;&EZ M871I;VXZ.F%C8V5S<SL-"@D)9G)I96YD('-T9#HZ;W-T<F5A;2 F(&]P97)A M=&]R/#PH<W1D.CIO<W1R96%M("9O<RP@8V]N<W0@1DE%3$0F*3L-"@D)=&5M M<&QA=&4\8VQA<W,@07)C:&EV93X-"@D)=F]I9"!S97)I86QI>F4H07)C:&EV M92 F87(L(&-O;G-T('5N<VEG;F5D(&EN="!V97)S:6]N*2![#0H)"0EA<B F M(&)O;W-T.CIS97)I86QI>F%T:6]N.CIB87-E7V]B:F5C=#QS=')I;F<^*"IT M:&ES*3L-"@D)"6%R("8(a);65M8F5R.PT*"0E]#0H)<')I=F%T93H-"@D)<W1R M:6YG(&UE;6)E<CL-"@D)1DE%3$0H*7M]#0H)<'5B;&EC.@T*"0E&245,1"AC M;VYS="!S=')I;F<F(&YA;64I.B!S=')I;F<H;F%M92E[?0T*?3L-"@T*#0IC M;&%S<R!$1$0@('L-"@EP<FEV871E.@T*"0EF<FEE;F0@8VQA<W,@8F]O<W0Z M.G-E<FEA;&EZ871I;VXZ.F%C8V5S<SL-"@D)9G)I96YD('-T9#HZ;W-T<F5A M;2 F(&]P97)A=&]R/#PH<W1D.CIO<W1R96%M("9O<RP@8V]N<W0@1$1$)B!D M9"D[#0H)"71E;7!L871E/&-L87-S($%R8VAI=F4^#0H)"79O:60@<V5R:6%L M:7IE*$%R8VAI=F4@)F%R+"!C;VYS="!U;G-I9VYE9"!I;G0@=F5R<VEO;BD@ M>PT*"0D)87((a))B!A8V-C;V1E.PT*"0D)87(@)B!F:65L9#L-"@D)"6%R("8@ M9&ES<#L-"@D)?0T*"7!U8FQI8SH-"@D)1$1$*"DZ#0H)"0EA8V-C;V1E*# I M+ T*"0D)9&ES<"@P*2P-"@D)"69I96QD*# I#0H)"0E[?0T*"0EC;&%S<R!! M0T-#3T1%("![#0H)"0EP<FEV871E.@T*"0D)"69R:65N9"!C;&%S<R!B;V]S M=#HZ<V5R:6%L:7IA=&EO;CHZ86-C97-S.PT*"0D)"69R:65N9"!S=&0Z.F]S M=')E86T@)B!O<&5R871O<CP\*'-T9#HZ;W-T<F5A;2 F;W,L(&-O;G-T($%# M0T-/1$4F*3L-"@D)"0ET96UP;&%T93QC;&%S<R!!<F-H:79E/@T*"0D)"79O M:60@<V5R:6%L:7IE*$%R8VAI=F4@)F%R+"!C;VYS="!U;G-I9VYE9"!I;G0@ M=F5R<VEO;BD@>PT*"0D)"0EA<B F(&%C8V-O9&4[#0H)"0E]#0H)"0EP=6)L M:6,Z#0H)"0ES=')I;F<@86-C8V]D93L-"@D-"@D)"4%#0T-/1$4H*7M]#0H) M"0E!0T-#3T1%*&-O;G-T('-T<FEN9R8@<RD@.B!A8V-C;V1E*',I('M]#0H) M"7T[#0H-"@D)8VQA<W,@1$E34" @>PT*"0D)<')I=F%T93H-"@D)"0EF<FEE M;F0@8VQA<W,@8F]O<W0Z.G-E<FEA;&EZ871I;VXZ.F%C8V5S<SL-"@D)"0EF M<FEE;F0@<W1D.CIO<W1R96%M("8@;W!E<F%T;W(\/"AS=&0Z.F]S=')E86T@ M)F]S+"!C;VYS="!$25-0)BD[#0H)"0D)=&5M<&QA=&4\8VQA<W,@07)C:&EV M93X-"@D)"0EV;VED('-E<FEA;&EZ92A!<F-H:79E("9A<BP@8V]N<W0@=6YS M:6=N960@:6YT('9E<G-I;VXI('L-"@D)"0D)87(@)B!D:7-P.PT*"0D)?0T* M"0D)<'5B;&EC.@T*"0D)<W1R:6YG(&1I<W [#0H)#0H)"0E$25-0*"E[?0T* M"0D)1$E34"AC;VYS="!S=')I;F<F(',I(#H@9&ES<"AS*2![?0T*"0E].PT* M"7!U8FQI8SH-"@D)04-#0T]$12H)"0EA8V-C;V1E.PT*"0E&245,1"H)"0D) M9FEE;&0[#0H)"41)4U J"0D)"61I<W [#0I].PT*#0II;G0@;6%I;BAI;G0@ M87)G8RP@8VAA<BH@87)G=EM=*2![#0H)1$1$(&1D9#L-"B-I9F1E9B!.3U]% M6$-%4%1)3TX-"@ED9&0N86-C8V]D92 ](&YE=R!$1$0Z.D%#0T-/1$4H(F$B M*3L-"B-E;F1I9@T*"61D9"YF:65L9 D](&YE=R!&245,1"@B0D%2(BD[#0H) M9&1D+F1I<W )/2!N97<@1$1$.CI$25-0*"D[#0H-"@EC;VYS="!C:&%R*B!F M:6QE(#T@(E1%4U0N='AT(CL-"@E[#0H)"7-T9#HZ;V9S=')E86T@;W,H9FEL M92D[#0H)"6)O;W-T.CIA<F-H:79E.CIT97AT7V]A<F-H:79E(&]A*&]S*3L- M"@D);V$@/#P@9&1D.PT*"0EO<RYC;&]S92(a)I.PT*"7T-"@T*"7L-"@D)<W1D M.CII9G-T<F5A;2!I<RAF:6QE*3L-"@D)8F]O<W0Z.F%R8VAI=F4Z.G1E>'1? G:6%R8VAI=F4@:6$H:7,I.PT*"0EI82 ^/B!D9&0[#0H)?0T*?0T* ` end

1 0

Boost 1.30 with g++ 3.4
by Ben Hutchings 02 Oct '04

02 Oct '04

I have an existing body of code using some parts of Boost 1.30 (Bind, Function, Regex, Thread, and some utilities) and compiled using VC++ 7.1 on Windows. I now need to build with g++ 3.3 or 3.4 on Linux as well, and for various reasons I would prefer to use 3.4. Boost 1.30 predates g++ 3.4 by some way and I know that it won't all work without changes. However, neither will 1.31, and 1.32 has still not been released. I would rather not upgrade to either of these in case they break the existing Windows build. Are there any known bugs or other problems in the above-mentioned libraries from Boost 1.30 when used with g++ 3.4, and if so, any known fixes for them? (Assume I'm using Boost 1.30.2 - I might still have 1.30.0 but upgrading to 1.30.2 should be low-risk.) Ben.

2 1

Are BOOST_BUILD_PATH && BOOST_ROOT necessary?
by Steven T. Hatton 01 Oct '04

01 Oct '04

>From reading the documentation on boost.org, I have gotten the impression I don't need to set $BOOST_BUILD_PATH and $BOOST_ROOT. I'm more than a little confused about how I should use the boost libraries. Part of this comes from the fact that it is not clear to me exactly where the demarkation is between using the build system to build boost, and using it to build my own programs. Some of my confusion comes from the appearant change in configuration requirements described in the documentation. It is suggested I don't need the environment variable used with earlier releases. One of these variables is $BOOST_ROOT, which the documentation used as an example of how to build boost. That example was exactly what I successfully (I believe) build the libraries with. I'm using SuSE Linux 9.1 on a P4 box. Some basic questions are these: When I downloaded and built boost, I first fetched the source for bjam. This is the name of the file I downloaded: boost-jam-3.1.10.tgz It compiled quite nicely, and I copied the resulting bjam jam mkjambase and yyacc to a location in my path. Are there anything other things such as configuration files I need to reside with the binary executables? Are there necessary configuration file that I need to have visible to these programs, even if they are not colocated? I then build boost with the command: bjam --prefix=$BOOST_ROOT "-sTOOLS=gcc" install after setting my BOOST_ROOT the way I wanted it. That resulted in two directories being placed in $BOOST_ROOT/ one is called $BOOST_ROOT/include/ the other is called $BOOST_ROOT/lib/. Under $BOOST_ROOT/include/ I have <path>/boost-1_31/boost/ which contains dozens of header files. I added $BOOST_ROOT/include/boost-1_31 to my $INCLUDE_PATH, and $BOOST_ROOT/lib to my $LIBRARY_PATH and $LD_LIBRARY_PATH variables. Is this the correct way to configure my system to use boost? Is there anything else I need to do in order to compile my programs against the boost headers and libraries? Will the boost libraries work as well as other, comperable libraries using autotools rather than bjam? Are there any special accommodations I need to make in order to use boost with the gnu build tools? Do I need to do anything special to use boost with bjam that does not involve placing files in my current project directories? For example, do I need to provide a global configuration file of some kind? Is it a preferred option, even if not strictly required? There is much remaining in the source directory where I compiled boost. Is that something I need to also put in an accessible place on my system? If so, what so I need to put where, and how to I modify my environment variable to facilitate its use? -- Regards, Steven

4 15

BOOST_CHECK_CLOSE apparent misbehavior
by Ross Boylan 01 Oct '04

01 Oct '04

I get the following error Specification_test.cc(22): error in "specsimple": difference between spec(i, j){0.206788} and results[k]{0.206788} exceeds 1e-05% The numbers agree to all printed digits. I get a maximum relative error (assuming the printed values are rounded from extremes)*(see footnote) of .000001/.206787 = 4.8e-6 < 1e-5. Even doubling this is under the tolerance. As I read the documentation, this should pass. 1e-6 tolerance produces a lot more discrepancies; 1e-4 says they are all OK. Have I misunderstood something, or is something funny going on? In particular, the "%" after "1e-5" in the error message suggests the tolerances are supposed to be in percentage terms, i.e, 1e-5 implies a real tolerance of 1e-7. That would explain things, but I see nothing in the documentation to suggest the tolerance value is a percent. (Well, the docs do say the tolerance can be an integer.) The relevant line is BOOST_CHECK_CLOSE(spec(i, j), results[k], tol); All relevant quantities are doubles. It may be relevant that the program under test includes <cmath>. Debian package libboost-dev 1.31.0-7 on an Athlon system. # g++ --version g++.real (GCC) 3.3.4 (Debian 1:3.3.4-6sarge1) Linux kernel 2.4.26 * In fact, the results value is coded as 0.2067880 in the program, so my calculation likely gives double the possible discrepancy.

2 1

RE: [Boost-users] Re: Boost:regex and C++ Parsing - Spirit!
by Foster, Gareth 01 Oct '04

01 Oct '04

Sheesh, I've learned some new words there. I mean, dictionary.com is as close to naked ... Only joking. I thought it was the perfect way to describe how slick the library was :) that's my effusing done for the day anyway. -----Original Message----- From: boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Justin Findlay Sent: 30 September 2004 17:22 To: boost-users(a)lists.boost.org Subject: Re: [Boost-users] Re: Boost:regex and C++ Parsing - Spirit! On Thu, Sep 30, 2004 at 10:23:22AM +0100, Foster, Gareth wrote: > > Wow, I just read through the 1st few pages of the spirit docs, and I > can safely say, that is as close to naked women as C++ code will ever > be, its such a sexy idea. One library, and you can parse any sort of > config file, code or anything! Amazing. Gentlemen, consider decency. /me covers his eyes in embarassment. > Interetsing stuff, thank you all! Spirit is indeed an elegant library, by utilizing many powerful features of C++ in context it exemplifies what sublime things can be done with the language. Good luck with your project Gaz. (-: Please excuse the offtopic post. No effusions of remonstrance were personally directed. Justin _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

1 0

Forgot to add
by Foster, Gareth 01 Oct '04

01 Oct '04

I also was going to say Joel, you ought to moan about the description of spirit in the docs, I can see it is there in the list of libraries now, and whilst it probably does describe what the library does, it doesn't do it in a way that is very identifiable for those who don't know about the subject, I just plain missed it, despite the fact that I was looking to parse C++. spirit <file:///C:/boost/boost_1_31_0/libs/spirit/index.html> - LL parser framework represents parsers directly as EBNF grammars in inlined C++, from Joel de Guzman and team. Why not something like ... spirit <file:///C:/boost/boost_1_31_0/libs/spirit/index.html> - A customisable framework for parsing any syntax. You will know what I mean and how to describe it properly etc I'm sure. Just a thought :) Gaz

2 1