February 2006 - Boost - lists.boost.org

Re: [boost] [test] VC6.5 no longer supported?
by Martin Bonner 06 Feb '06

06 Feb '06

----Original Message---- From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] On Behalf Of Richard V. Day Sent: 04 February 2006 06:25 To: boost(a)lists.boost.org Subject: Re: [boost] [test] VC6.5 no longer supported? > Gennadiy Rozental wrote: > >> Starting release 1.34 Boost.Test *officially* stop supporting VC 6.5, >> GCC2.95 and old Borland. Unofficially Boost.Test is required to make >> sure that none of the test that are included in Boost regression >> testing are not failing due to failure in Boost.Test. If regression >> testing is dropped for any of above compilers it means that >> Boost.Test is not bound by any requirements anymore. >> >> > It sounds like I and many other people are going to have to stop using > boost No you're not. Boost 1.33.1 will not stop working. > as many of us are still tied to this compiler whether we like it > or not. We do not all have a choice as to what compiler we can use. We > must make do with what we have. You're just not going to be able to use the latest version of boost. -- Martin Bonner Martin.Bonner(a)Pitechnology.com Pi Technology, Milton Hall, Ely Road, Milton, Cambridge, CB4 6WZ, ENGLAND Tel: +44 (0)1223 203894

2 1

Re: [boost] Boost regression notification (2006-02-05 [HEAD])
by Martin Bonner 06 Feb '06

06 Feb '06

There seems to be an error in the "broken platform" code. ----Original Message---- From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] On Behalf Of Douglas Gregor Sent: 05 February 2006 17:02 To: boost(a)lists.boost.org Subject: [boost] Boost regression notification (2006-02-05 [HEAD]) > Boost Regression test failures > Report time: 2006-02-05T13:58:58Z > [snip] > > The following platforms have a large number of failures: > tru64cxx71-006 > gcc-4.0.2-linux > intel-9.0-linux > gcc-3.4.5-linux > gcc-3.2.3-linux > gcc-3.3.6-linux > > 3735 failures in 35 libraries (2809 are from non-broken platforms) Implies that there are a total of 926 failures on broken platforms [snip] > serialization (474 of 3095 failures are from non-broken platforms) Implies that there are 2621 failures for serialization alone on broken platforms. 2621 > 926. I assume that one of the strings "non-broken" should actually be "broken" - but I don't known which one! -- Martin Bonner Martin.Bonner(a)Pitechnology.com Pi Technology, Milton Hall, Ely Road, Milton, Cambridge, CB4 6WZ, ENGLAND Tel: +44 (0)1223 203894

1 0

[Range] breaking update pending
by Thorsten Ottosen 06 Feb '06

06 Feb '06

Dear All, I have been trimming boost.range to incorporate the changes we have been discussing some time ago. These changes will break many uses of the library. Inside boost this will affect Boost.foreach Boost.string algo Boost.iostreams (*) (*) I don't this will break The list of major changes is the follwing: 1. ADL hooks renamed boost_range_begin -> range_begin, boost_range_end -> range_end 2. ADL hook boost_range_size removed; boost::size(rng) now requires RandomAccessIterators to guarantee O(1) complexity. 3. range_result_iterator renamed range_iterator and range_iterator renamed mutable_iterator. The correct way to spell const_iterator<T> is now iterator<const T>. 4. intrinsic string support removed. instead a header as_literal.hpp is previded with a small utility for use in string algorithms. I expect that (3) and (4) is where the most work lies. If nobody has anything to add, will add the new version to the cvs within a few days. -Thorsten

5 28

Library Proposal: Reflection for C++
by Stefan Roiser 06 Feb '06

06 Feb '06

Hi, We would like to propose a library and tools which enhance C++ with reflection capabilities. The package, "Reflex", provides a library for runtime introspection and interaction with C++ "constructs" such as objects, types, scopes, members, templated types, ... The library has no external dependencies and was developed with the ISO/IEC standard for C++ as guideline. Production of dictionary information of arbitrary C++ definitions is done via a Python script (genreflex), in a non-intrusive way, using an external tool (gccxml - www.gccxml.org) The generated dictionary source code can be compiled into a shared library, dynamically loaded and accessed via an API providing the introspection information. You can find more information at http://cern.ch/reflex Below you may find an example code snippet which exposes a subset of the functionality. The four different parts show 1 - the definition of the example classes 2 - how to generate the dictionary information 3 - example on introspection (re-generate classes from the dictionary information) 4 - examples on interaction (get/set data members, invoke functions, con/destruct objects) Cheers Stefan // // 1. original class Foo.h // namespace zot { struct foo_base { public: foo_base() : fBar(4711) {} ~foo_base() {} protected: int fBar; }; class foo : public foo_base { public: int bar(); void set_bar(int i); void set_bar(float f); void operator ++ (); }; inline int foo::bar() { return fBar; } inline void foo::set_bar(float f) { fBar = int(f); } inline void foo::set_bar(int i) { fBar = i; } inline void foo::operator ++ () { ++fBar; } } // namespace zot // // 2. Run python script on Foo.h generating dictionary source code // (Foo_rflx.cpp) and produce a shared library libFooRflx.so // genreflex Foo.h --gccxmlpath=/dir/to/gccxml/bin (e.g.) g++ -shared -o libFooRflx.so Foo_rflx.cpp -I${REFLEXROOT}/ include -L${REFLEXROOT}/lib -lReflex // // 3. + 4. example code for introspection and interaction // #include "Reflex/Reflex.h" using namespace std; using namespace ROOT::Reflex; enum Visibility { Public, Protected, Private }; void generate_class_decl( const Type & cl, const string & indent ) { // ... base class declarations if ( cl.BaseSize()) { for ( Base_Iterator b = cl.Base_Begin(); b != cl.Base_End(); ++b) generate_class_decl((*b).ToType(), indent); } cout << indent << "class " << cl.Name(); // ... bases if ( cl.BaseSize()) { cout << " : " ; for ( Base_Iterator b = cl.Base_Begin(); b != cl.Base_End(); + +b ) { if ( (*b).IsVirtual() ) cout << "virtual "; if ( (*b).IsPublic() ) cout << "public "; if ( (*b).IsProtected() ) cout << "protected "; if ( (*b).IsPrivate() ) cout << "private "; cout << (*b).ToType().Name(SCOPED); if ( b != cl.Base_End()-1 ) cout << ", "; } } cout << " {" << endl; Visibility vis = Private; // ... function members for ( Member_Iterator f = cl.FunctionMember_Begin(); f != cl.FunctionMember_End(); ++f ) { if ( ! (*f).IsArtificial()) { if ( (*f).IsPublic() && vis != Public ) { cout << indent << "public:" << endl; vis = Public; } else if ( (*f).IsProtected() && vis != Protected ) { cout << indent << "protected:" << endl; vis = Protected; } else if ( (*f).IsPrivate() && vis != Private ) { cout << indent << "private:" << endl; vis = Private; } Type ft = (*f).TypeOf(); cout << indent + " "; if ( ! (*f).IsConstructor() && !(*f).IsDestructor() ) cout << ft.ReturnType().Name(SCOPED) << " "; if ( (*f).IsOperator() ) cout << "operator "; cout << (*f).Name() << " ("; if ( ft.FunctionParameterSize() ) { for ( size_t p = 0 ; p < ft.FunctionParameterSize(); p++ ) { cout << ft.FunctionParameterAt(p).Name(SCOPED|QUALIFIED); if ( (*f).FunctionParameterNameAt(p).length() ) cout << " " << (*f).FunctionParameterNameAt(p); if ( (*f).FunctionParameterDefaultAt(p).length() ) cout << " = " << (*f).FunctionParameterDefaultAt(p); if ( p != ft.FunctionParameterSize()-1 ) cout << ", "; } } cout << ");" << endl; } } // ... data members for ( Member_Iterator d = cl.DataMember_Begin(); d != cl.DataMember_End(); ++d ) { if ( (*d).IsPublic() && vis != Public ) { cout << indent << "public:" << endl; vis = Public; } else if ( (*d).IsProtected() && vis != Protected ) { cout << indent << "protected:" << endl; vis = Protected; } else if ( (*d).IsPrivate() && vis != Private ) { cout << indent << "private:" << endl; vis = Private; } cout << indent + " " << (*d).TypeOf().Name(SCOPED) << " " << (*d).Name() << ";" << endl; } cout << indent << "};" << endl; } void generate_class(const Type & ty) { string indent = ""; Scope sc = ty.DeclaringScope(); // ... declaring scope if ( ! sc.IsTopScope() ) { if (sc.IsNamespace()) cout << "namespace "; else if (sc.IsClass()) cout << "class "; cout << sc.Name() << " {" << endl; indent += " "; } generate_class_decl(ty, indent); if ( ! sc.IsTopScope() ) { cout << "}" << endl; if (sc.IsClass()) cout << ";"; } } int main() { // load the dictionary information void * v = dlopen("libFooRflx.so", RTLD_LAZY); // get meta information of type Foo Type fooType = Type::ByName("zot::foo"); // check if the type is valid if (fooType) { // // 3. Introspection // // generate declarations for foo generate_class(fooType); // // 4. Interaction // // update the information for inherited members of class foo // this will be automatic in the future fooType.UpdateMembers(); // construct an object of type Foo Object fooObj = fooType.Construct(); // get the value of the data member (i.e. 4711) int val = Object_Cast<int>(fooObj.Get("fBar")); // set the data member to 4712 fooObj.Set("fBar",++val); // get the data member again (i.e. 4712) val = Object_Cast<int>(fooObj.Get("fBar")); // call function setBar with value 4713 fooObj.Invoke("set_bar",Type::ByName("void (int)"), ++val); // call operator ++ to increase fBar by one fooObj.Invoke("operator++"); // call bar getter and cast the output to int (i.e. 4714) val = Object_Cast<int>(fooObj.Invoke("bar")); // delete the Foo object fooObj.Destruct(); } return 0; } /* // // the output of the introspection part is // namespace zot { class foo_base { public: foo_base (); ~foo_base (); protected: int fBar; }; class foo : public zot::foo_base { public: int bar (); void set_bar (int i); void set_bar (float f); void operator operator++ (); }; } // // // */ -- Stefan Roiser CERN, PH Department CH - 1211 Geneva 23 Mob:+41 76 487 5334 Tel:+41 22 767 4838 Fax:+41 22 767 9425

7 46

[Boost-bugs] [ boost-Bugs-1424965 ] Memory leak in tss
by SourceForge.net 06 Feb '06

06 Feb '06

Bugs item #1424965, was opened at 2006-02-06 00:53 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1424965&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: threads Group: None Status: Open Resolution: None Priority: 5 Submitted By: Braden McDaniel (braden) Assigned to: Mike Glassford (glassfordm) Summary: Memory leak in tss Initial Comment: The patch attached to this message seems never to have been applied: <http://lists.boost.org/Archives/boost/2005/05/86395.php> I believe I'm observing the same leak when using Spirit multithreaded. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1424965&group_… ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

Re: [boost] Why use Boost?
by Matt Doyle 06 Feb '06

06 Feb '06

> -----Original Message----- > From: boost-bounces(a)lists.boost.org > [mailto:boost-bounces@lists.boost.org]On Behalf Of David Maisonave > "Paul Giaccone" <paulg(a)cinesite.co.uk> wrote in message > news:<43E1D46C.7000500(a)cinesite.co.uk>... > > There is a thread on the Boost-users mailing list at the <snip> > IMHO, the help documents waist too much space in giving details that > really don't help the average user to figure out how to use an > interface. > Take intrusive_pr document for an example: > http://www.boost.org/libs/smart_ptr/intrusive_ptr.html > > There's no example usage at all. > It waist a lot of space giving details Synopsis and Members, but very > little space for an introduction, or a good explanation on how to use > it. I agree with you on this but I'd like to take it a step further. A potential new user needs a way to find out what exactly is in boost. Right now if I want to solve a particular problem and I don't know which library to use, I basically have to drill down through the list and read the overview for each one. Even then there's no guarantee that you'll find "the right thing". Would I have found explicit cast this way? Nope. What if I want to pass messages between processes, which is the best library... I don't really know how to make it easier for a person to find just the right library but IMHO a new user considering Boost doesn't need to be "sold". They have a problem they need to solve. Once you have solved _1_ problem then that person is sold, no more marketing required. My $0.02 worth, Matt Scanned by McAfee GroupShield {X3BTB534}

7 10

[filesystem, config (maybe) ] bug: static link with msvc8 fails
by Tobias Schwinger 06 Feb '06

06 Feb '06

When linking statically against Boost.Filesystem the (msvc) link step fails if <boost/filesystem.hpp> was included by one of the source files. Everything's works if - compiling with GCC, or - none of the source files includes boost/filesystem.hpp. The link settings are <threading>multi <link>static <runtime-link>static Here are the symptoms: boost_filesystem-vc80-mt-sd-1_34.lib is built, but linking fails because ... cannot open file 'libboost_filesystem-vc80-mt-sgd-1_34.lib' . Adding <runtime-debugging>off to the link settings changes error message to ... cannot open file 'libboost_filesystem-vc80-mt-s-1_34.lib' I'm using Boost.Build V2. There is an example project that shows the problem attached to this post (note the path to Boost in 'project-root.jam' needs manual adjustment). I hope the report was of any help. Regards, Tobias

2 2

When will next asio release occur?
by Andrew Schweitzer 05 Feb '06

05 Feb '06

Sorry to ask the obvious questions again. I don't seem to see the answer from a search of the list. Is there an expected date for acceptance decision? Or a "rough guess suject to change at any time"? If it gets accepted, is there an expected date on when it will be part of boost? Is there an expected date on next release at asio website? (Presumably before next boost release)?

2 2

asio and vc8.0 Link Error
by Ian Baxter 05 Feb '06

05 Feb '06

Asio when compiled in a mixed assembly with VS 8 produces a link error (LNK2022) because of an undefined struct in error.hpp. changing line 288 error.hpp to this: struct unspecified_bool_type_t{ }; fixes the problem. Cheers

2 1

[test] VC6.5 no longer supported?
by Joaquín Mª López Muñoz 05 Feb '06

05 Feb '06

Hello, As of Jan 28, the CVS version of Boost.Test has some commits labeled "VC6.0 workaround removed", which, expectedly enough, cause some of Boost.Test facilities to fail for that compiler-- for instance, including <boost/test/included/test_exec_monitor.hpp> no longer works in VC 6.5. Let me say in advance that I fully respect Gennadiy's decisions on which compilers he chooses Boost.Test should have support for, but I'd like to make sure before deciding on switching my current test framework, so my question is: is this a conscious decision and VC6.5 won't be supported by Boost.Test from now on, or, on the contrary, is this a transient state and VC 6.0 will be finally supported by Boost.Test 1.34? Thank you, Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

10 18