- Boost - lists.preview.boost.org

[Serialization] Build failures on the Boost trunk
by Douglas Gregor 27 Mar '08

27 Mar '08

I'm currently getting a bunch of errors from the serialization library on the Boost trunk on Mac OS X 10.4: darwin.compile.c++ ../../../bin.v2/libs/mpi/build/darwin-4.0.1/debug/ macosx-version-10.4/content_oarchive.o../../../boost/archive/impl/ archive_pointer_oserializer.ipp: In constructor 'boost::archive::detail::archive_pointer_oserializer<Archive>::archive_p ointer_oserializer(const boost::serialization::extended_type_info&)':../../../boost/archive/ impl/archive_pointer_oserializer.ipp:41: error: 'singleton' is not a member of 'boost::serialization'../../../boost/archive/impl/ archive_pointer_oserializer.ipp:43: error: expected primary- expression before '>' token../../../boost/archive/impl/ archive_pointer_oserializer.ipp:43: error: '::get_mutable_instance' has not been declared../../../boost/archive/impl/ archive_pointer_oserializer.ipp: In static member function 'static const boost::archive::detail::basic_pointer_oserializer* boost::archive::detail::archive_pointer_oserializer<Archive>::find (const boost::serialization::extended_type_info&)':../../../boost/ archive/impl/archive_pointer_oserializer.ipp:54: error: 'singleton' is not a member of 'boost::serialization'../../../boost/archive/impl/ archive_pointer_oserializer.ipp:56: error: expected primary- expression before '>' token../../../boost/archive/impl/ archive_pointer_oserializer.ipp:56: error: '::get_const_instance' has not been declared../../../boost/archive/impl/ archive_pointer_oserializer.ipp:57: error: 'singleton' is not a member of 'boost::serialization'../../../boost/archive/impl/ archive_pointer_oserializer.ipp:57: error: '::get_const_instance' has not been declared../../../boost/archive/impl/ archive_pointer_oserializer.ipp:57: error: expected primary- expression before 'void'../../../boost/archive/impl/ archive_pointer_oserializer.ipp:57: error: expected `)' before 'void'../../../boost/archive/impl/archive_pointer_oserializer.ipp:57: error: expected `)' before ';' token../../../boost/archive/impl/ archive_pointer_oserializer.ipp: In destructor 'virtual boost::archive::detail::archive_pointer_oserializer<Archive>::~archive_p ointer_oserializer()':../../../boost/archive/impl/ archive_pointer_oserializer.ipp:73: error: 'singleton' is not a member of 'boost::serialization'../../../boost/archive/impl/ archive_pointer_oserializer.ipp:75: error: expected primary- expression before '>' token../../../boost/archive/impl/ archive_pointer_oserializer.ipp:75: error: '::get_mutable_instance' has not been declared Any idea about what's happening? - Doug

1 0

New boost::function allocator semantics?
by Emil Dotchevski 27 Mar '08

27 Mar '08

What is the procedure for updating the boost::function allocator semantics according to http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2308.html? A working implementation is available here: http://www.revergestudios.com/boost-function/ I'm asking because it will break legacy code that uses the current allocator support in boost::function. Such legacy code would be very easy to fix (of course, legacy code that uses boost::function without supplying custom allocator will not break.) -- Emil Dotchevski Reverge Studios, Inc. http://www.revergestudios.com/reblog/index.php?n=ReCode

2 1

Re: [boost] Reminder: review will end March 28th
by Cédric Venet 27 Mar '08

27 Mar '08

Hi, I am not sure to be qualified to make a review but I will give it a try. First, I think the library should be accepted. > - What is your evaluation of the design? Seems good. I must say I didnt read or try the transform part of proto. > - What is your evaluation of the implementation? Didnt read the code > - What is your evaluation of the documentation? I think there is some (more) work to do on it. I had some probleme with users_guide\expression_construction\construction_utils.html Because it was not clear to me how to put it in pratice. In fact after a fast read of the doc, I mostly used the exemple as reference of how to do something. So, I don't know exactly what can be done but some ideas may be: *Provide more basic exemple *Refer to the exemple in the documentation to show the practical use of what is described. *make a FAQ One difficulty I didn't had time to study is how to do polymorphic grammar or semantic checking. (perhaps I should not put this in the review). Mor clearly, I add two example: First I would like to have a grammar which can work on any terminal but can only have compatible terminal in a one expression (for example, you can't have vector and list in one expression but you can have one expression with lists and one with vector and they would follow the same grammar). My idea was to do a basic proto grammar which just check operator use and then to use a transform to fold the type of the terminals, checking they are all compatible. Second, I have a grammar where I can add terminals 'a+b' and index terminal 'a[b]'. you can have '(a+b)[c]'. some terminals may be indexable but other not. I could make a grammar for indexable terminal and another for not indexable but it would be duplicated. And if I add more properties to my terminals (for example Boolean, integer or float), the number of grammar explode. I was thinking to again use a transform to check the 'semantic' of the expression. Is it the way to go? I didn't see any reference to this in the documentation, but this seems a common pattern to me? The proto grammar would only check the 'parsing' and one transform would check the semantic. A yes, I would add two note which seem relevant for VS user: * the compiler flag -Zm (for example -Zm150) to change the maximum size of the precompiled header * the pragma inline_recursion and inline_depth (default off and 8) > - What is your evaluation of the potential usefulness of the library? Extremely useful. > - Did you try to use the library? With what compiler? Did you have any > problems? I used it with VS2005. I didnt had any problem (at least not one which wasnt my fault) > - How much effort did you put into your evaluation? A glance? A quick > reading? In-depth study? I read the doc and started writing a small test. Didnt had the time to try transform. Regards, -- Cédric

1 0

[proto] I'm trying to write a vector class
by Noah Stein 27 Mar '08

27 Mar '08

Eric, I spent a few hours the other week trying to convert my last matrix-vector class library over to proto. It implemented expression trees, but I’d never gotten around to adding some features that proto should make much, much easier to implement such as expression optimization. I figured it would be a good way to experiment with the library to review. I eventually gave up on refactoring my class towards proto and instead tried refactoring your lazy_vector example towards my class. It's raised some questions/points. I'll illustrate with questions that are based on your lazy_vector example. 1) lazy_vector seemed like it could derive from lazy_vector_expr in CRTP fashion. I figured your use of std::vector<T> as the terminal type was just to make initialization easier; however, using CRTP fails to compile. Did I miss this in the documentation or is it not explicitly mentioned? 2) How can I handle scalar values transparently? My attempts to accept "v1=v2*5" have failed. I can't get the 5 to implicitly construct into a scalar_vector type I have defined. I had that working in my old one, but I can't seem to figure out the correct way of setting that up in proto. 3) My vector class' signature is very simple: template<typename T> class Vector : VectorExpr<terminal<T> > . The type T contains a number of traits defining the vector: the type of the elements, the dimension, how the data is stored. I can't figure out how to specify the terminals in my grammar. In your example, you use terminal<std::vector<_> > as your terminal. The std::vector part is unknown to me. That's my point of variation in my vector concept thus I can't know all the different types that could be used in the terminal. I tried deriving my storage classes from a common base class; however, that failed. Is there any way to encode some sort of restriction in the grammar for this situation? Right now, I'm using _, but that's clearly not a great solution. Proto looks very interesting. I was quite excited the first I saw it mentioned. There seems to be a lot of power there. I just need to figure out how to use it. You have a lot of documentation, but it seems to be attacking the problem from the opposite direction I'm approaching from, so it's been a little slow going. I hate asking questions about something I can investigate on my own, but I'd like to get far enough along that I can properly review it. Thanks, Noah No virus found in this outgoing message. Checked by AVG. Version: 7.5.519 / Virus Database: 269.22.0/1342 - Release Date: 3/25/2008 10:26 AM

2 3

Status of thread safe signals?
by James Talbut 27 Mar '08

27 Mar '08

What is the status of the thread safe signals library in sandbox/thread_safe_signals? Will it go in the main boost library at some point? Thanks Jim P Consider the environment. Please don't print this email. ________________________________________________________________________ This e-mail, and any attachment, is confidential. If you have received it in error, do not use or disclose the information in any way, notify me immediately, and please delete it from your system. ________________________________________________________________________

4 4

[pending/relaxed_heap.hpp] assert problem
by Dawson, Paul (UK Filton) 27 Mar '08

27 Mar '08

Using relaxed_heap I'm getting a problem with the asserts in the top() and pop() functions: assert(smallest_value->value != 0); Where value is a ::boost::optional<T>, and T is the indexed type of the heap. The problem that I'm having is that when my T is an int, and the int in question is perfectly valid and has an initialised value of zero, it fails the assert test. Based on my limited understanding, we would actually want to be asserting either (smallest_value != 0) since smallest_value is a pointer, or (smallest_value->value.is_initialised()) since this is an optional. Apologies if I have misunderstood something, as I am a newcomer to boost. Many thanks, Paul. --------------------------- Paul Dawson BAE Systems (Operations) Limited Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, Farnborough, Hants, GU14 6YU, UK Registered in England & Wales No: 1996687 ******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ********************************************************************

2 1

[gsoc2008] contacting the mentors
by Gautam Sewani 27 Mar '08

27 Mar '08

Hi, I am working on my proposal for GSOC 08 under Boost and I'd like to talk to the mentors.I was unable to find their contact details, can anyone help me in this regard? Yours Sincerely, Gautam Sewani

2 1

[interprocess] [shared_ptr] Failure to type convert offset_ptr<T> to T *
by Aleksey Midenkov 27 Mar '08

27 Mar '08

The failure is in sp_counted_impl.hpp:66: 64 template<class Ptr> 65 sp_counted_impl_pd(const Ptr & p, const A &a, const D &d ) 66 : this_allocator(a), D(d), m_ptr(p.get()) 67 {} p is of type offset_ptr<T> and m_ptr is of type T * Test case source, compiler output and quick fix patch (which is not fully correct, I suspect) are attached. $ g++ --version g++ (GCC) 4.2.3 (Debian 4.2.3-2) Copyright (C) 2007 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

2 1

Trac open bugs - by assignee
by Marshall Clow 27 Mar '08

27 Mar '08

[ 237 open bugs today, 235 yesterday ] If you are maintaining a library, and have not logged into the trac system at <http://svn.boost.org/trac/boost/>, please do so ASAP. Until you do that, no tickets can be assigned to you, and will remain under "None". Instructions on working with tickets can be found at: <http://svn.boost.org/trac/boost/wiki/TicketWorkflow> and a mapping of user names to "real names" can be found at: <http://svn.boost.org/trac/boost/report/16> Bug summary 24 djowel 21 az_sw_dude 15 vladimir_prus 14 grafik 13 dgregor 13 dave 12 doug_gregor 11 no-maintainer 11 bemandawes 11 agurtovoy 8 anthonyw 7 turkanis 7 jsiek 6 johnmaddock 5 witt 5 ramey 5 igaztanaga 4 matias 4 ebf 3 nesotto 3 nasonov 3 kaalus 3 danielw 3 danieljames 2 shammah 2 samuel_krempp 2 rogeeff 2 pavol_droba 2 marshall 2 jmaurer 2 hkaiser 2 aaron_windsor 2 None 1 urzuga 1 t_schwinger 1 speedsnail 1 pdimov 1 garcia 1 fcacciola 1 dlwalker 1 chris_kohlhoff None 1644 Boost.Test missing documentation file BOOST_CHECK_CLOSE_FRACTION.html None 1719 [addressof] Can't obtain the address of an instance of an anonymous struct aaron_windsor 1622 Adjacency list needs to handle self-edges correctly aaron_windsor 778 top-level configure is broken agurtovoy 1001 gcc 4.1.2 segfaults on mpl/test/apply.cpp agurtovoy 1051 MPL header ordering triggers bug agurtovoy 1099 unable to iterate through a "non-explicitly-declared" mpl::set agurtovoy 1215 Boost 1.34.1_ mpl: Wrong workaround detection using MinGW32 (or.hpp_ line #33) agurtovoy 1317 has_xxx randomly broken in msvc agurtovoy 1469 [mpl] nested typedef of set has two different meanings agurtovoy 1476 always<> is not nullary. agurtovoy 1528 g++ 4.3.0 reports error because of redeclaration of next agurtovoy 1549 Boost.MPL: 'index_of' algorithm is not documented agurtovoy 1568 duplicate include guards agurtovoy 588 mpl::remove compile error with gcc 4.1.0 anthonyw 1154 tss destruction segfaults in conjunction with dlopen/dlclose anthonyw 1168 [thread] tss crashes randomly anthonyw 1268 xtime_cmp changes to deal with overflow were reverted anthonyw 1470 Boost.Thread: Compilation errors with non-__cdecl calling convention anthonyw 1657 Bug in boost::threads sample anthonyw 1713 no definitions for copy ctor and assignment operator for basic_condition_variable anthonyw 876 xtime documentation incomplete anthonyw 881 errors when build with Apache stdcxx az_sw_dude 1028 typo in boost header: date_time/time_defs.hpp az_sw_dude 1078 from_iso_string cannot read the output from to_iso_string az_sw_dude 1098 Urgent libboost-date-time1.33.1 : bugs on ia64 ? az_sw_dude 1147 date_time library contains global #define ERROR az_sw_dude 1160 warning: month_format shadows a member of this az_sw_dude 1162 warning: ticks shadows a member of this az_sw_dude 1289 posix_time::time_facet forgets to pass a_ref argument to base class az_sw_dude 1299 change in typedef stringstream_type in format_date_parser.hpp causing compilation error az_sw_dude 1306 invalid docbook in date_period.xml az_sw_dude 1384 Linking problem with date_time library on Visual C++ 2008 Express az_sw_dude 1386 date_time documentation Jamfile breaks building of boost docs az_sw_dude 1524 format_date_parser.hpp(221) : cannot convert parameter 1 az_sw_dude 1574 operator<< for boost::posix_time::ptime ignores ostream flags az_sw_dude 1674 date_time::date_formatting.hpp: incorrectly formats year using global locale az_sw_dude 1695 add correct namespace to class to fix compilation bug az_sw_dude 287 wrong usage of ios_base::narrow az_sw_dude 316 date_time type conversion warning az_sw_dude 604 from_ftime incorrectly processes FILETIME filled with zeros az_sw_dude 642 operator<< for gregorian::date_duration not found az_sw_dude 889 Insane Dependencies az_sw_dude 890 date_time library supports only the current dst rule bemandawes 1378 filesystem path invalid name for hidden files (LINUX) bemandawes 1389 filesystem::ostream << boost::format generates operator ambigious error (in MSVC++) bemandawes 1458 Darwin Tiger throws std::runtime_error: locale::facet::_S_create_c_locale name not valid bemandawes 1578 bug in readdir_r_simulator() in a multi-threaded environment bemandawes 1583 Serious flaw in boost::filesystem filename handling (opensuse) bemandawes 1589 [filesystem] 'mbstate_t' : is not a member of 'std' bemandawes 1606 filesystem/src/exception.cpp doesn't build with gcc bemandawes 1613 Link Errors against file_system on OS X with Intel Version 10.1 C++ compilers bemandawes 1682 path_traits needs imbue() bemandawes 1701 boost::filesystem::remove_all - segmentation fault with wpath on Linux bemandawes 752 directory_iterator doesn't work with catch chris_kohlhoff 1703 [asio] Compiler warnings on VC8/9 + warning level 4 danieljames 1554 When BOOST_HASH_NO_EXTENSIONS is defined hash doesn't support new string types. danieljames 1555 When BOOST_HASH_NO_EXTENSIONS is defined hash doesn't support boost::system::error_code danieljames 1705 [boostbook] Spaces in reference file names for types like 'long long' danielw 1044 Argument pack inaccessable in a functions return type danielw 1054 Parameter takes an "infinite" amount of time to compile with the Intel compiler. danielw 1097 keyword.hpp generates many warnings C4180: qualifier applied to function type has no meaning; ignored dave 1010 linking boost.python on freebsd dave 1019 iterator_facade::pointer should be the return type of operator-> (DR 445) dave 1085 Python rules for compiling in Mac OS X dave 1179 [boost.python] can not export a union in VC2005sp1 dave 1181 [boost.python] can modify enum value dave 1387 Review / update docs to reflect changes dave 1460 Python classes with multiple bases are convertible only to the first class in the lists dave 1482 boost::python::throw_error_already_set should be marked noreturn dave 1516 [python] Failing VC9 regression tests dave 1599 [python] '_set_se_translator': identifier not found dave 1697 [utility][noncopyable] ADL barrier broken by msvc-9.0 dave 865 Use of C++0x keyword as identifier dave 910 gcc strict-aliasing problems with python dgregor 1009 Improper overflow handling in shortest paths algorithms dgregor 1164 Floyd Warshall broken with unsigned edge weights dgregor 1192 [boostbook] problem when two files have the same name dgregor 1199 configure doesn't work with path containing whitespaces (MacOS X) dgregor 1310 [result_of] const-qualified function pointer doesn't work dgregor 1326 Unable to check graph isomorphism using LEDA adapter dgregor 1391 dominator_tree_test on Borland/CodeGear outputs overly long line dgregor 1395 Write Tests for Python Bindings dgregor 1630 gcc-4.3: adjacency_list.hpp includes deprecated header dgregor 1680 long long and wchar_t support in MPI dgregor 556 Bundled graph properties dgregor 732 Johnson All-Pairs needs better "no path" information dgregor 736 Const correctness violation djowel 1170 Emit Warnings instead of # symbols in the syntax highlighter djowel 1171 Quickbook title output djowel 1172 non-utf djowel 1176 Space after inline code djowel 1206 Escaping from within code? djowel 1273 CR+LF newlines in position_iterator djowel 1276 spirit problem with _GLIBCXX_DEBUG djowel 1277 Closing section like [pre with } causes Quickbok to crash djowel 1280 sections in imported source files get put inside <para> elements in docbook output djowel 1281 Quickbook produces invalid BoostBook/DocBook XML djowel 1324 tuple should have a swap() that operates element-by-element djowel 1396 wrong result_of invocation around transform_view djowel 1436 [quickbook] inline code inside headings djowel 1484 Quickbook produces illegal docbook for some docinfo fields. djowel 1500 [Spirit/Phoenix] C4512 Compiler warnings from VC8 djowel 1570 Some boost headers aren't ready for gcc 4.3 djowel 1600 duplicate include guard djowel 1601 distane of boost::tuple djowel 1607 Tuple Library Documentation Changes djowel 1610 [MSVC/STLport] [tree/common.hpp] Standard library requirements violation(incomplete type as vector parameter) djowel 1614 vector workaround needed for MSVC9 djowel 1617 spirit gcc-4.3 fix djowel 1619 [Fusion] C4512 warnings from VC9 (Visual Studio 2008) djowel 1722 [TR1/Fusion] Conflict between TR1 and Fusion headers dlwalker 613 boost/crc.hpp uses non-standard conforming syntax doug_gregor 1021 [Graph][reverse_graph] Problem using reverse_graph adapter with an adapted user defined graph doug_gregor 1076 compile error: disconnecting struct with operator()() doesn't work in VS2005 SP1 doug_gregor 375 LEDA graph adaptors do not handle hidden nodes properly doug_gregor 402 random_vertex/random_edge are unnecessarily inefficient doug_gregor 403 Document copy_component doug_gregor 447 reverse_graph and constness of property maps doug_gregor 708 Dijkstra no_init version should not require VertexListGraph doug_gregor 733 Numbered headers don't work with "preferred" syntax doug_gregor 735 Fruchterman-Reingold grid performance can be improved doug_gregor 738 Memory leaks with signal::connect? doug_gregor 829 Implicit graph not implement doug_gregor 852 Problem with Boost and GCC 4.1 ebf 1507 [variant] C4512 warnings from VC8.0 ebf 1548 [variant][docs]typo: formal arg_ operand_ should be v in times_two arglist ebf 1654 recursive variants do not handle nested variants correctly. ebf 993 Variant should use least common multiple of alignments_ rather than maximum fcacciola 1666 Visualizer for boost::optional garcia 1581 Boost.MultiArray: Resizing bug if the index is not 0-based grafik 1041 Cygwin requires PATH setting. grafik 1322 trac rejects patch attachment as spam grafik 1417 Regresson tests hang in Darwin (Tiger) grafik 1430 Regression fails under Cygwin grafik 1433 Trac's spam detection rejects too many valid messages grafik 1512 Broken link to vacpp in bjam docs. grafik 1513 Broken link to bcpp in bjam docs. grafik 1571 boost bugtracker displays a patch incorrectly grafik 1576 cannot read non-ASCII output messages grafik 1577 Some commands don't work because hStdInput == 0 grafik 1663 build.bat cannot set/reset ERRORLEVEL grafik 616 Boost Jam_ and non english directorys grafik 959 linking fails when Boost is compiled with STLport 5.1.* on Linux (names mismatch) grafik 986 Problem building Python modules on boost 1.34.0 hkaiser 1079 boost-1.34.0 fails to compile. concept checks not satisfied. hkaiser 1670 wave almost unusably slow on real-world input igaztanaga 1080 boost::interprocess win32 global file mapping issue igaztanaga 1210 interprocess::barrier hangs during second use under linux (boost 1.33.1) igaztanaga 1390 Interpocess: managed shared memory failing completely under OS X igaztanaga 1634 boost::interprocess::vector cannot contain volatile int igaztanaga 1635 Incomplete include guard in boost/intrusive jmaurer 351 Diff in state of mersenne_twister gen between GCC3.41 & CW9 jmaurer 599 uniform_01 copies engine instead of using a reference johnmaddock 1081 Empty string rejected as perl-style regex johnmaddock 1314 Using SSE-intrinsics in VC8 causes static assert in type_with_alignment.hpp johnmaddock 1411 Fix BOOST_PARTIAL_SPECIALIZATION_EXPLICT_ARGS johnmaddock 1446 POSIX API doesn't use C locale johnmaddock 1451 error: use of C99 long long integer constant johnmaddock 1626 [type_traits] "bad_alloc is not a member of std" in has_virtual_destructor_test.cpp jsiek 1531 segfault in dynamic_bitset::reference assign operator jsiek 1540 Poisson distribution very slow for large mean (and may also overflow). jsiek 575 Calling subgraph::global_to_local on a root graph jsiek 636 strange compiling problem for transitive_closure jsiek 815 remove_edge core dumps on self-circle jsiek 875 No iterator based constructor for adjacency_matrix jsiek 900 graphml reader namespace handling is broken kaalus 1184 property_tree assignment (operator) bug kaalus 1604 property_tree xml parser doesn't compile with gcc kaalus 1678 Boost.property_tree::read_xml does not parse UNICODE file with BOMs marshall 1252 [pool] severe overhead with unaligned sizes. marshall 1493 SVN files making it through to install matias 1406 Understanding the Tables outdated matias 1651 incorrect typedefs in examples matias 1676 Dead links on Boost.Test example documentation. matias 1707 small typos in Boost.serialization documentation nasonov 1220 lexical_cast requires RTTI nasonov 1704 [any] 4512 warning from VC8/9 on warning level 4 nasonov 754 boost::any - typeid comparison across shared boundaries nesotto 1629 range/iterator_range.hpp bug nesotto 1675 [range] VC8 - compiler warnings when including range/array headers nesotto 1694 NDEBUG vs. BOOST_ASSERT in iterator_range.hpp no-maintainer 1068 Mersenne twister disables streaming for Visual C++ no-maintainer 1222 lambda::ret<T> should declare result_type. no-maintainer 1270 uniform_smallint doesn't compile with lagged_fibonacci random number generators no-maintainer 1515 [lambda] C4512 warnings from VC8.0 no-maintainer 1544 uniform_01 w/ref template param causes ref to ref error no-maintainer 1546 Method boost::random::uniform_int::operator()(engine_ value) is missing no-maintainer 1572 [lambda] smart pointer const-ness affects its contents no-maintainer 1632 Default Interval rounding policies incomplete no-maintainer 1691 [Random] Brokem MSVC workaround no-maintainer 781 Lambda: (_1 + "y")(string("x")) Doesn't Compile no-maintainer 819 uniform_int<> with type's maximum availaible range error pavol_droba 1152 rle_example fails pavol_droba 1385 begin must be boost-qualified pdimov 1106 shared_ptr<T> should not convert to shared_ptr<U> when T* doesn't convert to U* ramey 1285 [serialization] problem when including shared_ptr_132.hpp ramey 1708 Can't serialize class with private destructor ramey 1711 Boost Serialization export facility broken on gcc 4.1_ 4.2 ramey 1715 gcc-4.3 doesn't compile polymorphic_(i)(o)archive.hpp ramey 1721 Serialization examples don't compile in trunk for G++ 4.1 rogeeff 1383 signal.h features not found on Mac OS rogeeff 1542 [test] compiler errors when building with stdcxx library samuel_krempp 1699 Compile warning about initialization order. samuel_krempp 859 boost::format ignores a user defined locale shammah 290 perfomance: memory cleanup for pool takes too long shammah 386 boost::pool_allocator breaks with vector of vectors speedsnail 1138 Problems with TSS and static thread library t_schwinger 1653 wave executable erroneously required for build of function_types lib turkanis 1523 [iostreams] VC8/VC9 compiler warnings turkanis 1545 [boost/rational.hpp] 'noskipws' is not a member of 'std' turkanis 1579 gzip compressor should model DualUseFilter turkanis 1580 Add static assert to prohibit instantiating a chain with mode dual_use turkanis 1649 Fix definition of JavaScript menu to avoid long chains of functions turkanis 1656 Consider implementing flush() for symmetric filters turkanis 1671 type mismatch of buffer size parameter causes overload resolution to fail urzuga 574 [boost::lambda] Compile error with libstdc++ debug mode vladimir_prus 1132 program_options documentation error. vladimir_prus 1165 more quoting problems vladimir_prus 1274 Useless error message vladimir_prus 1321 invalid docbook in tool documentation vladimir_prus 1527 [program_options] Second (and subsequent) lines in tabbed text not aligned correctly vladimir_prus 1530 Program options documentation - Overview - Syntactic Information example typo vladimir_prus 1537 no value given in 'mysql_password =' vladimir_prus 1584 cryptic bbv2 error building quickbook vladimir_prus 1587 [program_options] crashes if value part missing in external configuration file vladimir_prus 1588 [program_options] crashes if value part missing in external configuration file vladimir_prus 1645 Invalid unicode support for default_value vladimir_prus 1679 added 4-way universal binary support from mac osx (ppc_ ppc64_ i386_ x86_64) vladimir_prus 469 multitoken broken vladimir_prus 689 [program_options] Endless loop with long default arguments vladimir_prus 850 program_options strips off escaped quotes in some situations witt 1046 Boost.Python quickstart instructions mention nonexistent target witt 583 Fixes for build on IBM pSeries for AIX and Linux witt 834 Homepage regression links witt 957 The "Getting Started" page does not mention the stdlib option witt 973 zip_iterator has value_type == reference -- -- Marshall Marshall Clow Qualcomm, Inc. <mailto:mclow@qualcomm.com> The famous British scientist, Lord Kelvin, said: "When you measure what you are speaking about and express it in numbers, you know something about it, but when you cannot (or do not) measure it, when you cannot (or do not) express it in numbers, then your knowledge is of a meagre and unsatisfactory kind."

1 0

[1.35.0] Last call for RC3 and final release
by Beman Dawes 27 Mar '08

27 Mar '08

As far as I know, all RC2 issues have been cleared. If there are any further changes to be made prior to generation of RC3 and the final release, please notify me immediately. A last run of the regression reports is being generated now. Unless that shows some unexpected regressions, RC3 will be generated immediately afterwards. The purpose of RC3 is to verify there were no packaging failures and no last minute breakages in the install scripts. Unless RC3 turns up showstoppers in those areas, it will then become the final release. --Beman

1 0

Formal review request : Boost Logging Library, take 3
by John Torjo 27 Mar '08

27 Mar '08

Hi all, Just to make it formal, although I said this when v2 got rejected. I'd like another shot, mid July. So, looking for a review manager ;) Any volunteers? Best, John -- http://John.Torjo.com -- C++ expert http://blog.torjo.com ... call me only if you want things done right

1 0

[pool] Tuning the growth characteristics of pool
by Chris Newbold 27 Mar '08

27 Mar '08

Greetings. We've started introducing boost::pool at various places in our software in order to manage allocation of small, short-lived objects. We have run into some difficulty, however, with the algorithm governing the growth of the blocks allocated internally. The currently implementation unconditionally doubles the number of chunks in each subsequent block. This works well for small to medium sized pools, but ends up becoming wasteful and, ultimately, scalability-limiting for pools holding several million objects. Right now we're using the get_next_size() and set_next_size() accessors to meddle with the growth curve and to enforce an absolute limit on next_size. This is somewhat clumsy, however, requiring us to wrap boost::pool with additional logic to inspect next_size and take evasive action when we don't like the new value. I think there might be value in formally parameterizing the algorithm used to expand the pool. My first thought on an interface for controlling the growth algorithm was to add it to the UserAllocator interface. Here's an example of how this might look with the default algorithm hoisted to default_user_allocator_new_delete: // Default UserAllocator implementation for boost::pool; // the block size is doubled on each allocation struct default_user_allocator_new_delete { typedef std::size_t size_type; typedef std::ptrdiff_t difference_type; static char* malloc(const size_type bytes) { ... } static void free(char* const block) { ... } static size_type next_size(size_type size) { return size << 1; } }; // An implementation of the UserAllocator interface for // use with boost::pool which allocates fixed-sized blocks // of 65536 chunks. struct fixed_block_size_allocator : public default_user_allocator_new_delete { static size_type next_size(size_type /* ignored */) { return 2 << 15; } }; One problem I can see with this approach is that "more clever" growth algorithms may want data assigned at runtime-- e.g. an absolute limit at which to stop doubling the block size. This need could be accommodated by making UserAllocators be copy-constructible and changing the boost::pool constructor to take an instance to UserAllocator to be copied and kept internally. Another alternative would be to keep the growth algorithm parameter separate from UserAllocator: // The default pool growth algorithm: it unconditionally doubles // the block size on each successive allocation struct default_growth_algorithm { static size_t operator()(size_t prev_size) { return prev_size << 1; } }; template <typename UserAllocator = default_user_allocator_new_delete typename GrowthAlgorithm = default_growth_algorithm> class pool; The same comments about the potential need to pass a copy-constructible instance of the algorithm to the boost::pool constructor apply to this solution too. I am more than willing to prototype some changes in the code if there is interest in extending boost::pool in this manner. -- Chris Newbold cnewbold(a)mathworks.com The MathWorks, Inc. +1.508.647.8077

2 1

[property_map, graph] optional properties
by Ares Lagae 27 Mar '08

27 Mar '08

Is there any support for optional properties in boost.graph? Suppose I want to write/read a graph to/from a file format that supports edge weights. It should be possible to write a function template that works with all graphs and writes/reads edge weights if those properties are in the graph. Is this currently possible using boost.graph? Would the following make sense: - add an operator bool() to the property_map concept that returns true for existing property map classes - add a class empty_property_map with an operator bool() that always returns false - make Graph.get() return empty_property_map for non-existing properties This would enable constructs such as: edge_weight_property_map = get(edge_weight, graph); if (edge_weight_property_map ) { std::cout >> edge_weight_property_map[0] >> ... } -- Ares Lagae Computer Graphics Research Group, Katholieke Universiteit Leuven http://www.cs.kuleuven.be/~ares/

2 2

[serialization][1.35.0] incompatible change in guid_initalizer?
by Bernd Speiser 27 Mar '08

27 Mar '08

Hi, using the serialization library in various versions, I encounter a problem with exporting guids when changing from boost 1.34.1 to 1.35.0 I am currently using gcc 4.3.0 (recent stable release) under openSuSE 10.2. I am separating the exporting macros into a header xxx_export.h. This is done to avoid excessive compilation times for files in which the export code is not needed. Moreover, various classes which have export code are separated into several files. Thus, I need to #include more than one xxx_export.h header into the final program cpp file. I get the follwing error during compile: header2_export.h:9: error: conflicting declaration ‘const boost::archive::detail::guid_initializer<Derived2>& <unnamed>::boost_serialization_guid_initializer_9’ header1_export.h:9: error: ‘<unnamed>::boost_serialization_guid_initializer_9’ has a previous declaration as ‘const boost::archive::detail::guid_initializer<Derived1>& <unnamed>::boost_serialization_guid_initializer_9’ Obviously, the symbol names are derived from the line number in the header file, right? Using two (or more) different export header files, this leads to confusion. I tried to remedy the situation by enclosing the BOOST_CLASS_EXPORT_GUID () macros in the two export header files in two different namespaces. OK, that worked. HOWEVER - it is not backward compatible with boost version 1.34.1. If I use the code that works with 1.3.50 with the earlier version, I get: In file included from exportTestn.cpp:10: header1n_export.h:10: error: expected initializer before ‘<’ token header1n_export.h:10: error: ISO C++ forbids declaration of ‘type name’ with no type header1n_export.h:10: error: wrong number of template arguments (1, should be 2) /usr/local/lib/gcc/x86_64-unknown-linux-gnu/4.3.0/../../../../include/c++/4.3.0/bits/stl_pair.h:72: error: provided for ‘template<class _T1, class _T2> struct std::pair’ header1n_export.h:10: error: explicit instantiation of non-template ‘int derived1::boost::archive::detail::export_archives_invoke’ header1n_export.h:10: error: expected `;' before ‘<’ token In file included from exportTestn.cpp:12: header2n_export.h:10: error: expected initializer before ‘<’ token header2n_export.h:10: error: ISO C++ forbids declaration of ‘type name’ with no type header2n_export.h:10: error: wrong number of template arguments (1, should be 2) /usr/local/lib/gcc/x86_64-unknown-linux-gnu/4.3.0/../../../../include/c++/4.3.0/bits/stl_pair.h:72: error: provided for ‘template<class _T1, class _T2> struct std::pair’ header2n_export.h:10: error: explicit instantiation of non-template ‘int derived2::boost::archive::detail::export_archives_invoke’ header2n_export.h:10: error: expected `;' before ‘<’ token Am I doing something wrong here? Is there a solution which works for both boost::serialization versions? I have attached the relevant files for reference. Note that files header1.h, header2.h, header1_export.h and header2_export.h are without the additional namespace, while files header1n.h, header2n.h, header1n_export.h, and header2n_export.h are WITH the additional namespace. Thanks for any help. Bernd

3 4

date_time streaming operators bug report
by Maxim Yegorushkin 27 Mar '08

27 Mar '08

Good evening gentlemen, Boost::gregorian::date streaming operators currently alter the locale of the stream by inserting a custom_date_facet allocated on the heap into the locale. The facet never gets explicitly destroyed, rather its ownership is passed to the locale. Locale's destructor destroys the facet eventually. As the code of the streaming operators, the constructor and the (compiler generated) virtual destructor of the facet belong to header files, the vtable for the facet ends up in the object file of the translation unit that first calls a streaming operator and creates the facet. The problem arises when using dynamic linking. It manifests itself most apparently when locale's destructor is invoked. Locale's destructor accesses the vtables of the facets when destroying them. This requires the vtables to be accessible. If the module which contained the vtable of custom_date_facet has already been unloaded, the facet on the heap is left with a dangling vtable pointer. If the virtual address space range of the unloaded module is not accessible any more (has been unmapped), accessing the dangling vtable pointer leads to a crash. The crash was first encountered on Windoze XP SP2 + MSVC 2005 SP1 + boost-1.33.x and reproduced on Linux Fedora 8 + gcc-4.1.4 + boost-1.34.1 on the same day. Here are the steps to reproduce: 1) A (C-language) application without C++ run-time dependencies explicitly loads at run-time two shared libraries (Foo, then Bar) linked dynamically against the same C++ run-time shared library. Loading the first library causes the C++ run-time library to be loaded and initialised. 2) A call is made to library Foo. The library outputs a boost::gregorian::date into std::cout, creating the facet. Another call is made to Bar just in case, which outputs just text into std::cout. 3) The libraries unloaded in the same order (Foo, the Bar). Unloading the second library decrements the reference counter of the C++ run-time dynamic library to zero and causes it do deinitialise. Deinitialising involves destroying the standard streams and eventually the locale the facet belongs to. The vtable pointer of the facet object refers to the address in Foo, which has already been unloaded. The application crashes. Following is output of Linux crush. Please note, in the backtrace in stack frame 0 offending address 0x00135f20 belongs to unloaded foo.so, which can be deduced from the process memory map. A fix might be to avoid passing the ownership of the facet to the locale of the stream (i.e. avoid calling imbue()), rather have the facet allocated statically elsewhere and use it if the stream does not have one already (attached explicitly by the user if desired). Max [max@zen boost_custom_date_facet]$ cat main.c #include <dlfcn.h> #include <stdlib.h> #include <stdio.h> #include <errno.h> #include <string.h> #define CHECK(expr, ...) if(expr) {} else { \ fprintf(stderr, "%s:%d: ", __FILE__, __LINE__); \ fprintf(stderr, __VA_ARGS__); \ fprintf(stderr, "\n"); \ exit(EXIT_FAILURE); \ } typedef void fun_t(); int main() { void *foo_lib, *bar_lib; fun_t *foo, *bar; printf("---- loading foo.so\n"); CHECK((foo_lib = dlopen("./foo.so", RTLD_NOW)), "%s", dlerror()); CHECK((foo = (fun_t*)dlsym(foo_lib, "foo")), "%s", dlerror()); printf("---- foo.so loaded\n"); printf("---- loading bar.so\n"); CHECK((bar_lib = dlopen("./bar.so", RTLD_NOW)), "%s", dlerror()); CHECK((bar = (fun_t*)dlsym(bar_lib, "bar")), "%s", dlerror()); printf("---- bar.so loaded\n"); printf("---- invoking foo()\n"); foo(); printf("---- invoking bar()\n"); bar(); printf("---- unloading foo.so\n"); CHECK(!dlclose(foo_lib), "%s", dlerror()); printf("---- foo.so unloaded\n"); printf("---- unloading bar.so\n"); CHECK(!dlclose(bar_lib), "%s", dlerror()); // <---- crashes here printf("---- bar.so unloaded\n"); return EXIT_SUCCESS; } [max@zen boost_custom_date_facet]$ cat foo.cc #include <iostream> #include <fstream> #include <boost/date_time/gregorian/gregorian.hpp> extern "C" void foo() { boost::gregorian::date d(2008, 3, 26); std::cout << "foo\n" << d << '\n' << std::ifstream("/proc/self/maps").rdbuf() << std::endl ; } [max@zen boost_custom_date_facet]$ cat bar.cc #include <iostream> extern "C" void bar() { std::cout << "bar" << std::endl; } [max@zen boost_custom_date_facet]$ cat test.sh #!/bin/bash -x uname -a rpm -q gcc gcc-c++ boost # exit on compiler errors set -e gcc -o main -g -Wall -Wextra -ldl main.c g++ -o foo.so -D_GLIBCXX_DEBUG -fpic -g -Wall -Wextra -shared foo.cc g++ -o bar.so -D_GLIBCXX_DEBUG -fpic -g -Wall -Wextra -shared bar.cc ls -l main foo.so bar.so # don't exit on main crash set +e ulimit -c unlimited rm -f core* LD_DEBUG=libs ./main gdb -silent main core* <<EOF bt EOF [max@zen boost_custom_date_facet]$ ./test.sh + uname -a Linux zen 2.6.24.3-34.fc8 #1 SMP Wed Mar 12 18:17:20 EDT 2008 i686 i686 i386 GNU/Linux + rpm -q gcc gcc-c++ boost gcc-4.1.2-33 gcc-c++-4.1.2-33 boost-1.34.1-7.fc8 + set -e + gcc -o main -g -Wall -Wextra -ldl main.c + g++ -o foo.so -D_GLIBCXX_DEBUG -fpic -g -Wall -Wextra -shared foo.cc + g++ -o bar.so -D_GLIBCXX_DEBUG -fpic -g -Wall -Wextra -shared bar.cc + ls -l main foo.so bar.so -rwxrwxr-x 1 max max 63878 2008-03-27 00:01 bar.so -rwxrwxr-x 1 max max 835145 2008-03-27 00:01 foo.so -rwxrwxr-x 1 max max 9298 2008-03-27 00:01 main + set +e + ulimit -c unlimited + rm -f core.25031 + LD_DEBUG=libs + ./main 25064: find library=libdl.so.2 [0]; searching 25064: search cache=/etc/ld.so.cache 25064: trying file=/lib/libdl.so.2 25064: 25064: find library=libc.so.6 [0]; searching 25064: search cache=/etc/ld.so.cache 25064: trying file=/lib/libc.so.6 25064: 25064: 25064: calling init: /lib/libc.so.6 25064: 25064: 25064: calling init: /lib/libdl.so.2 25064: 25064: 25064: initialize program: ./main 25064: 25064: 25064: transferring control: ./main 25064: ---- loading foo.so 25064: find library=libstdc++.so.6 [0]; searching 25064: search cache=/etc/ld.so.cache 25064: trying file=/usr/lib/libstdc++.so.6 25064: 25064: find library=libm.so.6 [0]; searching 25064: search cache=/etc/ld.so.cache 25064: trying file=/lib/libm.so.6 25064: 25064: find library=libgcc_s.so.1 [0]; searching 25064: search cache=/etc/ld.so.cache 25064: trying file=/lib/libgcc_s.so.1 25064: 25064: 25064: calling init: /lib/libgcc_s.so.1 25064: 25064: 25064: calling init: /lib/libm.so.6 25064: 25064: 25064: calling init: /usr/lib/libstdc++.so.6 25064: 25064: 25064: calling init: ./foo.so 25064: ---- foo.so loaded ---- loading bar.so 25064: 25064: calling init: ./bar.so 25064: ---- bar.so loaded ---- invoking foo() foo 2008-Mar-26 00110000-00111000 r-xp 00110000 00:00 0 [vdso] 00111000-00147000 r-xp 00000000 08:05 17178033 /home/max/src/boost_custom_date_facet/foo.so 00147000-00149000 rwxp 00036000 08:05 17178033 /home/max/src/boost_custom_date_facet/foo.so 00149000-0014c000 r-xp 00000000 08:05 17178034 /home/max/src/boost_custom_date_facet/bar.so 0014c000-0014d000 rwxp 00002000 08:05 17178034 /home/max/src/boost_custom_date_facet/bar.so 00700000-0070b000 r-xp 00000000 08:01 3649841 /lib/libgcc_s-4.1.2-20070925.so.1 0070b000-0070c000 rwxp 0000a000 08:01 3649841 /lib/libgcc_s-4.1.2-20070925.so.1 007b8000-007d3000 r-xp 00000000 08:01 3647869 /lib/ld-2.7.so 007d3000-007d4000 r-xp 0001a000 08:01 3647869 /lib/ld-2.7.so 007d4000-007d5000 rwxp 0001b000 08:01 3647869 /lib/ld-2.7.so 007d7000-0092a000 r-xp 00000000 08:01 3647870 /lib/libc-2.7.so 0092a000-0092c000 r-xp 00153000 08:01 3647870 /lib/libc-2.7.so 0092c000-0092d000 rwxp 00155000 08:01 3647870 /lib/libc-2.7.so 0092d000-00930000 rwxp 0092d000 00:00 0 00932000-00959000 r-xp 00000000 08:01 3649817 /lib/libm-2.7.so 00959000-0095a000 r-xp 00026000 08:01 3649817 /lib/libm-2.7.so 0095a000-0095b000 rwxp 00027000 08:01 3649817 /lib/libm-2.7.so 0095d000-00960000 r-xp 00000000 08:01 3649815 /lib/libdl-2.7.so 00960000-00961000 r-xp 00002000 08:01 3649815 /lib/libdl-2.7.so 00961000-00962000 rwxp 00003000 08:01 3649815 /lib/libdl-2.7.so 0616a000-0624a000 r-xp 00000000 08:01 4058038 /usr/lib/libstdc++.so.6.0.8 0624a000-0624e000 r-xp 000df000 08:01 4058038 /usr/lib/libstdc++.so.6.0.8 0624e000-0624f000 rwxp 000e3000 08:01 4058038 /usr/lib/libstdc++.so.6.0.8 0624f000-06255000 rwxp 0624f000 00:00 0 08048000-08049000 r-xp 00000000 08:05 17178019 /home/max/src/boost_custom_date_facet/main 08049000-0804a000 rw-p 00000000 08:05 17178019 /home/max/src/boost_custom_date_facet/main 09597000-095b8000 rw-p 09597000 00:00 0 b7f99000-b7f9b000 rw-p b7f99000 00:00 0 b7fb3000-b7fb4000 rw-p b7fb3000 00:00 0 bfec6000-bfedb000 rw-p bffea000 00:00 0 [stack] ---- invoking bar() bar ---- unloading foo.so 25064: 25064: calling fini: ./foo.so [0] 25064: ---- foo.so unloaded ---- unloading bar.so 25064: 25064: calling fini: ./bar.so [0] 25064: 25064: 25064: calling fini: /usr/lib/libstdc++.so.6 [0] 25064: ./test.sh: line 17: 25064 Segmentation fault (core dumped) LD_DEBUG=libs ./main + gdb -silent main core.25064 Using host libthread_db library "/lib/libthread_db.so.1". warning: Can't read pathname for load map: Input/output error. Missing separate debuginfo for ./bar.so Try: yum --enablerepo='*-debuginfo' install /usr/lib/debug/.build-id/63/a5b3dd1b5bb0cac7f2460e64314ba4bb271ba1 Reading symbols from /lib/libdl-2.7.so...Reading symbols from /usr/lib/debug/lib/libdl-2.7.so.debug...done. done. Loaded symbols for /lib/libdl-2.7.so Reading symbols from /lib/libc-2.7.so...Reading symbols from /usr/lib/debug/lib/libc-2.7.so.debug...done. done. Loaded symbols for /lib/libc-2.7.so Reading symbols from /lib/ld-2.7.so...Reading symbols from /usr/lib/debug/lib/ld-2.7.so.debug...done. done. Loaded symbols for /lib/ld-2.7.so Reading symbols from /usr/lib/libstdc++.so.6.0.8...Reading symbols from /usr/lib/debug/usr/lib/libstdc++.so.6.0.8.debug...done. done. Loaded symbols for /usr/lib/libstdc++.so.6.0.8 Reading symbols from /lib/libm-2.7.so...Reading symbols from /usr/lib/debug/lib/libm-2.7.so.debug...done. done. Loaded symbols for /lib/libm-2.7.so Reading symbols from /lib/libgcc_s-4.1.2-20070925.so.1...Reading symbols from /usr/lib/debug/lib/libgcc_s-4.1.2-20070925.so.1.debug...done. done. Loaded symbols for /lib/libgcc_s-4.1.2-20070925.so.1 Reading symbols from /home/max/src/boost_custom_date_facet/bar.so...done. Loaded symbols for ./bar.so Core was generated by `./main'. Program terminated with signal 11, Segmentation fault. #0 0x00135f20 in ?? () (gdb) #0 0x00135f20 in ?? () #1 0x061b5b51 in std::ios_base::Init::~Init () at /usr/src/debug/gcc-4.1.2-20070925/obj-i386-redhat-linux/i386-redhat-linux/libstdc++-v3/include/bits/basic_string.h:274 #2 0x061cb0f0 in __tcf_0 () at /usr/src/debug/gcc-4.1.2-20070925/obj-i386-redhat-linux/i386-redhat-linux/libstdc++-v3/include/iostream:76 #3 0x00803907 in __cxa_finalize (d=0x624b588) at cxa_finalize.c:56 #4 0x061a9c54 in __do_global_dtors_aux () from /usr/lib/libstdc++.so.6.0.8 #5 0x062251dc in _fini () from /usr/lib/libstdc++.so.6.0.8 #6 0x007cb0c2 in _dl_close_worker (map=0x9597f48) at dl-close.c:271 #7 0x007cb877 in _dl_close (_map=0x9597f48) at dl-close.c:729 #8 0x0095dd24 in dlclose_doit () from /lib/libdl-2.7.so #9 0x007c61b6 in _dl_catch_error (objname=0x96105c, errstring=0x961060, mallocedp=0x961058, operate=0x95dd00 <dlclose_doit>, args=0x9597f48) at dl-error.c:178 #10 0x0095e30c in _dlerror_run () from /lib/libdl-2.7.so #11 0x0095dd5a in dlclose () from /lib/libdl-2.7.so #12 0x080488b9 in main () at main.c:41 (gdb) quit

1 0

[smart_ptr] get_deleter documentation
by Daniel Frey 26 Mar '08

26 Mar '08

Hi, get_deleter is missing "throws: nothing". At least I hope it never throws... :) Regards, Daniel

2 2

[1.35.0] Release Candidate 2 available
by Beman Dawes 26 Mar '08

26 Mar '08

1.35.0 Release Candidate 2 (RC2) is available at http://boost.cowic.de/rc/ RC2 fixes all of the serious issues reported for RC1. Note that links to the web site from the RC appear to be broken because the restructured web site will not go live until the actual release ships. In the meantime, the new website content is available at beta.boost.org. Please take the time to download RC2, and try to install it on your system. Kick the tires, and report any problems or issues you discover. Report by posting to either boost(a)lists.boost.org or boost-users(a)lists.boost.org. For a list of known issues, see http://svn.boost.org/trac/boost/wiki/MergeOneDotThreeFiveDotZero. Thanks, --Beman

9 19

Re: [boost] [1.35.0] Release Candidate 2 available
by Bruno Lalande 26 Mar '08

26 Mar '08

> > > Is the release mode link error an actual error, or just (un)informative > messages being printed by the linker. Apparently it's not a mere informative message, since the link phase finally ends up in error with a "collect2: ld returned 1 exit status". However, the description of the bug #16276 that originated the bug #16625 says that the issue "may lead to linker failure or corrupted binary", so indeed, it can be what I'm facing. Thanks for the information. Bruno

3 2

Why there is no boost::rational for non IntType ?
by Reetesh Mukul 26 Mar '08

26 Mar '08

Why there is no boost::rational for non IntType ? I think there are cases where we require such type of rationals, e.g. ( 2 + 3i) / (5 + 6i). In std::complex, we don't have any such constraint on element type of the complex number. That is, though std::complex<double> is quite natural we can have the construct std::complex<int> as well. Is boost::rational<> strictly modeled on the basis of rational numbers ? Another question, is there any continued fraction library in BOOST ? With Regards, Reetesh Mukul

4 3

[pool] boost::details::pool::lcm parameters
by dherring＠ll.mit.edu 26 Mar '08

26 Mar '08

Quick question: In boost/pool/detail/gcd_lcm.hpp, why does template <typename Integer> Integer lcm(const Integer & A, const Integer & B); take its parameters as const references instead of just passing the values? I don't see a reason to do this; gdc(A, B) takes values. Thanks, Daniel P.S. As seen in boost_1_35_0_RC2, aka boost-posix-2008-03-21.

2 2

Re: [boost] [Fwd: Re: [proto]possible morphism design (was Re: Proto review: a humble request]
by Eric Niebler 26 Mar '08

26 Mar '08

Larry Evans wrote: > Hi Eric. > > Apparently some of my posts aren't getting through. I posted > the attached before my reply to Hartmut, but it hasn't made it > to the newsgroup yet. So, I thought you might like a look at > it. Do you post messages to GMane or email them to the list. I do the later. From: Larry Evans <cppljevans(a)suddenlink.net> > On 03/24/08 17:15, Eric Niebler wrote: <snip> > > I can't tell where we are getting confused, but I > > suspect that you've been misled by the role of the terminal<>, negate<>, > > plus<>, etc. meta-functions. They are not expression types ... they are > > meta-functions that generate expression types. > > Yes. I'm embarrassed. I was away from the thread awhile and forgot > that in the expr equation here: > > http://archives.free.net.ph/message/20080322.024505.84b8c598.en.html > > expr *only* meant instances of proto::expr<Tag,Args,Arity> > for some Tag,Args, and Arity. > > The reason I added the ::type later was because I remembered that > using the meta-functions required that to produce an expression and > also, somewhere in my testing (can't remember where, ATM) I had to > append ::type to the args to a meta-function template's args to get an > expression. > > Sorry, I should have been more careful. No problem. Glad the fog of confusion is thinning. <snip> > > you can't convert a proto grammar to a proto expression type, in > > general. > > The 'in general' is the key phrase there. I wasn't attempting to > convert the grammars that weren't convertible. The grammars that > *are* convertible are those formed from the 'meta-functions that > generate expression types'( as you said above) *and* whose arguments > have been *similarly converted* (otherwise, an argument could be a > grammar and consequently the conversion result *wouldn't* be an > expression type). > > > We've covered this ground already ... grammar types are a > > super-set of expression types. > > I know. I'm sorry. I just hadn't got firm in my mind that > I was talking about expression types instead of meta-function > generators. The probable reason is that: > > meta-function<Args> is a grammar > > meta-function<Args>::type is an expression_type > (under certain restrictions on Args) Correct. > and: > > expression_type is a grammar > > got me mixed up and lead me to jump to the conclusion: > > expression_type::type is an expression type > > when, in fact, there's no such nested type. I supposed that > expression_type::type simply equaled expression_type (which is what > mpl meta-functions often do, IIRC). Right, expr<> doesn't have a nested ::type typedef. It used to, but it got renamed to ::proto_base_expr. > [snip] > > > > Any formalism that is based on > > converting a proto grammar to a proto expression by accessing a nested > > ::type typedef is wrong. Grammars are not convertible to expressions. > > The meta-functions that generate expression types are not expressions > > themselves. They are meta-functions. > > From: > > The meta-functions are also *usable as grammars* for matching such nodes > > on: > > libs/proto/doc/html/boost_proto/users_guide/expression_construction/tags_and_meta_functions.html > > a meta-function *is* a grammar and can be used to "generate expression > types"(quoting you). Maybe instead of "grammar conversion to > expression" I should have said "meta-function grammar use to generate > an expression". Hmm, ok. > I assume an example of this is: > > terminal<int>::type > > where grammar, terminal<int> (it's a grammar according to the above > .html reference), is used to generate the expression type, > expr<tag:terminal,args0<int> >. > > ============================================== > Now, back to the question of morphisms. If the source algebra is just > meta-function grammars whose arguments are also meta-function grammars, > then there's a morphism from that to the target algebra which is expression > types. The morphism, f, is simply applying the meta-function > recursively. The base case, is of course, the terminals: > > base_case: > > terminal<T> //a meta-function grammar in source algebra. > f<terminal<T> >::type > ==> terminal<T>::type //the corresponding expression in the target > //algebra. Yes. > > recursive_case: > > metafun<M1,M2,...Mn> //a meta-function grammar. > > f<metafun<M1,M2,...,Mn> >::type > ==> metafun<f<M1>::type,f<M1>::type,...,f<Mn>::type>::type > //^the corresponding expression in target algebra. Ah, yes. > here, metafun can be any of the meta-functions listed here: > > libs/proto/doc/html/boost_proto/users_guide/expression_construction/tags_and_meta_functions.html > > (except maybe the if_else_). The attached compiles and shows that the > above at least works for the morphism between 0-ary and 1-ary > meta-functions and expressions. The attached uses morphism instead of > f as the name of the morphism. OK! I understand that, and it is correct in the limited case of those dual-purpose grammars-and-metafunctions. I'm re-attaching your code, in case others want to see it. -- Eric Niebler Boost Consulting www.boost-consulting.com

1 0

[Fwd: [serialization][1.35.0] incompatible change in guid_initalizer?]
by Bernd Speiser 26 Mar '08

26 Mar '08

sorry, forgot to attach the files, here they are ... Bernd -------- Original Message -------- Subject: [serialization][1.35.0] incompatible change in guid_initalizer? Date: Wed, 26 Mar 2008 16:41:33 +0100 From: Bernd Speiser <bernd.speiser(a)uni-tuebingen.de> Reply-To: bernd.speiser(a)uni-tuebingen.de To: boost(a)lists.boost.org Hi, using the serialization library in various versions, I encounter a problem with exporting guids when changing from boost 1.34.1 to 1.35.0 I am currently using gcc 4.3.0 (recent stable release) under openSuSE 10.2.

1 0

[smart_ptr] shared_from_this
by Daniel Frey 26 Mar '08

26 Mar '08

Hello again, does shared_from_this() also guarantee that it never throws? Regards, Daniel

4 9

Build statically linked boost libs *-vc90-mt-sgd.lib
by Richard Crossley 26 Mar '08

26 Mar '08

Hi, Feeling stupid... How do I generate the statically linked *-vc90-mt-sg*.lib series of libraries? I've run: bjam debug release link=static toolset=msvc stage --build-dir=K:\Temp\BoostBuild Against the 1.35 R2 source Which, for example, gives me the following in the stage\lib directory libboost_*-vc90-mt-1_35.lib libboost_*-vc90-mt-gd-1_35.lib libboost_*-vc90-mt-gd.lib libboost_*-vc90-mt.lib Regards, Richard.

2 5

[getting-started][1.35] Link Update
by Daniel James 26 Mar '08

26 Mar '08

Hi, I've just checked in a fix for a link from getting started which broke for the updated Boost.Thread documentation. Please can someone with the python docutils rebuild the getting started documentation? Also, can I merge this to release? http://svn.boost.org/trac/boost/changeset/43866 Daniel

2 1