- Boost - lists.boost.org

Plans for 1.33.1?
by John Maddock 20 Aug '05

20 Aug '05

I notice that there are already a few patches that have gone into the RC_1_33_0 branch, presumably in expectation of a 1.33.1 release? So some questions: 1) Is the release branch now officially open again for patches: I assume that it is now that the release is out. 2) Is there any interest in either a hotfix patch-release or possibly a full 1.33.1 in 4 to 6 weeks time? If yes, then I believe we really need to start a readme file with a list of patches made - this would become the readme for the patch when it's released. Thoughts? John.

12 21

Fall Review Schedule - version 2.0
by Tom Brinkman 20 Aug '05

20 Aug '05

Boost Fall Review Schedule - version 2.0 Contact Tom Brinkman at reportbase(a)gmail.com to request a review, to make updates to this document or to volunteer to be a review manager. The next library up for review is the xpressive library by Eric Niebler on September 8, 2005. It is available at http://boost-sandbox.sf.net/vault/index.php?directory=eric_niebler. This library still needs a review manager. Please contact me to volunteer. Following the review of the xpressive library is the TR1 library by John Maddock at john(a)johnmaddock.co.uk. The review is set for September 20, 2005. This library can be download at http://boost-sandbox.sourceforge.net/vault/index.php?&direction=0&order=&di…. This library needs a review manager volunteer also. Lets all make an effort to get more involved in the review processes this fall. I know the library authors would love to get more feedback. Check out the Boost::wiki page for New Libraries Under Construction at http://www.crystalclearsoftware.com/cgi-bin/boost_wiki/wiki.pl?LibrariesUnd… If your one of the libray's authors or active users, please feel free to make any changes to the libraries summary description. Click the question mark to add more detailed information about the library. Review Queue as of August 16, 2005. Confirmed: 1. xpressive - Eric Niebler (September 8, 2005) 2. TR1 - John Maddock (September 20, 2005) 3. logging - John Torjo (October 5, 2005) To be Confirmed: 4. singleton - Jason Hise (postponed) 5. function types - Tobias Schwinger (mini post-review needed) 6. output formatters - Reece Dunn (new review needed) 7. policy pointer - David B. Held 8. fixed strings - Reece Dunn 9. intrusive - Olaf Krzikalla 10. interfaces - Jonathan Turkanis 11. binary_int - Scott Schurr (ready to be reviewed) 1. xpressive Author: Eric Niebler eric(a)boost-consulting.com Review Manager: needed Download: http://boost-sandbox.sf.net/vault/index.php?directory=eric_niebler Docs: http://boost-sandbox.sf.net/libs/xpressive Review Date: September 8, 2005 xpressive is a TR1 regex work-alike that also accepts regexes as expression templates and lets regexes nest and call each other recursively. Significant changes since 0.9.3 - c_regex_traits to wrap the global C locale - null_regex_traits for searching non-char data - doc and test improvements - bugs in static regexes and Unicode support squashed You can consider this the xpressive 1.0 release candidate. All that remains is to add more tests and documentation, and perhaps a tweak to the traits interface. 2. TR1 Author - John Maddock john(a)johnmaddock.co.uk Review Manager - needed Download - http://boost-sandbox.sourceforge.net/vault/index.php?&direction=0&order=&di… Docs - in download file Review Date: September 20, 2005 (follows xpressive) The TR1 library provides an implementation of the C++ Technical Report on Standard Library Extensions. This library does not itself implement the TR1 components, rather it's a thin wrapper that will include your standard library's TR1 implementation (if it has one), otherwise it will include the Boost Library equivalents, and import them into namespace std::tr1. Functionality supported includes: Reference Wrappers, Smart Pointers, Class template result_of.,Function template mem_fn., Function Object Binders, Polymorphic function wrappers, Type Traits, Random Number Generators and Distributions, Tuples, Tuple Interface to std::pair, Fixed Size Array, Hash Function Objects, Regular Expressions, Complex Number Algorithm Overloads, Complex Number Additional Algorithms, Functionality in TR1 but not yet available in this implementation: Mathematical Special Functions, Unordered Associative Set (Hash Table), Unordered Associative Map (Hash Table), C99 C language additions. This library also makes changes to Boost.Config, and adds some new functionality to Boost.Math, reviewers should start with the readme.html in the root directory of the zip file. 3. logging Author - John Torjo john(a)torjo.com Review Manager - Hartmut.Kaiser Hartmut.Kaiser(a)gmail.com Download: http://torjo.com/code/logging.zip Docs: http://torjo.com/ Review Date: October 5, 2005 (follows TR1) The Boost Log Library is a small library, who: * makes it very easy to declare/define new logs * allows you very simple access to logs * allows for log hierarchies, and for modifying log hierarchies * allows for easy and efficient enabling/disabling of logs/log hierarchies * allows for easy manipulation of log behaviors (the log's destination(s) and/or adjusting the original message) * is thread-safe Using the library in code is easy and straightforward: int i = 1, j = 2, k = 3; BOOST_LOG(app) << "testing " << i << '-' << j << '-' << k << std::endl; BOOST_LOG(dbg) << "this is a debug message, i=" << i << std::endl; BOOST_LOG(info) << "I just wanted to tell you something...."; Recent Additions: - can be compiled as a static/dynamic runtime (works as a DLL as well) - removed dependency on boost_thread Note: I did not test this on Unix, but it should work. If anybody can take a look at detail/ts_posix.hpp, I'd appreciate it. - solved other small issues, based on feedback - slightly improved documentation 4) Singleton Author - Jason Hise chaos(a)ezequal.com Review Manager - Andreas Huber ahd6974-groups(a)yahoo.com Download: http://tinyurl.com/6qvrd (old version from previous review) Docs: http://tinyurl.com/6qvrd Review Date: Winter-2006 The singleton library provides multiple powerful methods of controlling the lifetimes of global resources. Client code can choose among the many provided methods of creation, or can easily write new creators for specialized initialization needs. Client code can additionally control precisely when a singleton instance is automatically created and destroyed, can create and destroy singleton instances explicitly any number of times, and can set up dependencies between singletons in an easy and natural way. Jason has stated that he will not be ready for the next review for a few months. 5) Function Types Author - Tobias Schwinger tschwinger(a)neoscientists.org Review Manager - John Maddock john(a)johnmaddock.co.uk Download: http://tinyurl.com/4oe7q (old version - from previous review) Docs: http://tinyurl.com/4oe7q Review Date: needed This library provides a metaprogramming facility to classify, decompose and synthesize function-, function pointer-, function reference- and member function pointer types. For the purpose of this documentation, these types are collectively referred to as function types (this differs from the standard definition and redefines the term from a programmer's perspective to refer to the most common types that involve functions). The classes introduced by this library shall conform to the concepts of the Boost Metaprogramming library (MPL). The Function Types library enables the user to: * test an arbitrary type for being a function type of specified kind, * inspect properties of function types, * view and modify sub types of an encapsulated function type with MPL Sequence operations, and * synthesize function types. This library supports variadic functions and can be configured to support non-default calling conventions. This library was reviewed June 2005 and was accepted pending a mini post-review. 6. Output formatters Author - Reece Dunn msclrhd(a)hotmail.com Review Manager - needed Download: needed Docs: needed Review Date: needed This library was reviewed september 11, 2004. It requires a second full review. 7. Policy Pointer Author - David B. Held dheld(a)codelogicconsulting.com Review Manager - Gennadiy gennadiy.rozental(a)thomson.com Download: Boost Sandbox under policy_ptr Docs: Boost Sandbox under policy_ptr Review Date: needed Smart pointers are used to automate memory management by handling the deletion of dynamically allcoated objects (and other resources). They assist in ensuring program correctness, exception safety, and memory integrity. Policy Pointer is a policy-based smart pointer framework designed to accomodate the large number of smart pointer designs. Through the use of policy classes, virtually any smart pointer type can be constructed within this framework. This library is a Boostification of the original Loki::SmartPtr type with significant modifications. 8. Fixed Strings Author - Reece Dunn msclrhd(a)hotmail.com Review Manager - Beman Dawes bdawes(a)acm.org Download: boosts-sandbox/boost/fixed_string Docs: boosts-sandbox/boost/fixed_string Review Date: needed The fixed string library provides buffer overrun protection for static sized strings (char s[ n ]). It provides a C-style string interface for compatibility with C code (for example, porting a C program to C++). There is also a std::string-style interface using a class based on flex_string by Andre Alexandrescu with a few limitations due to the non-resizable nature of the class. 9. Intrusive Author - Olaf Krzikalla krzikalla(a)gmx.de Review Manager - needed Download: http://people.freenet.de/turtle++/intrusive.zip Docs: http://people.freenet.de/turtle++/intrusive.zip Review Date: needed While intrusive containers were and are widely used in C, they became more and more forgotten in the C++-world due to the presence of the standard containers, which don't support intrusive techniques. Boost.Intrusive not only reintroduces this technique to C++, but also encapsulates the implementation in STL-like interfaces. Hence anyone familiar with standard containers can use intrusive containers with ease. 10. Interfaces Author - Jonathan Turkanis technews(a)kangaroologic.com Review Manager - needed Download: http://www.kangaroologic.com/interfaces Docs: http://www.kangaroologic.com/interfaces Review Date: needed "Boost.Interfaces provides a macro-based Interface Definition Language (IDL) which can be used to define C++ class types called interfaces. An interface is a lightweight value type associated with a set of named function signatures. An interface instance can be bound at runtime to any object which implements the interface, i.e., to any object of a type with accessible non-static member functions having the same name and signature as the set of functions associated with the interface. The functions of the bound object can then be invoked through the interface instance using the 'dot' operator. Binding is completely non-intrusive: the object's type need not declare any virtual functions or derive from any particluar base class. "Current applications of Boost.Interfaces include: * Non-intrusive dynamic polymorphism — interfaces can often be used in place of abstract base classes, and are sometimes much faster (see Performance). * Dynamic inheritance — allows function calls to be forwarded automatically to an object specified at runtime (see Delegation). * Smart Interface Pointers — smart pointers which can manage the lifetime of any object whose type implements a given interface. * Smart References — like smart interface pointers, but the managed object is accessed using the "dot" operator." 11. binary_int Author: Scott Schurr scott_schurr(a)credence.com Review Manager: pavel_vozenilek(a)hotmail.com Download: needed Docs: needed Review Date: October, 2005 (ready to be reviewed) The binary_int<> template allows the compile-time expression of integer binary literals. There is no run-time code overhead for using this template; all overhead is at compile time. I expect these binary literals to work any place that an integer literal would work at compile (not preprocessing) time. The template is designed to allow binary values up to 64-bits to be expressed, although it has only been tested up to 32-bits to date.

3 2

Re: [boost] (Vector) norm functions?
by Michael Stevens 19 Aug '05

19 Aug '05

On Friday 19 August 2005 17:48, Neal Becker <ndbecker2(a)gmail.com> wrote: > David Abrahams wrote: > > > Daryle Walker <darylew(a)hotmail.com> writes: > > > >> Should we add functions to evaluate the various norms of a (numeric) > >> sequence? > > > > I'm fairly certain that functionality is in uBlas already. > > > > Yes, but just for ublas vector, not for generic sequences, right? True. But you can adapt many STL containers (such as std::vector) into a uBLAS Storage model which can be accessed as a vector. The overhead would not be great. Such adaptors would make an interesting addition to uBLAS -- ___________________________________ Michael Stevens Systems Engineering 34128 Kassel, Germany Navigation Systems, Estimation and Bayesian Filtering http://bayesclasses.sf.net ___________________________________

1 0

Missing archives? Early releases.
by Daryle Walker 19 Aug '05

19 Aug '05

Looking at <http://lists.boost.org/Archives/boost/>, some of the early months are missing: March 2000, February 2000, March 1999, January 1999, and anything on or before October 1998 (if any). I was looking for information on early releases. I saw an article from Beman on 1999-12-30 about v1.10.3, claiming that it was the first numbered release. And that he keeps backups of the old site. I wonder if he could find versions of Boost before 1.11.2 (that's the earliest I found in CVS). -- Daryle Walker Mac, Internet, and Video Game Junkie darylew AT hotmail DOT com

2 1

Boost regression notification (2005-08-19)
by Douglas Gregor 19 Aug '05

19 Aug '05

Boost regression test failures ------------------------------ Report time: 2005-08-19T15:45:26Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 64 failures in 6 libraries: graph (11) iostreams (3) parameter (9) python (20) serialization (20) wave (1) |graph| graphviz_test: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux mingw-3_4_2 vc-7_1 vc-7_1 vc-7_1 |iostreams| bzip2_test: mingw-3_4_2 gzip_test: mingw-3_4_2 zlib_test: mingw-3_4_2 |parameter| basics: borland-5_6_4 macros: borland-5_6_4 sfinae: borland-5_6_4 unnamed: borland-5_6_4 cw-9_4 intel-win32-8_1 msvc vc-6_5 vc-6_5-stlport |python| exec: cw-8_3 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 msvc vc-6_5 vc-6_5-stlport vc-7_0 vc-7_1 vc-7_1 vc-7_1 |serialization| test_class_info_load_binary_archive: cw-9_5-darwin gcc-3_4_3-sunos test_class_info_load_binary_archive_dll: cw-9_5-darwin gcc-3_4_3-sunos test_class_info_load_text_archive: gcc-3_4_3-sunos test_class_info_load_text_archive_dll: gcc-3_4_3-sunos test_class_info_load_text_warchive: gcc-3_4_3-sunos test_class_info_load_text_warchive_dll: gcc-3_4_3-sunos test_class_info_load_xml_archive: cw-9_5-darwin gcc-3_4_3-sunos test_class_info_load_xml_archive_dll: cw-9_5-darwin gcc-3_4_3-sunos test_class_info_load_xml_warchive: gcc-3_4_3-sunos test_class_info_load_xml_warchive_dll: gcc-3_4_3-sunos test_const_save_fail1: msvc test_const_save_fail2: msvc test_const_save_fail3: msvc test_map_binary_archive_dll: msvc test_map_text_archive_dll: msvc test_map_text_warchive_dll: msvc |wave| testwave: gcc-3.3.6-linux

1 0

OpenOffice is using Boost
by Fredrik Blomqvist 19 Aug '05

19 Aug '05

Hi, I recently browsed the OpenOffice source and noticed that it uses Boost. This seems like an excellent candidate to promote. Btw, when I look at the other entries in the users lists, I get the feeling that a lot of companies where "boosters" work must be missing? Obvious examples would be MetaCommunications (Aleksey) and I guess/assume also ReadSoft (Björn Karlsson) and Housemarque (Vesa). I guess it's up to the respective indivuduals to decide on this though, just wanted to remind :) Regards // Fredrik Blomqvist

2 1

Rational Discovery is using Boost
by Greg Landrum 19 Aug '05

19 Aug '05

I somehow have kept forgetting to submit this: Company: Rational Discovery LLC Rational Discovery provides computational modeling, combinatorial library design and custom software development services to the pharmaceutical, biotech and chemical industries. We do a substantial amount of internal research to develop new approaches for applying machine-learning techniques to solve chemical problems. Because we're a small organization and chemistry is a large and complex field, it is essential that we be able to quickly and easily prototype and test new algorithms. We have found the Boost libraries, a reliable source of high-quality code, to be indispensable. Libraries used: python, graph, smart_ptr, any, lexical_cast, random, string_algo, tuple, uBLAS, URL: http://www.rationaldiscovery.com Parts of this blurb were taking the "who's using Boost.Python" page. Best Regards, -greg

2 1

Fall Review Schedule - version 1.0
by Tom Brinkman 19 Aug '05

19 Aug '05

Boost Fall Review Schedule - version 1.0 Contact Tom Brinkman at reportbase(a)gmail.com to request a review, to make updates to this document or to volunteer to be a review manager. Review Queue as of August 14, 2005. Not in any particular: 1. xpressive - Eric Niebler 2. logging - John Torjo 3. singleton - Jason Hise (new review needed) 4. function types - Tobias Schwinger (mini post-review needed) 5. output formatters - Reece Dunn (new review needed) 6. policy pointer - David B. Held 7. fixed strings - Reece Dunn 8. intrusive - Olaf Krzikalla 9. interfaces - Jonathan Turkanis Other Libraries: 10. factory - Federico Stella f.stella(a)flashnet.it 11. TR1 1. xpressive - Author: Eric Niebler eric(a)boost-consulting.com> Review Manager: needed Download: http://boost-sandbox.sf.net/vault/index.php?directory=eric_niebler Docs: http://boost-sandbox.sf.net/libs/xpressive Review Date: to be confirmed xpressive is a TR1 regex work-alike that also accepts regexes as expression templates and lets regexes nest and call each other recursively. Significant changes since 0.9.3 - c_regex_traits to wrap the global C locale - null_regex_traits for searching non-char data - doc and test improvements - bugs in static regexes and Unicode support squashed You can consider this the xpressive 1.0 release candidate. All that remains is to add more tests and documentation, and perhaps a tweak to the traits interface. 2. logging Author - John Torjo john(a)torjo.com Review Manager - Hartmut.Kaiser Hartmut.Kaiser(a)gmail.com Download: http://torjo.com/code/logging.zip Docs: http://torjo.com/ The Boost Log Library is a small library, who: * makes it very easy to declare/define new logs * allows you very simple access to logs * allows for log hierarchies, and for modifying log hierarchies * allows for easy and efficient enabling/disabling of logs/log hierarchies * allows for easy manipulation of log behaviors (the log's destination(s) and/or adjusting the original message) * is thread-safe Using the library in code is easy and straightforward: int i = 1, j = 2, k = 3; BOOST_LOG(app) << "testing " << i << '-' << j << '-' << k << std::endl; BOOST_LOG(dbg) << "this is a debug message, i=" << i << std::endl; BOOST_LOG(info) << "I just wanted to tell you something...."; Recent Additions: - can be compiled as a static/dynamic runtime (works as a DLL as well) - removed dependency on boost_thread Note: I did not test this on Unix, but it should work. If anybody can take a look at detail/ts_posix.hpp, I'd appreciate it. - solved other small issues, based on feedback - slightly improved documentation 3) Singleton Author - Jason Hise chaos(a)ezequal.com Review Manager - Needed Download: http://tinyurl.com/6qvrd (old version from previous review) Docs: http://tinyurl.com/6qvrd The singleton library provides multiple powerful methods of controlling the lifetimes of global resources. Client code can choose among the many provided methods of creation, or can easily write new creators for specialized initialization needs. Client code can additionally control precisely when a singleton instance is automatically created and destroyed, can create and destroy singleton instances explicitly any number of times, and can set up dependencies between singletons in an easy and natural way. 4) Function Types Author - Tobias Schwinger tschwinger(a)neoscientists.org Review Manager - John Maddock john(a)johnmaddock.co.uk Download: http://tinyurl.com/4oe7q (old version - from previous review) Docs: http://tinyurl.com/4oe7q This library provides a metaprogramming facility to classify, decompose and synthesize function-, function pointer-, function reference- and member function pointer types. For the purpose of this documentation, these types are collectively referred to as function types (this differs from the standard definition and redefines the term from a programmer's perspective to refer to the most common types that involve functions). The classes introduced by this library shall conform to the concepts of the Boost Metaprogramming library (MPL). The Function Types library enables the user to: * test an arbitrary type for being a function type of specified kind, * inspect properties of function types, * view and modify sub types of an encapsulated function type with MPL Sequence operations, and * synthesize function types. This library supports variadic functions and can be configured to support non-default calling conventions. This library was reviewed June 2005 and was accepted pending a mini post-review. 5. Output formatters Author - Reece Dunn msclrhd(a)hotmail.com Review Manager - Needed Download: Docs: This library was reviewed september 11, 2005. It requires a second full review. 6. Policy Pointer Author - David B. Held dheld(a)codelogicconsulting.com Review Manager - Gennadiy gennadiy.rozental(a)thomson.com Download: Boost Sandbox under policy_ptr Docs: Boost Sandbox under policy_ptr Smart pointers are used to automate memory management by handling the deletion of dynamically allcoated objects (and other resources). They assist in ensuring program correctness, exception safety, and memory integrity. Policy Pointer is a policy-based smart pointer framework designed to accomodate the large number of smart pointer designs. Through the use of policy classes, virtually any smart pointer type can be constructed within this framework. This library is a Boostification of the original Loki::SmartPtr type with significant modifications. 7. Fixed Strings Author - Reece Dunn msclrhd(a)hotmail.com Review Manager - Beman Dawes bdawes(a)acm.org Download: boosts-sandbox/boost/fixed_string Docs: boosts-sandbox/boost/fixed_string The fixed string library provides buffer overrun protection for static sized strings (char s[ n ]). It provides a C-style string interface for compatibility with C code (for example, porting a C program to C++). There is also a std::string-style interface using a class based on flex_string by Andre Alexandrescu with a few limitations due to the non-resizable nature of the class. 8. Intrusive Author - Olaf Krzikalla krzikalla(a)gmx.de Review Manager - needed Download: http://people.freenet.de/turtle++/intrusive.zip Docs: http://people.freenet.de/turtle++/intrusive.zip While intrusive containers were and are widely used in C, they became more and more forgotten in the C++-world due to the presence of the standard containers, which don't support intrusive techniques. Boost.Intrusive not only reintroduces this technique to C++, but also encapsulates the implementation in STL-like interfaces. Hence anyone familiar with standard containers can use intrusive containers with ease. 9. Interfaces Author - Jonathan Turkanis technews(a)kangaroologic.com Review Manager - needed Download: http://www.kangaroologic.com/interfaces Docs: http://www.kangaroologic.com/interfaces "Boost.Interfaces provides a macro-based Interface Definition Language (IDL) which can be used to define C++ class types called interfaces. An interface is a lightweight value type associated with a set of named function signatures. An interface instance can be bound at runtime to any object which implements the interface, i.e., to any object of a type with accessible non-static member functions having the same name and signature as the set of functions associated with the interface. The functions of the bound object can then be invoked through the interface instance using the 'dot' operator. Binding is completely non-intrusive: the object's type need not declare any virtual functions or derive from any particluar base class. "Current applications of Boost.Interfaces include: * Non-intrusive dynamic polymorphism — interfaces can often be used in place of abstract base classes, and are sometimes much faster (see Performance). * Dynamic inheritance — allows function calls to be forwarded automatically to an object specified at runtime (see Delegation). * Smart Interface Pointers — smart pointers which can manage the lifetime of any object whose type implements a given interface. * Smart References — like smart interface pointers, but the managed object is accessed using the "dot" operator."

11 11

(Vector) norm functions?
by Daryle Walker 19 Aug '05

19 Aug '05

Should we add functions to evaluate the various norms of a (numeric) sequence? //======================================================================= template < typename Number, typename InputIterator > Number norm_1( InputIterator b, InputIterator e ) { using std::abs; return std::accumulate( b, e, Number(), abs(_1) + abs(_2) ); } template < typename Number, typename InputIterator > Number norm_2( InputIterator b, InputIterator e ) { using std::sqrt; return sqrt( std::inner_product( b, e, b, Number() ) ); } template < typename Number, typename InputIterator > Number norm_infinity( InputIterator b, InputIterator e ) { using std::abs; return abs( *std::max_element( b, e, abs(_1) < abs(_2) ) ); } template < typename Number, typename InputIterator > Number norm_x( int n, InputIterator b, InputIterator e ) { switch ( n ) { default: { using std::pow; using std::abs; Number r = Number(); for ( ; b != e ; ++b ) { r += pow( abs(*b), n ); } return root( r, n ); } case 2: return norm_2<Number>( b, e ); case 1: return norm_1<Number>( b, e ); case 0: // You can't really have a zero-norm // And you can't pass in infinity as a parameter // So we have 0 -> infinity return norm_infinity<Number>( b, e ); } } //======================================================================= I just wrote that here, so I don't know if it can work. I don't know if I used the bind/lambda stuff correctly, and there's still the problem that the "root" function doesn't exist. -- Daryle Walker Mac, Internet, and Video Game Junkie darylew AT hotmail DOT com

3 3

Re: [boost] serialization queston
by Robert Ramey 19 Aug '05

19 Aug '05

Upon (re) reading this, I'm not really sure what is being suggested here. That's why I didn't respond to the original post. I think my view that there is no problem probably reflects my lack of understanding of the original question. Anyway - here it is. Robert Ramey >Why not make include polymorphic_archive automatic? And make other >archive types resort to polymorphic_archive when no serialization for >that archive type was BOOST_CLASS_EXPORTED. As you say, the only cost >is a "teensy bit of execution time", in most cases users won't even >notice, but the code size will be reduced. I am generally not in favor of adding code not requested by the library user and not required. I much prefer that the library reflect what the user has said he wants. So my view is there are a couple of options. a) if one want's to use a polymorphic archive, include that in a (possibly precompiled) module. b) if one want's to use the template archive implementations, specify the ones you want. c) if this generates too much code bloat, make a library which includes any or all of the above. Its fairly easy to do this. Then link against your library of serialization implementations. Only ones actually used will be included in your program. So this would automatically give you access to ALL archive implementations without including dead code in your applications. The C++ module to build the library would look something like: #include <boost/archive/text_iarchive.hpp> #include <boost/archive/text_iarchive.hpp> #include <boost/archive/xml_iarchive.hpp> ... #include <boost/archive/polymorphic_iarchive.hpp> #include <boost/archive/polymorphic_oarchive.hpp> #include A.hpp #include B.hpp ... // if class modules above don't include export then BOOST_CLASS_EXPORT(A) BOOST_CLASS_EXPORT(B) Robert Ramey

2 2