- Boost - lists.preview.boost.org

GTL compile time and concepts redesign
by Simonson, Lucanus J 03 May '08

03 May '08

I have modified my example code to move the accessors out of the templated traits class and into a non-templated concept struct as Fernando suggested. I also added compile time accessors that are parameterized by enum values, which I decided would give me the benefits of type safety and readability I was getting with my isotropic types as runtime parameters, while allowing the much desired compile-time parameter for people who prefer it. The runtime accessors are still there and call the compile-time accessors by default. The user can specialize the accessors to adapt them to their type, but now it is significantly harder to do so, because previously the accessors were members of a template class, and it was the class that was specialized, allowing the functions to retain their template parameter list. Now I am unable to partially specialize the accessor functions, which means that I cannot make their arguments template parameters of the function (because the user can't be expected to specialize for every conceivable type.) The user also has to explicitly specialize each version of the compile-time accessor, such as: template <> inline rectangle_traits<LayoutObject>::interval_type rectangle_concept::get<HORIZONTAL>(const LayoutObject& rectangle) { return rectangle_traits<LayoutObject>::interval_type(rectangle.xl, rectangle.xh); } template <> inline rectangle_traits<LayoutObject>::interval_type rectangle_concept::get<VERTICAL>(const LayoutObject& rectangle) { return rectangle_traits<LayoutObject>::interval_type(rectangle.yl, rectangle.yh); } and can't do the following: template <orientation_2d_enum orient> inline rectangle_traits<LayoutObject>::interval_type rectangle_concept::get(const LayoutObject& rectangle) { if(orient == HORIZONTAL) return rectangle_traits<LayoutObject>::interval_type(rectangle.xl, rectangle.xh); return rectangle_traits<LayoutObject>::interval_type(rectangle.yl, rectangle.yh); } as might be their first inclination. I'm not sure to what extent that makes specializing the accessors harder. User feedback I get is that specialization (all kinds) is hard, and in practice I usually help them out by providing the specializations they need for the types they have to get them over that first hurdle and running with library. I feel that there is still some more progress to be made here, please have a look. Thanks, Luke

1 0

Going to Boostcon? Need a ride from Denver?
by Marshall Clow 02 May '08

02 May '08

I'll be arriving in Denver about 1:00 PM on Sunday, renting a car and driving to Aspen. If anyone needs a ride, there should be room for at least a couple in my car. Reply privately, please - not to the list. -- -- Marshall Marshall Clow Idio Software <mailto:marshall@idio.com> It is by caffeine alone I set my mind in motion. It is by the beans of Java that thoughts acquire speed, the hands acquire shaking, the shaking becomes a warning. It is by caffeine alone I set my mind in motion.

1 0

Re: [boost] throw_exception rev. 44954 -> g++ warnings
by Ralf W. Grosse-Kunstleve 02 May '08

02 May '08

> In my opinion, this warning should be issued only if an attempt to > call the non-virtual destructor of a type with virtual functions > through a base class pointer is actually made, not simply because the > possibility exists. What's the disadvantage of adding the virtual destructors? It certainly is a huge disadvantage if -Wall cannot be used anymore. Until rev. 44954 everything we have compiled noise-free with -Wall (heaps of sources, many different gcc versions). I think the warning is useful. A library author cannot anticipate all situations in which the library may be used. If someone wants to derive from a class in a library and this triggers the smarter warning you propose for the first time, it is probably too late. If the library is part of the system headers it cannot be changed. The user is stuck. Ralf

2 1

[gil] [announcement] New IO lib
by Christian Henning 02 May '08

02 May '08

Hi there, over the past few months I have been working on a new version of gil's io extension. In this release I've added support for: * more image formats, most importantly bit_aligned images ( like 1bit images ), * reading of subimages like one row at a time for huge images, * reading image information, only. * having a unified interface for all sorts of devices, subimages, and converter objects. So far, png, jpeg, and tiff images are supported. In the not so distant future there will be bmp and pnm images added. You can grab the current version via subversion from: https://gil-contributions.googlecode.com/svn/trunk/gil_2/boost/gil/extensio… If desired I can supply a zip file to the vault. The images libraries can be grabbed from: ftp://ftp.uu.net/graphics/jpeg/jpegsrc.v6b.tar.gz ( www.ijg.org isn't responding ) http://www.libpng.org/pub/png/libpng.html http://www.libtiff.org/ It's highly advised to built your own version of the image lib you need. I installed the GNU's binaries for Windows, but unfortunately, I only had problems with them. The library is still header-only. When using boost::filesystem's paths, of course, you add a dependency to the filesystem lib. The Read Interface ------------------------ Reading an image can be done in multiple ways depending on what your need is. Like the old io lib there are 4 different ways of reading images. As there are: * read_image: Read image, the right amount of memory will be allocated beforehand. The supplied image type needs to be compatible with actual image file. * read_view: Read image, the image's memory must be already allocated. The supplied image type needs to be compatible with actual image file. * read_and_convert_image: Same as read_image, but the user can specify an color converter. * read_and_convert_view: Same as read_view, but the user can specify an color converter. There is a new function for reading image information. Since every image format has it's own set of tags, the library defines seperate image_read_info<format_tag> structures. Please see, for instance, the jpeg_tags.hpp header. As for the function parameters the following sections in the same order. 1. String for file name ( std::string, std::wstring, char*, boost::filesystem::path ) OR devices ( FILE*, TIFF*, std::ifstream ) 2. Image or view type 3. Optional: Subimage definition ( top_left corner + dimensions ) 4. Optional: Color converter. This parameter is only valid for converting functions. The default parameter is gil's default_color_converter 5. Format Tag. Reading the image information only takes parameter 1 and 5. Here are some examples for reading images: #include <boost/gil/extension/io_new/jpeg_read.hpp> // Read image information std::string filename( "..\\test_images\\jpg\\found online\\test.jpg" ); image_read_info< jpeg_tag > info = read_image_info( filename, tag_t() ); // Read image FILE* file = fopen( filename.c_str(), "rb" ); rgb8_image_t img; read_image( file, img, tag_t() ); // Read image ifstream in( filename.c_str(), ios::in | ios::binary ); rgb8_image_t img( 136, 98 ); read_view( in, view( img ), tag_t() ); // Read and convert image, use gil's default converter. rgb8_image_t img; read_and_convert_image( filename, img, tag_t() ); // Read a 10x10 subimage, starting from the top_left corner. rgb8_image_t img; read_image( filename, img, point_t( 0,0 ), point_t( 10, 10 ), tag_t() ); I have created some header files to support the old read interface. For example: #include <boost/gil/extension/io_new/jpeg_io_old.hpp> std::string filename( "..\\test_images\\jpg\\found online\\test.jpg" ); rgb8_image_t img( 136, 98 ); jpeg_read_view( filename, view( img ) ); The Write Interface --------------------------- The write interface is a much simpler than the read interface. Here, we only have write_view as the entry point. As for parameters the following sections are supported: 1. String for file name ( std::string, std::wstring, char*, boost::filesystem::path ) or devices ( FILE*, TIFF*, std::ofstream ) 2. View type 3. Optional: image_write_info< FormatTag > 4. Format type The image_write_info<...> structure defines a format specific properties which can be used when writing an image. A good example is jpeg's image quality value. Examples: #include <boost/gil/extension/io_new/tiff_write.hpp> // Write image string filename( "..\\test\\tiff\\test1.tif" ); gray8_image_t img( 320, 240 ); write_view( filename, view( img ), tiff_tag() ); // Write image string filename( "..\\test\\tiff\\test2.tif" ); TIFF* file = TIFFOpen( filename.c_str(), "w" ); rgb8_image_t img( 320, 240 ); write_view( file, view( img ), tag_t() ); I have created some header files to support the old write interface. For example: #include <boost/gil/extension/io_new/tiff_io_old.hpp> string filename( "..\\test\\tiff\\test3.tif" ); gray8_image_t img( 320, 240 ); tiff_write_view( filename, view( img ) ); Supported image formats ------------------------------------- In the process of developing the new version I tried to include as many formats as possible. One consequence is a much higher compilation time. Hopefully, a design review by the community can hint me better ways to reduce it. Also, there are still holes in the support. Most noteably is TIFF, since it can support almost everything. This makes it very hard not to have code explosion during compilation. Here is a list of list of supported formats: TIFF: * Number of samples: 1, 3, 4 ( eg. RGB would be 3 ) * Bits per sample: 1, 2, 4, 8, 16, 32, 64 * planar and interleaved images * indexed images. Indices can be of 1, 2, 4, 8, or 16 bit depth, whereas the palette must a rgb16_image_t. PNG: * gray, gray_alpha, rgb, rgba * bit_depth can be 1, 2, 4, 8, 16 JPEG: * gray, rgb, cmyk, ycck ( will be read as cymk ) Please note, that I'm still in process of testing all these different formats. The primary goal of this new version is to eventually replace the old io library which is part of boost's distribution. Do I need to apply for a review? I'm not sure how to go from here. I know there is still some work to do before a possible review. Documentation is lacking and support for dynamic image needs to be added. But what I want for now is to get some feedback on design and implementation. I would like to thank Lubomir Bourdev and Andreas Pokorny for their most valueable input. Thanks, Christian

6 16

Re: [boost] detail/shared_cout.hpp: missing workaround.hpp include
by Ralf W. Grosse-Kunstleve 02 May '08

02 May '08

Done. Thanks! ----- Original Message ---- From: Peter Dimov <pdimov(a)pdimov.com> To: boost(a)lists.boost.org Sent: Friday, May 2, 2008 12:25:54 PM Subject: Re: [boost] detail/shared_cout.hpp: missing workaround.hpp include Ralf W. Grosse-Kunstleve: > I'm getting compilation errors on several platforms due to a missing > include in boost/detail/shared_count.hpp. This header makes use of > BOOST_WORKAROUND, but workaround.hpp isn't included. > Are the any objections to adding the include? No. Please go ahead.

1 0

detail/shared_cout.hpp: missing workaround.hpp include
by Ralf W. Grosse-Kunstleve 02 May '08

02 May '08

I'm getting compilation errors on several platforms due to a missing include in boost/detail/shared_count.hpp. This header makes use of BOOST_WORKAROUND, but workaround.hpp isn't included. Are the any objections to adding the include? Ralf Index: boost/detail/shared_count.hpp =================================================================== --- boost/detail/shared_count.hpp (revision 45030) +++ boost/detail/shared_count.hpp (working copy) @@ -28,6 +28,7 @@ #include <boost/detail/bad_weak_ptr.hpp> #include <boost/detail/sp_counted_base.hpp> #include <boost/detail/sp_counted_impl.hpp> +#include <boost/detail/workaround.hpp> // In order to avoid circular dependencies with Boost.TR1 // we make sure that our include of <memory> doesn't try to // pull in the TR1 headers: that's why we use this header

2 1

[xml-archive] gcc-4.3 fails with boost svn 45019
by Neal Becker 02 May '08

02 May '08

./boost/exception/enable_error_info.hpp: In instantiation of boost::exception_detail::error_info_injector<boost::archive::archive_exception::exception_code> : ./boost/throw_exception.hpp:45: instantiated from void boost::throw_exception(const E&) [with E = boost::archive::archive_exception::exception_code] ./boost/archive/impl/xml_iarchive_impl.ipp:146: instantiated from void boost::archive::xml_iarchive_impl<Archive>::load_override(boost::archive::class_name_type&, int) [with Archive = boost::archive::naked_xml_iarchive] libs/serialization/src/xml_iarchive.cpp:38: instantiated from here ./boost/exception/enable_error_info.hpp:22: error: base type boost::archive::archive_exception::exception_code fails to be a struct or class type ./boost/exception/enable_current_exception.hpp: In instantiation of boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::archive_exception::exception_code> > : ./boost/throw_exception.hpp:45: instantiated from void boost::throw_exception(const E&) [with E = boost::archive::archive_exception::exception_code] ./boost/archive/impl/xml_iarchive_impl.ipp:146: instantiated from void boost::archive::xml_iarchive_impl<Archive>::load_override(boost::archive::class_name_type&, int) [with Archive = boost::archive::naked_xml_iarchive] libs/serialization/src/xml_iarchive.cpp:38: instantiated from here ./boost/exception/enable_current_exception.hpp:60: error: duplicate base type boost::exception_detail::error_info_injector<boost::archive::archive_exception::exception_code> invalid ./boost/exception/enable_error_info.hpp: In constructor boost::exception_detail::error_info_injector<T>::error_info_injector(const T&) [with T = boost::archive::archive_exception::exception_code] : ./boost/exception/enable_error_info.hpp:69: instantiated from typename boost::exception_detail::enable_error_info_return_type<T>::type boost::enable_error_info(const T&) [with T = boost::archive::archive_exception::exception_code] ./boost/throw_exception.hpp:45: instantiated from void boost::throw_exception(const E&) [with E = boost::archive::archive_exception::exception_code] ./boost/archive/impl/xml_iarchive_impl.ipp:146: instantiated from void boost::archive::xml_iarchive_impl<Archive>::load_override(boost::archive::class_name_type&, int) [with Archive = boost::archive::naked_xml_iarchive] libs/serialization/src/xml_iarchive.cpp:38: instantiated from here ./boost/exception/enable_error_info.hpp:25: error: type boost::archive::archive_exception::exception_code is not a direct base of boost::exception_detail::error_info_injector<boost::archive::archive_exception::exception_code> ./boost/exception/enable_current_exception.hpp: In constructor boost::exception_detail::clone_impl<T>::clone_impl(const T&) [with T = boost::exception_detail::error_info_injector<boost::archive::archive_exception::exception_code>] : ./boost/exception/enable_current_exception.hpp:144: instantiated from boost::exception_detail::clone_impl<T> boost::enable_current_exception(const T&) [with T = boost::exception_detail::error_info_injector<boost::archive::archive_exception::exception_code>] ./boost/throw_exception.hpp:45: instantiated from void boost::throw_exception(const E&) [with E = boost::archive::archive_exception::exception_code] ./boost/archive/impl/xml_iarchive_impl.ipp:146: instantiated from void boost::archive::xml_iarchive_impl<Archive>::load_override(boost::archive::class_name_type&, int) [with Archive = boost::archive::naked_xml_iarchive] libs/serialization/src/xml_iarchive.cpp:38: instantiated from here ./boost/exception/enable_current_exception.hpp:65: error: type boost::exception_detail::error_info_injector<boost::archive::archive_exception::exception_code> is not a direct base of boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::archive::archive_exception::exception_code> >

3 3

Re: [boost] [serialization] Trivial code fails to compile on gcc-4.3
by Neal Becker 02 May '08

02 May '08

Tim Blechmann wrote: >>> Do you know where to fix this? >>> >>> >> Patch is attached. >> >> Robert knows this, since I sent him this patch two weeks ago. >> >> Maybe I should have opened a bug report to make the patch public >> available. > > please do so ... there are quite a number of related bug reports on the > tracker ... > > btw, my personal git tree of boost contains a mirrored version of the > 1.35 release branch with patches for gcc-4.3 ... > http://tim.klingt.org/git?p=boost.git > How do I git it? git clone http://tim.klingt.org/git?p=boost.git boost.git Initialized empty Git repository in /usr/local/src/boost.git/.git/ Cannot get remote repository information. Perhaps git-update-server-info needs to be run there?

2 1

[serialization] Trivial code fails to compile on gcc-4.3
by Neal Becker 02 May '08

02 May '08

--- test2.cc #include <boost/serialization/nvp.hpp> #include <boost/serialization/vector.hpp> --- g++ -I /usr/local/src/boost.hg test2.cc In file included from test2.cc:2: /usr/local/src/boost.hg/boost/serialization/vector.hpp:185: error: redefinition of struct boost::serialization::implementation_level<std::vector<long int, std::allocator<long int> > > /usr/local/src/boost.hg/boost/serialization/vector.hpp:185: error: previous definition of struct boost::serialization::implementation_level<std::vector<long int, std::allocator<long int> > > /usr/local/src/boost.hg/boost/serialization/vector.hpp:185: error: redefinition of struct boost::serialization::implementation_level<std::vector<long unsigned int, std::allocator<long unsigned int> > > /usr/local/src/boost.hg/boost/serialization/vector.hpp:185: error: previous definition of struct boost::serialization::implementation_level<std::vector<long unsigned int, std::allocator<long unsigned int> > >

4 6

Trac open bugs - by assignee
by Marshall Clow 02 May '08

02 May '08

[ 301 open bugs today, 302 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 29 djowel 25 az_sw_dude 23 dgregor 22 grafik 17 dave 16 vladimir_prus 16 bemandawes 12 ramey 12 no-maintainer 12 anthonyw 11 agurtovoy 10 turkanis 10 jsiek 8 nesotto 8 matias 7 rogeeff 6 danieljames 5 igaztanaga 4 witt 4 pavol_droba 4 nasonov 4 johnmaddock 4 ebf 3 samuel_krempp 3 kaalus 3 danielw 2 troyer 2 shammah 2 marshall 2 jmaurer 2 hkaiser 2 garcia 2 <Blank> 1 urzuga 1 t_schwinger 1 speedsnail 1 pdimov 1 jano_gaspar 1 fcacciola 1 dlwalker 1 aaron_windsor 1 None <Blank> 1750 Autolink library name not in sync with actually build lib <Blank> 1879 region allocators: auto_alloc_ scoped_alloc None 1736 Headers containing non ASCII characters cause MS VC to issue warning 4819 in some locales aaron_windsor 1622 Adjacency list needs to handle self-edges correctly 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 1805 thread creation crashes with /Zp1 switch in VS2005 compiler anthonyw 1813 Signed/Unsigned warning in win32/condition_variable anthonyw 1825 thread.hpp injects windows.h and breaks user application. anthonyw 1826 Auto detection of threadapi and target-os broken under cygwin gcc anthonyw 1867 Missing member functions in shared_mutex (win32) anthonyw 1881 max() & min() macros are leaking from <windows.h> into entire project 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 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 1726 boost/date_time/posix_time/time_formatters.hpp incorrectly formats fractional seconds using global locale az_sw_dude 1740 date_time includes <windows.h> az_sw_dude 1788 local_time::local_time_period streaming operators not implemented az_sw_dude 1859 boost::gregorian::to_tm() doesn't fill in tm_zone on Mac OS X az_sw_dude 1878 Documention Corrections - Various date_time Pages 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 1711 Boost Serialization export facility broken on gcc 4.1_ 4.2 bemandawes 1767 missing file: boost/filesystem/cerrno.hpp bemandawes 1768 system: error_code.cpp #defines macros without checking whether already defined bemandawes 1840 name check functions have different behavior wrt empty string bemandawes 1876 portable_file_name() returns true for '.' and '..' bemandawes 752 directory_iterator doesn't work with catch 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' danieljames 1742 Some bugs in http://www.boost.org/doc/libs/1_35_0 danieljames 1743 Documentation has incorrect Build & Link settings for some libraries danieljames 1818 The tables in status reports jump all over the place. 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 1730 No debug libs on Windows by default dave 1851 Issue with proxies and rvalues dave 1860 zip_iterator::value_type should not be reference dave 1887 [doc] input_iterator_archetype is not a valid InputIterator 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 1021 [Graph][reverse_graph] Problem using reverse_graph adapter with an adapted user defined graph dgregor 1076 compile error: disconnecting struct with operator()() doesn't work in VS2005 SP1 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 1630 gcc-4.3: adjacency_list.hpp includes deprecated header dgregor 375 LEDA graph adaptors do not handle hidden nodes properly dgregor 402 random_vertex/random_edge are unnecessarily inefficient dgregor 403 Document copy_component dgregor 447 reverse_graph and constness of property maps dgregor 556 Bundled graph properties dgregor 708 Dijkstra no_init version should not require VertexListGraph dgregor 732 Johnson All-Pairs needs better "no path" information dgregor 733 Numbered headers don't work with "preferred" syntax dgregor 735 Fruchterman-Reingold grid performance can be improved dgregor 736 Const correctness violation dgregor 738 Memory leaks with signal::connect? dgregor 829 Implicit graph not implement dgregor 852 Problem with Boost and GCC 4.1 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 1651 incorrect typedefs in examples djowel 1763 wrong AST when parser_tag==0 djowel 1764 wrong AST when parser_tag==0 djowel 1844 Quickbook matches forward slashes (for italics) with slashes in links djowel 1864 [Documentation]There is no documentation for repetivive_view djowel 1872 [Spirit2] 'assignment operator could not be generated' warnings from VC9 dlwalker 613 boost/crc.hpp uses non-standard conforming syntax 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 garcia 1741 Review schedule out of date grafik 1041 Cygwin requires PATH setting. grafik 1322 trac rejects patch attachment as spam grafik 1406 Understanding the Tables outdated 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 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 1733 Website layout overlays on IE7 grafik 1735 [website] Wrong HTML on main documentation page. grafik 1738 Boost Jam details and download link grafik 1739 Search box and Google link grafik 1753 Python docs: bad link to the Jamroot grafik 1771 Statechart TOC mangled. grafik 1776 Documentation page renders incorrectly in Safari 3.1 on OS X grafik 1889 regression.py can't be run from a path with spaces (Windows) 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 jano_gaspar 1852 copy constructor does not copy capacity 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 1446 POSIX API doesn't use C locale johnmaddock 1451 error: use of C99 long long integer constant johnmaddock 1863 Boost.Regex unstable with Borland Turbo C++ 2006 jsiek 1531 segfault in dynamic_bitset::reference assign operator jsiek 1540 Poisson distribution very slow for large mean (and may also overflow). jsiek 1755 Boost.tokenizer is broken for wide characters - patch attached jsiek 1798 met an error using boost::tokenizer in multi-times in vs2005_ unicode jsiek 1888 Why doesn't InputIterator require that reference is convertible to value_type? 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 1854 Interval is not available as a component in the SVN system matias 1744 No information on building static libraries with bjam under Windows matias 1822 header dependency in boost/serialization/map.hpp matias 1853 Typo in interval documentation matias 1855 Typo in lambda documentation (online) matias 1866 Typos in Boost Test documentation matias 1869 Typo in Unit Test Framework documentation matias 1880 documentation bug matias 1886 Typo in Interval documentation nasonov 1220 lexical_cast requires RTTI nasonov 1704 [any] 4512 warning from VC8/9 on warning level 4 nasonov 1847 Can't compile without <locale> header_ boost::lexical_cast problem 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 nesotto 1748 [ptr_container] compiler warnings from VC9 nesotto 1754 Illegal HTML in range docs. nesotto 1785 assign::list_of works poorly with class constructors nesotto 1795 [ptr_container] minor documentation typo nesotto 1842 boost::sub_rage::front error 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 1856 minstd_rand returning different values in 1.35.0 than in 1.34.1 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 pavol_droba 1761 StringAlgo: Error in an example pavol_droba 1827 String algorithm composite header doesn't include join pdimov 1106 shared_ptr<T> should not convert to shared_ptr<U> when T* doesn't convert to U* ramey 1708 Can't serialize class with private destructor ramey 1734 BOOST_STATIC_WARNING can't be passed a dependent expression ramey 1747 [serialization] unreferenced formal parameter warnings from VC9 ramey 1807 boost::archive::xml_archive_exception does not store error code and reports wrong message text ramey 1812 Boost.Serialization fails to build on Cygwin ramey 1823 Archive concept: Incomplete description? ramey 1824 serialization keeps using wchar_t if BOOST_NO_STD_WSTRING is set ramey 1836 bug in serializing wide character strings ramey 1837 Base class missed in binary_wiarchive ramey 1849 Deserialization of std::string overwrites non-copied contents. ramey 1857 IA64_ GCC 4.3_ redefinition of 'struct boost::serialization::implementation_level<std::vector<long int_ std::allocator<long int> > >' ramey 1877 Documentation Corrections - Archive Concepts rogeeff 1383 signal.h features not found on Mac OS rogeeff 1542 [test] compiler errors when building with stdcxx library rogeeff 1644 Boost.Test missing documentation file BOOST_CHECK_CLOSE_FRACTION.html rogeeff 1676 Dead links on Boost.Test example documentation. rogeeff 1723 No subprocess can be started in init_unit_test_suite rogeeff 1746 Online documentation for 1.35.0 is out of date for current lib version rogeeff 1839 Test fails if child process exits with non-zero code samuel_krempp 1699 Compile warning about initialization order. samuel_krempp 1801 Typo in documentation. 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 troyer 1774 serialization: file written with 1.34.1 can't be read in with 1.35 troyer 1778 Possible regression in 1.35 serialization of 2D arrays 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 turkanis 1727 Sample code in documentation does not compile_ has namespace errors. turkanis 1870 zlib_base function names must differ from their zlib counterpart turkanis 1875 Boost.Iostreams warnings with GCC -Wall -W -std=c++98 -pedantic 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 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 1809 Allow empty values in conf file vladimir_prus 1816 --build-type=complete broken in current svn 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 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

[thread]joining the first thread finishing from a group of threads
by vicente.botet 02 May '08

02 May '08

Hello, I have several implementations of the same function with different algorithms. I want to launch these in parallel and join the one finishing the first, and stop the others. I have started and in my solution I need to wrap the function in order to make the needed synchronization, which seam not quite satisfactory. Is there an easy way to join the first thread that finish from a thread group and getting it? boost::thread_group tg; // ... boost::thread* first = tg.join_one(); Do you find useful this feature? Regards _____________________ Vicente Juan Botet Escriba

3 3

Strange font settings on www.boost.org
by Jens Seidel 02 May '08

02 May '08

Hi, I noticed that headlines look very strange on the new website. I think the problem is #content h1, #content h2, #content h3, #content h4, #content h5, #content h6 { margin: 0em; color: #000000; font-family: "Times New Roman",serif; font-variant: small-caps; clear: both; } in http://www.boost.org/style/css_0/content.css. Why is a special font used? I do not have such a font and I would also prefer if the browser would be able to use a default. As far as I know it is save to use a few standard font aliases such as sans-serif or similar in HTML but "Times New Roman" is probably not one of these, right? Jens

4 3

[optional] boost::variant<T,nil_t> in docs
by Alexander Nasonov 02 May '08

02 May '08

Shouldn't it be boost::variant<T,none_t> (nil_t -> none_t) instead? Thanks, Alex

1 0

gcc-4.3.0, shared lib build problem?
by Neal Becker 02 May '08

02 May '08

After building boost (recent svn Revision: 44635 ) using: bjam -sICU_PATH=/usr -sEXPAT_INCLUDE=/usr -sEXPAT_LIBPATH=/usr/lib64 --layout=system threading=single stage Then when I tried to re-build my shared object against the boost libs, I got: /usr/bin/ld: mod/ldpc.os: relocation R_X86_64_32 against `__dso_handle' can not be used when making a shared object; recompile with -fPIC Did -fPIC flag go missing when building the boost libs? (Can someone refresh my memory which bjam flag to use to show the compile invocation)?

1 1

Another C++ puzzler
by Marco Costalba 02 May '08

02 May '08

After the great success of Eric's puzzle on the common type of a given types set here it is another puzzle for you C++ wizards. This one arise from the multi signature boost function implementation recently posted to this list. Let's have two boost.function objects, each one defined on a different function signature Sig_1, Sig_2 boost::function<Sig_1> boost_fun_1; boost::function<Sig_2> boost_fun_2; Then have two overloaded template functions called "set" to assign a function/functor to either one of the above boost.function objects template<typename Fun> void set(Fun const& fun, typename enable_if<is_compatible<Fun, Sig_1> >::type* = 0) { boost_fun_1 = fun; } template<typename Fun> void set(Fun const& fun, typename enable_if<is_compatible<Fun, Sig_2> >::type* = 0) { boost_fun_2 = fun; } To disambiguate between the two a SFINAE technique is used on the second (hidden) argument of "set" Where struct is_compatible is defined as: /* Check if a function/functor Fun has a given signature Sig */ template<typename Fun, typename Sig> struct is_compatible { /* Check for a function */ template<class U> static yes_type check(typename enable_if<is_same<U, Sig> >::type*); /* Check for a functor */ template<class U, Sig U::*> struct helper; template<class U> static yes_type check(helper<U, &U::operator()>*); /* Default */ template<class U> static no_type check(...); typedef typename boost::remove_pointer<Fun>::type F; static bool const value = (sizeof(check<F>(0)) == sizeof(yes_type)); }; Now the puzzle is: There is a way to remove struct is_compatible altogether ? or at least greatly simplify it ? Constrains are - Public API must be set(fun) where fun is any functor/function for which either expression "boost_fun_1 = fun" or "boost_fun_2 = fun" compiles. - If both "boost_fun_1 = fun" and "boost_fun_2 = fun" are not compilable then a compile error should raise Hint: an almost working solution could have been template<typename Fun> void set(Fun const& fun, bool = (boost::function<Sig_1>() == fun)) { boost_fun_1 = fun; } template<typename Fun> void set(Fun const& fun, bool = (boost::function<Sig_2>() == fun)) { boost_fun_2 = fun; } But unfortunately it is forbidden to refer to an argument (fun in this case) in the expression of the default value of another argument. Have fun Marco

4 7

[ptr_container]ptr_multimap difference in doc and code
by Sergei Politov 02 May '08

02 May '08

Hi, I have found some differences in documentation for ptr_multimap, and its real implementation. In code: template< class U > iterator insert( key_type& key, std::auto_ptr<U> x ) { return insert( key, x.release() ); } In documentation: template< class U > iterator insert( const key_type&, std::auto_ptr<U> x ); The difference is in first argument of this function. I don't known which way is right to submit the bug report. Could somebody please help me? Best Regards, Sergei

2 2

[parameter][serialization] VC 8/9 regression test failures
by Richard Webb 02 May '08

02 May '08

The trunk regression tests are showing a large number of failures for Parameter and Serialization (and several other libraries that use them). These seem to have appeared as a result of some recent type_traits changes. -parameter- The parameter tests are failing with: ..\boost/parameter/aux_/tagged_argument.hpp(173) : error C2504: 'is_convertible' : base class undefined This can be fixed by adding # include <boost/type_traits/is_convertible.hpp> to tagged_argument.hpp -serialization- The serialization tests are failing with: ..\boost/serialization/is_abstract.hpp(43) : warning C4005: 'BOOST_IS_ABSTRACT' : macro redefinition ..\boost/type_traits/intrinsics.hpp(99) : see previous definition of 'BOOST_IS_ABSTRACT' Due to a BOOST_IS_ABSTRACT that was just added to type_traits conflicting with one that already existed in serializtion. Thanks, Richard Webb

4 4

Help required in asynchronous I/O
by Suresh 02 May '08

02 May '08

Hello, I am working on incorporating async I/O in postgres. I had the foll. doubts in async operation. If I do for(i=0;i<MAX;i++){ bzero( (char *)&aiocb1[i], sizeof(struct aiocb) ); aiocb1[i].aio_fildes = fd; aiocb1[i].aio_nbytes = BUF_SIZE; aiocb1[i].aio_buf = malloc(BUF_SIZE+1); aiocb1[i].aio_offset = off+100; //next_offset; aiocb1[i].aio_lio_opcode = LIO_READ; sigemptyset(&sig_act[i].sa_mask); sig_act[i].sa_flags = SA_SIGINFO; sig_act[i].sa_sigaction = aio_completion_handler; aiocb1[i].aio_sigevent.sigev_notify = SIGEV_SIGNAL; aiocb1[i].aio_sigevent.sigev_signo = SIGIO; aiocb1[i].aio_sigevent.sigev_value.sival_ptr = &aiocb1[i]; ret = sigaction( SIGIO, &sig_act[i], NULL ); off+=100; list[i]=&aiocb1[i]; } void aio_completion_handler( int signo, siginfo_t *info, void *context ){ int i=0,ret; if (info->si_signo == SIGIO) { ..... } } It calls the aio_completion handler once when all the i/o requests are completed and we check the signal and proceed. The same method if I use for callback using threads, then it calls the aio_completion handler MAX times instead of calling it only once. aiocb1[i].aio_sigevent.sigev_notify = SIGEV_THREAD; aiocb1[i].aio_sigevent._sigev_un._sigev_thread._function = aio_completion_handler; .... void aio_completion_handler( sigval_t sigval ) { ... } How do I do something similar to signal mechanism whereing a check if the signal is mine and then only proceed. In short, how do I guarantee that aio_completion_handler is called only once in case of list AIO. Please help me out of this. Thanks and regards, Suresh --------------------------------- Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. --------------------------------- Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.

1 0

throw_exception rev. 44954 -> g++ warnings
by Ralf W. Grosse-Kunstleve 02 May '08

02 May '08

SVN rev. 44954 from yesterday introduces new g++ warnings (several g++ versions, incl. 4.1.2 Fedora 8). See below. Would it make sense to add the virtual destructors g++ want's to have? Ralf include_te.cpp: #include <boost/throw_exception.hpp> % svn update -r44953 Updated to revision 44953. % g++ -Wall -c -I$hot/boost include_te.cpp % svn update -r44954 U boost/throw_exception.hpp Updated to revision 44954. % g++ -Wall -c -I$hot/boost include_te.cpp boost/exception/detail/counted_base.hpp:17: warning: 'class boost::exception_detail::counted_base' has virtual functions but non-virtual destructor boost/exception/detail/cloning_base.hpp:19: warning: 'class boost::exception_detail::cloning_base' has virtual functions but non-virtual destructor boost/exception/enable_current_exception.hpp:24: warning: 'class boost::exception_detail::clone_base' has virtual functions but non-virtual destructor boost/exception/exception.hpp:27: warning: 'struct boost::exception_detail::error_info_container' has virtual functions but non-virtual destructor

2 1

[exception] exception_ptr for GCC
by Sebastian Redl 01 May '08

01 May '08

Hi, My quest for a general exception_ptr for GCC has reached its end, in the sense of, "I can't make it any better without modifying GCC." My current code is extremely fragile regarding code generation (it depends on the layout of the functions in the file) and there is one circumstance under which it leaks the exception object, but in general it works quite well. The header file, source file, and a file containing test cases are attached. Even though this can obviously not be used in production code, it's an interesting study of absurd things you can do in order to get around the limitations of a fixed ABI. Sebastian

2 2

[Concept Check] - Extending the BCCL with AllocatorConcept
by Michael Fawcett 01 May '08

01 May '08

I recently had the need to code up an AllocatorConcept, and it occurred to me that it might fit well within the BCCL. I noticed that Intrusive also had an allocator concept and wondered if other libraries did too (perhaps under a different name). Would this be of interest as an extension to BCCL? A quick Google search of boost.org shows that dynamic_bitset, multi_index, function, regex, shared_ptr (and I'm sure more) all have Allocator template parameters where it might make sense. For very generic concepts such as Allocator, do they belong in BCCL rather than coded in each library? I've pasted the code below. --Michael Fawcett -- code -- namespace boost { template <typename T> struct AllocatorConcept { typedef typename T::const_pointer const_pointer; typedef typename T::const_reference const_reference; typedef typename T::difference_type difference_type; typedef typename T::pointer pointer; typedef typename T::reference reference; typedef typename T::size_type size_type; typedef typename T::value_type value_type; // TODO: Do we need to do more here, e.g. char_allocator_type::rebind<value_type>::other == T? typedef typename T::template rebind<char>::other char_allocator_type; BOOST_CLASS_REQUIRE(T, boost, DefaultConstructibleConcept); BOOST_CLASS_REQUIRE(T, boost, CopyConstructibleConcept); BOOST_CLASS_REQUIRE(T, boost, EqualityComparableConcept); void constraints() { pointer p = 0; reference ref = *p; const_reference cref = *p; p = value.address(ref); const_pointer cp = value.address(cref); p = value.allocate(1); p = value.allocate(1, 0); value.construct(p, *p); value.deallocate(p, 1); value.destroy(p); size_type s = value.max_size(); } private: T value; }; }

2 3

Build Issue in Sandbox
by Jared McIntyre 01 May '08

01 May '08

Were trying to get the explore library tests in the sandbox to build against 1.35, and are having issues in MSVC not being able to find libboost_unit_test_framework-vc80-mt-gd-1_35.lib at link time. Everything is fine in 1.35. I've tried building both as bjam --v2 and bjam --v2 -a --build-type=complete. We're trying to get this ready for BoostCon, so if anyone has any ideas, I'd really appreciate the help. Thanks, Jared This is the jamfile # Boost.Explore Library # Copyright Jared McIntyre 2007. Use, modification and # distribution is subject to the Boost Software License, Version # 1.0. (See accompanying file LICENSE_1_0.txt or copy at # http://www.boost.org/LICENSE_1_0.txt) # For more information, see http://www.boost.org # bring in rules for testing import testing ; project : source-location . : requirements ; { test-suite explore_stream : [ run is_assoc_iter.cpp ] [ run simple_types.cpp ] [ run c_array.cpp ] [ run user_defined_container.cpp ] [ run std_vector.cpp ] [ run std_deque.cpp ] [ run std_list.cpp ] [ run std_map.cpp ] [ run std_set.cpp ] [ run std_pair.cpp ] [ run boost_array.cpp ] [ run boost_tuple.cpp ] [ run boost_variant.cpp ] [ run boost_range.cpp ] [ run custom_format_simple.cpp ] [ run html_table_output.cpp ] [ run multi_dim_test.cpp ] [ run columnated.cpp ] ; }

1 0

Boost.Python: Build and Install with Python 2.4 and 2.5?
by Steve M. Robbins 01 May '08

01 May '08

Hi, I'm part of the Debian Boost packaging team, seeking some guidance on how to build and install Boost.Python so that it is usable with all Python versions shipped in Debian. Debian currently ships Python 2.4 and 2.5. When reading the following, keep in mind that Boost.Python is not a Python extension but, rather, a library that eases writing an extension in C++. So it is necessary that the compiled libraries be visible to be linked with user-written C++ code. One idea is to use a user-config.jam file containing using python : 2.4 : /usr ; using python : 2.5 : /usr ; Then run jam twice bjam variant= ... bjam variant= ... python python=2.5 This produces pairs of library files such as bin.v2/.../link-static/libboost_python-gcc42-1_34_1.a bin.v2/.../link-static/python-2.5/libboost_python-gcc42-1_34_1.a (and similar pairs for shared libraries and all other variants). The key item to note is that the two files have the same name. The python version, unlike the GCC version, is not embedded in the library name. So these files cannot both be installed into /usr/lib. The question, then, is how to distinguish them once installed? Should we: 1. Rename the resulting libraries to decorate them with the python version in addition to the gcc version? This could generate libboost_python-py24-gcc42-1_34_1.a libboost_python-py25-gcc42-1_34_1.a 2. Similar to above, but use bjam's --buildid option? This has the drawback that the build ID shows up differently than the GCC version decoration, e.g. libboost_python-gcc42-1_34_1-py24.a libboost_python-gcc42-1_34_1-py25.a 3. Put the libraries in different subdirectories, e.g. /usr/lib/python2.4/libboost_python-gcc42-1_34_1.a /usr/lib/python2.5/libboost_python-gcc42-1_34_1.a 4. Put the default version directly in /usr/lib and the others in subdirectories, e.g. /usr/lib/libboost_python-gcc42-1_34_1.a /usr/lib/python2.5/libboost_python-gcc42-1_34_1.a The drawback to all these approaches is that client code has to be adjusted to build on Debian. Linking against Boost (for non-bjam projects) is already hard enough with the decorated library names that I fear making the situation worse. The attraction of #4 is that at least the variants for the default python version are found in a natural manner. This has some appeal to me, personally, but I worry that it is too easy to build an extension to python 2.5 and link in the wrong Boost.Python library. In contrast, the other options have the advantage that it forces the user to declare which version of Python is being used. I'd appreciate your thoughts. Have I overlooked a better solution? What are the other packagers of Boost.Python doing? In principle, it would be nice to have the Boost libraries named the same across distributions. Thanks, -Steve

3 5

Re: [boost] Release 1_35_0_RC2: Boost Python hello tutorial
by Johannes Brunen 01 May '08

01 May '08

Beman Dawes wrote: > In the meantime, have you tried a more modern version of VC++? > The free download of VC++ 2008 Express Edition, for example. Ok, I just tried the same procedure with the VC++ 2005 (i.e. 8.0) compiler with the same result. It does not generate the .pyd files, neither in release mode nor in debug mode. Thanks, for adding it to the issus list Best, Johannes

8 15

Please let's avoid sending mails containing HTML parts
by Jens Seidel 01 May '08

01 May '08

Hi, I noticed that Boost's mailing list rules don't forbid sending useless HTML attachments which is not a good idea for discussion lists. Please let's extent http://www.boost.org/more/discussion_policy.htm to avoid this. Advantages: * Smaller messages * Faster opening (difference between text and HTML parts can be factor 10 and more!) * More consistent display formatting (no differences between text and HTML can occur without HTML) * There is absolutely no need to send HTML stuff. If one really depends on pictures or similar stuff the person should use normal attachments or even better upload the data to a remote site Omitting HTML parts is just a common rule for many lists, strange that Boost didn't enforce it yet. Jens

5 4