- Boost - lists.boost.org

[trac] no Ticket component for Boost.Range
by Ronald Garcia 06 Aug '07

06 Aug '07

Howdy, Not sure who the right person is to point this to, but I have created a new ticket for Boost.Range, yet there is no "Component" listing for that library. I have left the Component as "None" Thanks, ron

3 2

Timeseries review
by Sanjeev Mohindra 06 Aug '07

06 Aug '07

Just doing through it now. It would be very useful. Some quick questions and comments based on very brief perusal. 1. How does one handle missing (time-series) values in this framework? So, for example, I have set up my time-series with a certain discretization and then at some point(s) along the series, I receive no data, what would be an elegant way of dealing with this situation in the library. We would also need a policy to ignore or interpolate the values of missing data. 2. I like the resampling support (Coarse_grain and Fine_grain) 3. Did I say, the library would be extremely useful. -- Sanjeev

2 1

[range] documentation questions
by Ronald Garcia 06 Aug '07

06 Aug '07

In the synopsis of iterator_range on the page: libs/range/doc/utility_class.html what are the following metafunctions: const_iterator_of iterator_of I do not see them documented anywhere. There is also a typo in the synopsis of subrange: sub_range( const Range2& r ); should be sub_range( const ForwardRange2& r );

2 2

Re: [boost] [svn] empty log messages
by Phil Endecott 06 Aug '07

06 Aug '07

Daniel Wallin wrote: > The timeline shows a couple of changesets with empty log messages: > Could we change the pre-commit hook to disallow this? Just in case anyone's not aware of this, svn will let you change the commit messages for old commits. The command is something like svn propset svn:log --revprop -r 12345 "Frob the foobar" . By default, however, this is disabled by the pre-revprop-change hook. This chould be set up so that e.g. only the person responsible for a commit could subsequently change its log message. Regards, Phil.

1 0

Trac bugs - by assignee
by Marshall Clow 06 Aug '07

06 Aug '07

[ Back from vacation; 329 open tickets today ] 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> 24 grafik 24 doug_gregor 22 johnmaddock 21 bemandawes 20 None 17 az_sw_dude 15 jsiek 14 vladimir_prus 14 rogeeff 14 ramey 12 pdimov 12 dave 11 turkanis 11 agurtovoy 7 samuel_k 6 shammah 6 nesotto 6 jbandela 6 anthonyw 5 witt 5 <Blank> 4 urzuga 4 nobody 4 mark_rodgers 4 fcacciola 4 djowel 4 dgregor 4 danielw 3 jmaurer 3 ebf 3 dlwalker 2 hubert_holin 2 garcia 2 eric_niebler 2 danieljames 2 alnsn 1 t_schwinger 1 speedsnail 1 nmusatti 1 mistevens 1 kevlin 1 hkaiser 1 chris_kohlhoff 1 asutton 1 aaron_windsor None 1144 GIL 2.1 PNG IO fix for endianness problem with bit_depth == 16. None 1135 bjam crashes None 1130 GCC -wundef warnings None 1116 disable some warnings in msvc build None 1101 [MPI] Const-incorrectness in boost::mpi::status None 1094 Finding the correct library to link (feature request for pkg-config support)h None 1090 scoped_file class that deletes file at end of scope None 1089 missing boost::serialization::make_nvp in pointer container library None 1080 boost::interprocess win32 global file mapping issue None 1079 boost-1.34.0 fails to compile. concept checks not satisfied. None 1068 Mersenne twister disables streaming for Visual C++ None 1059 random_on_sphere can be made 10 times faster! None 1033 iostreams::restrict doesn't work on an iostreams::file_source None 1003 [iostreams] copy-paste error in typedefs for wchar multichar_filters None 1002 [iostreams] close_impl<closable_tag> does not comply with spec None 991 [pool] None 986 Problem building Python modules on boost 1.34.0 None 982 x64 documentation for windows None 980 boost.format vc8/win32 compilation warning None 960 [random] lognormal_distribution problem <Blank> 1112 reference_wrapper<T> should convert to reference_wrapper<U> when T& is convertible to U& <Blank> 1093 Mandatory source files shouldn't require_ or give the impression to require_ the Boost Build system <Blank> 1070 [iostreams]boost\iostreams\copy.hpp line80 copy_impl <Blank> 1027 [ptr_container] optional serialization support <Blank> 1011 amd64: #error Boost.Numeric.Interval: Please specify rounding control mechanism. aaron_windsor 778 top-level configure is broken agurtovoy 1122 Update regression.py to use SVN repo. agurtovoy 1099 unable to iterate through a "non-explicitly-declared" mpl::set agurtovoy 1051 MPL header ordering triggers bug agurtovoy 1049 Getting mpl/has_xxx.hpp to compile on AIX agurtovoy 1001 gcc 4.1.2 segfaults on mpl/test/apply.cpp agurtovoy 861 Detect nested template members with has_template_xxx agurtovoy 816 duplicat initial members -> erase_key postcond. fail agurtovoy 761 [mpl] evc4 port agurtovoy 640 documentation mistake agurtovoy 637 Adjusts mpl::pair concept to be compatible with STL pairs agurtovoy 588 mpl::remove compile error with gcc 4.1.0 alnsn 839 lexical_cast - local variable shadow patch alnsn 754 boost::any - typeid comparison across shared boundaries anthonyw 1053 Error using boost::mutex and C++/CLI anthonyw 659 provide an abstract "Task" type based on Boost.Threads anthonyw 881 errors when build with Apache stdcxx anthonyw 876 xtime documentation incomplete anthonyw 868 [thread] thread_specific_ptr::element_type ? anthonyw 802 [thread] MSVS: Allow use of thread headers with /Za asutton 693 Add clique detection algorithms DFMax_ Bron-Kerbosch az_sw_dude 1117 [asio][0.3.8 rc3]check BOOST_ASIO_HAS_IOCP before assumed _WIN32_WINNT was defined az_sw_dude 1098 Urgent libboost-date-time1.33.1 : bugs on ia64 ? az_sw_dude 1078 from_iso_string cannot read the output from to_iso_string az_sw_dude 1028 typo in boost header: date_time/time_defs.hpp az_sw_dude 224 Extensions to std::string: compareIgnoreCase()_ trim()_ ... az_sw_dude 187 locale az_sw_dude 17 Socket wrapper class az_sw_dude 890 date_time library supports only the current dst rule az_sw_dude 889 Insane Dependencies az_sw_dude 827 Unused variable in format date parser az_sw_dude 642 operator<< for gregorian::date_duration not found az_sw_dude 614 new timezone db file for #1471723 - 2007 DST support az_sw_dude 605 support new 2007 DST rules for timezone db az_sw_dude 604 from_ftime incorrectly processes FILETIME filled with zeros az_sw_dude 596 make timezone csv file C/C++ compatible az_sw_dude 316 date_time type conversion warning az_sw_dude 287 wrong usage of ios_base::narrow bemandawes 1092 [Boost.Filesystem] Program can't run under Win 98 bemandawes 1073 operations.cpp_ dummy_first_name lifetime bemandawes 1061 boost::filesystem::basic_recursive_directory_iterator fails on empty directories. bemandawes 1014 rename throws an exception that is not documented bemandawes 995 'multiply defined symbols' when including <boost/filesystem.hpp> in different source files bemandawes 897 exists() throws exeption on existing but locked file on wind bemandawes 842 typo in auto_unit_test.hpp Revision 1.17 bemandawes 824 BOOST_IOSTREAMS_HAS_LSEEK64 on Mac OS X bemandawes 823 Seekable file_descriptor_source /sink? bemandawes 800 [filesystem] chdir() bemandawes 752 directory_iterator doesn't work with catch bemandawes 680 significantly different timer class behaviour on Win and Lin bemandawes 662 [filesystem] portable_posix_name() may fail on premain call bemandawes 621 filesystem::path as a template bemandawes 607 Log level names wrong in documentation bemandawes 600 VC8 can't find windows.h even though environment is correct! bemandawes 590 mkstemp bemandawes 559 linker error mingw 3.4.5 bemandawes 366 handle double '/' in the boost::filesystem bemandawes 294 unicode support in boost::filesystem bemandawes 222 Code analysis_ flaw detection_ debugging chris_kohlhoff 710 asio redefine FD_SETSIZE macro danieljames 1095 GCC warnings with -Wsign-promo danieljames 1064 problem on platforms with no errno.h header file danielw 1097 keyword.hpp generates many warnings C4180: qualifier applied to function type has no meaning; ignored danielw 1054 Parameter takes an "infinite" amount of time to compile with the Intel compiler. danielw 1044 Argument pack inaccessable in a functions return type danielw 863 [parameter] fix operator|| for lazy binding dave 1096 Tutorial needs updating for BBv2 dave 1085 Python rules for compiling in Mac OS X dave 1066 Patch to make Boost.Python compile on SunCC dave 1020 Boost.Iterator proposal to add is_constant_iterator dave 1019 iterator_facade::pointer should be the return type of operator-> (DR 445) dave 1010 linking boost.python on freebsd dave 918 __doc__ strings dave 916 BPL Support for Python Callable Objects dave 910 gcc strict-aliasing problems with python dave 903 inconsistent usage of function pointer typedefs dave 865 Use of C++0x keyword as identifier dave 857 add shared_ptr< const T> support dgregor 1140 boost::iostreams linked_streambuf bug dgregor 1139 [iostreams] Regex filter segfaults when zero matches found dgregor 1124 ./configure failed on cygwin dgregor 556 Bundled graph properties djowel 664 crash in boost::spirit::parse djowel 543 Embedded python won't compile djowel 314 spirit insert_key_actor.hpp djowel 241 Miss " = ParserT()" dlwalker 766 "Bug" in comment (x2) dlwalker 653 [integer] add support for integers longer than long dlwalker 613 boost/crc.hpp uses non-standard conforming syntax doug_gregor 1087 Mismatch between BBv2 and bjam toolsets in configure script. doug_gregor 1076 compile error: disconnecting struct with operator()() doesn't work in VS2005 SP1 doug_gregor 1067 Function needs to use pass-by-reference internally doug_gregor 1021 [Graph][reverse_graph] Problem using reverse_graph adapter with an adapted user defined graph doug_gregor 954 boost::dynamic_properties has no copy-constructor doug_gregor 891 Bunch of compilation error reported while using function.hpp doug_gregor 870 boost::graph::graph_utility.hpp is_connected() bad call doug_gregor 862 [utility] Make result_of handle lambda expressions doug_gregor 852 Problem with Boost and GCC 4.1 doug_gregor 829 Implicit graph not implement doug_gregor 746 max flow with lower bounds (capacities) doug_gregor 738 Memory leaks with signal::connect? doug_gregor 736 Const correctness violation doug_gregor 735 Fruchterman-Reingold grid performance can be improved doug_gregor 733 Numbered headers don't work with "preferred" syntax doug_gregor 732 Johnson All-Pairs needs better "no path" information doug_gregor 708 Dijkstra no_init version should not require VertexListGraph doug_gregor 447 reverse_graph and constness of property maps doug_gregor 403 Document copy_component doug_gregor 402 random_vertex/random_edge are unnecessarily inefficient doug_gregor 395 BGL graph types do not support allocators doug_gregor 375 LEDA graph adaptors do not handle hidden nodes properly doug_gregor 373 LEDA graph adaptors for undirected graphs doug_gregor 372 adjacency_matrix should model BidirectionalGraph ebf 993 Variant should use least common multiple of alignments_ rather than maximum ebf 965 [doc] boost::variant tutorial - final example uses v1_v2 should be seq1_seq2 ebf 547 [variant] Compile time checked getter eric_niebler 1119 enable_reference_tracking copy constructor does not call base class version eric_niebler 1071 Request for BOOST_REVERSE_FOREACH and rationale fcacciola 818 No zero-argument in_place() fcacciola 765 optional documentation fcacciola 617 Numeric Conversion Documentation minor bug fcacciola 282 boost::optional<enum> fails with /CLR garcia 1127 multi_array views do not handle negative strides correctly garcia 1045 [multi_array] Need a proper swap operation grafik 1128 boost-buil rule does not overrule BOOST_BUILD_PATH grafik 1088 Docs for template escape feature. grafik 1074 FreeBSD specific patches to boost 1.34.0 grafik 1041 Cygwin requires PATH setting. grafik 1040 boost.devel archive at ActiveState disconnected grafik 1031 AmigaOS fixes for bjam grafik 1023 inspect grafik 989 Boost build does not support building universal binaries on macintosh grafik 714 [jam] HardLink rule on NT platform grafik 94 Better reporting of failed expectation. grafik 93 Testing problems on AIX and OSF grafik 1062 Cygwin install stage fails with combination of patches grafik 977 bjam crashes when compiled with gcc 4.2 grafik 959 linking fails when Boost is compiled with STLport 5.1.* on Linux (names mismatch) grafik 896 <native-wchar_t>off does not work when build with vc-8.0 grafik 798 bjam: always define OSPLAT grafik 721 Generated files "@()" don't work in regular expressions. grafik 683 libraries won't build grafik 616 Boost Jam_ and non english directorys grafik 552 Building universal binary on MacOSX grafik 546 boost.build needs fixes for HP/UX grafik 497 Unable to build boost with Dinkumware STL version 4.02 grafik 481 Linker Problems with VC .NET 2003 / STLPort / Boost grafik 431 boost jam problem with parallel builds hkaiser 1077 Spirit integer parser does not always detect integer overflow hubert_holin 647 octonion documentation bug hubert_holin 162 Cannot compile octonion_test.cpp because of bug in sinc.hpp jbandela 665 bug in char_separator jbandela 501 token_iterator::at_end() result is inversed jbandela 306 Visual C++ "Language Extensions" support jbandela 283 Compiler error for tokenizer on Solaris jbandela 279 SLOOOWW tokenizer compilation on VC++6.0 jbandela 259 Problem compiling :/ jmaurer 920 Proposed extension to random library jmaurer 819 uniform_int<> with type's maximum availaible range error jmaurer 351 Diff in state of mersenne_twister gen between GCC3.41 & CW9 johnmaddock 1105 Add BOOST_NO_STD_TYPEINFO or inject ::type_info into std johnmaddock 1104 Add BOOST_NO_TYPEID johnmaddock 1103 Add BOOST_NO_IOSFWD johnmaddock 1102 Add BOOST_NO_IOSTREAM johnmaddock 1083 boost_regex 1.34.0 uses ICU library without linking to it johnmaddock 1081 Empty string rejected as perl-style regex johnmaddock 1075 [doc] incorrect comment johnmaddock 1008 Undocumented type traits. johnmaddock 905 Assertion failed in token_iterator.hpp johnmaddock 871 Problem build boost 1.33.1 on Aix 4.3.3 johnmaddock 883 errors when build with Apache stdcxx johnmaddock 812 Crash on RH machine with gcc < 3.4 johnmaddock 775 Warnings on MSVC 2005 johnmaddock 764 [regex] add support for a BOOST_NO_CREGEX mode johnmaddock 679 regex - perl syntax affects what gets matched johnmaddock 633 [config] evc4 port johnmaddock 591 make portable stdint.h from boost code johnmaddock 540 Please add support for Borland C++ Builder 2006 johnmaddock 502 Problem running configure for unsupported platform johnmaddock 492 Adding boost::is_complex to type_traits.hpp johnmaddock 360 Regex johnmaddock 315 Implement operator[] for Tokenizer jsiek 900 graphml reader namespace handling is broken jsiek 875 No iterator based constructor for adjacency_matrix jsiek 815 remove_edge core dumps on self-circle jsiek 813 concept_check.hpp unused variable warning jsiek 694 Add Maximum Common Subgraph (MCS) algorithm jsiek 636 strange compiling problem for transitive_closure jsiek 580 Max Flow Algorithm jsiek 575 Calling subgraph::global_to_local on a root graph jsiek 541 [concept_check.hpp] remove unused variable warning in msvc jsiek 416 Spelling of Edmonds-Karp-Algorithm jsiek 193 Check ordering for mutexes jsiek 182 Support aspect-orientation jsiek 116 creating my own properties jsiek 100 more use of the concept "allocator" jsiek 69 Boost with Dinkumware C++ Library !? kevlin 913 Specialization of lexical_cast mark_rodgers 821 allow_unregistered improvement mark_rodgers 558 add database library? mark_rodgers 87 function to get the size of a array mark_rodgers 30 parser mistevens 688 ublas: bug in mapped_vector_of_mapped_vector nesotto 807 boost::assignment documentation: mathematical "typo" nesotto 730 The ptr_map iterator cannot be dereference to value type nesotto 723 local_time_facet error in VS2005 Win2003 nesotto 624 bug in boost::range_detail nesotto 518 [Boost.Range]boost::const_begin calls non-qualified 'begin' nesotto 471 boost.range and "const char[]". nmusatti 285 Borland compiler error with Pool_ boost::pool_allocator nobody 930 iostream and zlib nobody 922 Lexical cast and wide characters nobody 884 [iostreams] workaround for the boost + stdcxx on MSVC 7.1 nobody 795 [ublas] vector::back() pdimov 1114 Request for shared_ptr::type and shared_ptr::pointer pdimov 1113 shared_array<T> should convert to shared_array<T const> pdimov 1111 boost::bind objects should expose function_type and list_type pdimov 1110 Add a release method to scoped_array pdimov 1109 intrusive_ptr needs a helper base class pdimov 1108 shared_ptr does not compile under g++ with -fno-rtti pdimov 1107 Add weak_use_count to weak_ptr as a debugging aid pdimov 1106 shared_ptr<T> should not convert to shared_ptr<U> when T* doesn't convert to U* pdimov 997 error in boost::bind doc pdimov 810 support for weak_ptr binding pdimov 445 Can't delete automatically in circularly included object. pdimov 398 Support for embedded VC++ 4.0 ramey 1143 Archive headers appear to be missing multiple(?) include files ramey 1142 boost/serialization/optional doesn't include necessary header ramey 1141 Dangerious operator<< for wostream ramey 1137 Virtual destructor is missing ramey 1121 xml_archive_exception is missing seperate header file_ and documentation mismatch ramey 1086 Serialization of weak_ptr produces invalid XML ramey 1038 "<" and ">" should be excaped in xml_oarchive ramey 1036 assert failure in oserializer.hpp:418 ramey 969 basic_binary_iprimitive::load_binary bug ramey 968 xml_grammar - incorrect define char ramey 961 boost::basic_binary_oprimitive not instantiated correctly ramey 874 Ability to partially specialize implementation_level ramey 757 xml serialization fails when using namespace ramey 878 error C2039: 'mbstate_t' : is not a member of 'std' rogeeff 1136 Let BOOST_CHECK_EQUAL support std::wstring rogeeff 1060 no example sources in online docs for Boost::Test rogeeff 1050 BOOST_CHECK_CLOSE_FRACTION documentation missing rogeeff 1032 typo in Boost.Test documentation rogeeff 1030 execution_monitor.ipp #warning directive breaks compilation on MSVC 8.0 rogeeff 999 prg_exec_fail3 fails on release variant rogeeff 998 prg_exec_fail2 fail on ppc rogeeff 962 Missing links in Test library documentation rogeeff 956 Doc error in test examples. rogeeff 893 grammatical error in error message rogeeff 847 [Test Library] How to init/free a singleton rogeeff 762 [test] evc4 issue with SEH support rogeeff 747 failing on 6 targets in MacOS X rogeeff 645 [test] no eh exception handling functions on evc4 samuel_k 859 boost::format ignores a user defined locale samuel_k 849 boost::format and operator priority rule samuel_k 713 Boost.Format doesn't work on MSVC with /vd2 compiler option samuel_k 704 format zero length string msvc-8 samuel_k 585 64 bit compile warning/error for boost::format samuel_k 570 boost::format parse method doesn't work samuel_k 493 format: assert when parsing invalid pattern shammah 840 pool allocator - local variable shadow patch shammah 836 warning using pool.hpp shammah 386 boost::pool_allocator breaks with vector of vectors shammah 290 perfomance: memory cleanup for pool takes too long shammah 284 pool::purge_memory() does not reset next_size shammah 88 ct_gcd_lcm.hpp compilation error speedsnail 1138 Problems with TSS and static thread library t_schwinger 1100 Building boost.function_types fails cvs rev-1.1_ no chdir command in bash turkanis 869 [iostreams] patch for building by BBv2 turkanis 856 iostreams file_descriptor::write fails under Win32 turkanis 822 Incorrect usage of bad_write()_ bad_seek() etc. turkanis 817 Performance problem in iostreams turkanis 791 iostreams::tee_filter is for output only turkanis 786 bug in iostreams/copy.hpp line 81 turkanis 699 Changing size of memory-mapped file on Windows turkanis 586 iostreams // file_descriptor::seek BUG on files > 4 GB turkanis 579 boost.iostreams file_descriptor and sharing turkanis 525 problem with boost::iostreams when compiled with Visual C++ turkanis 484 Boost.Iostreams and newline translation urzuga 864 [lambda][utility] Make lambda support result<> urzuga 781 Lambda: (_1 + "y")(string("x")) Doesn't Compile urzuga 574 [boost::lambda] Compile error with libstdc++ debug mode urzuga 426 lambda vs pure virtual functions vladimir_prus 1132 program_options documentation error. vladimir_prus 1131 program_options patch: optional argument support (gnu getopt_long style) vladimir_prus 1129 Standalone doc_ outdated path from homepage vladimir_prus 1125 parse_config_file should be mentioned in the How To vladimir_prus 1058 Cygwin libraries & GNU libtool vladimir_prus 985 Free features don't work when building boost vladimir_prus 879 Building Boost with Apache C++ Standard Library (STDCXX) vladimir_prus 853 path with spaces not always handled vladimir_prus 850 program_options strips off escaped quotes in some situations vladimir_prus 808 [program_options] parse_config_file documentation bug vladimir_prus 689 [program_options] Endless loop with long default arguments vladimir_prus 674 find-library for boost decorated names vladimir_prus 644 Boost.Build v2 build script help for evc4 vladimir_prus 469 multitoken broken witt 1046 Boost.Python quickstart instructions mention nonexistent target witt 973 zip_iterator has value_type == reference witt 957 The "Getting Started" page does not mention the stdlib option witt 834 Homepage regression links witt 145 filter iterator adaptor should be able to be bidirectional -- -- 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

boost::function question
by Balasubramanyam, Shivakumar 06 Aug '07

06 Aug '07

Hi, I would be like to know how you can bind a member function that has a overloaded arguments. For example. Class X; Class Y; Class A{ Line1: Void Func(X x); Line2: Func(Y y); } Any ideas? Thanks, Shiva

2 1

Re: [boost] Release Tools Analysis Part I: Build systems
by David Abrahams 06 Aug '07

06 Aug '07

on Sun Aug 05 2007, Stefan Seefeld <seefeld-AT-sympatico.ca> wrote: > FWIW, I submitted a patch to SCons providing a python extension > module around ucpp (http://pornin.nerim.net/ucpp/) to provide a > 'more accurate' C/C++ dependency scanner, long before wave was around. Does anyone know if ucpp is actually conforming? Until very recently, most preprocessors were badly broken (and maybe most still are). If it conforms, it would be interesting to benchmark it against Wave. > Steven refused that, believing that it could (and should) all be done > in pure python. Well, with a great deal of due respect to Steven, he's wrong. Sure it /can/ be done in pure python, but /should/ it be? Before we had insane C++ template metaprograms, the cost of preprocessing and lexing typically swamped that of any other C/C++ compilation phase, just because they had to deal with more data (individual characters). And now we have insane preprocessor metaprograms, so things have not gotten any easier on the C/C++ preprocessor. > That was many years ago, and the situation hasn't substantially > changed since then. Sounds familiar. -- Dave Abrahams Boost Consulting http://www.boost-consulting.com The Astoria Seminar ==> http://www.astoriaseminar.com

4 9

Organization idea: separate libraries in our SVN
by Daryle Walker 06 Aug '07

06 Aug '07

[I thought I wrote a message similar to this a few years ago, but I can't seem to find it on GMane. Anyway, this is a good time to re-introduce it since Subversion allows directory manipulations.] The current layout of the Boost material in our SCM system is the same as the final archives. That does not necessarily have to be the case. Since we put emphasis on distinct libraries within Boost as far as maintenance is concerned, maybe we should enforce in the SCM layout. You know how, when we look at a potential library, the library is in an archived folder with sub-folders mirroring the files' places in the final layout. The trial library would have its own root "boost" and "libs" (and any other) sub-directories. I suggest that all the current libraries be set up like that, in a common directory holding all the libraries. This common directory would be the trunk. At release time, the contents of each library's directory are merged into a release directory. If only one library directory has a particular file object, it's copied as-is. If multiple libraries have a commonly-named file object, we have an error if at least one of them is a file. Otherwise, the commonly-named directories are merged using this algorithm recursively. (A particular leaf file should only be part of one library.) So the new trunk would be like: * trunk/ ** General/ ** any/ ... ** crc/ ... ** filesystem/ ... ** math-quaterion/ ** math-common_factor/ ... ** quickbook/ ... ** utility-general/ ** utility-enable_if/ ... ** wave/ ** wave-tool/ ... Note that the tools get parallel library directories. The "General" folder holds our license, logos, and any other non-library common files. Libraries of the same category don't have to have distinctive namespaces (and sub-folders of the boost/ header directory); they can be merged in the final product, but maintained separately in the SCM system. (The existing I/O, math, and numeric namespaces/directories are sort of like this, but now we can refine them further, and do stuff like put all the Boost container classes under one sub-namespace/directory.) While the final users get a merged archive, Boost developers would have to include each library's header separately in their compiler options. This could be useful because it will tell us about each library's dependencies on other Boost libraries. I think Subversion has some sort of symbolic-file-link support. Maybe with that, we could create a directory parallel to the trunk that represents an already merged archive. (It would have to be read-only, of course.) It could be updated with a commit script watching the trunk directory. * master-level/ ** trunk/ ** synthetic-archive/ <- read-only; maybe at separate website ** branches/ ** tags/ Something I like about this system is that it lets me know exactly how many libraries we have. (There's so many and it's hard to keep track sometimes.) Furthermore, now that libraries can be safely enumerated enables all sorts of automatic processing. Using SVN properties on each library's folders, and various sub-objects, would enhance said processing. (I think that properties and their changes generally can be version-controlled.) We could have the commit script make sure that the appropriate file objects have the properties we need. * The master list of libraries can be script-generated. Descriptions of each library and their original authors can be stored as SVN properties in each library's folder. * The current maintainers for each library can be stored as an SVN property. A regression suite that access SVN can then send notifications to the right people. (A master list of maintainers can also be generated for the final archive.) * There can be a property listing which sibling libraries a particular library (directly) depends on. This can be used by a script to isolate one library for extraction and take all it needs for the ride. An extraction can be in my separate library directories form or in a fused archive form. Furthermore, when actually built, you'll discover any missing sibling library dependencies. * Did you know that you can mix-and-match various revisions of items in the same directory? Exploiting this could reduce the need of branching in order to isolate breaking changes. Let's say that we start out at revision r25. The Filesystem library is changed and checked-in at r30. All the other libraries stay at r25 until an explicit update bumps everything to r30. (Subversion's commits do _not_ sneak in an update to uninvolved file objects.) Unknowingly, r27 introduced a bug in the CRC library which breaks Filesystem. The Filesystem maintainer could temporarily lock his/her copy of the CRC library folder to r26 until the bug is fixed! Taken to the extreme, the release manager can check out the copy of the trunk's HEAD, back-step any libraries as necessary to their individual last-known-good(-enough) revision, and then run the merge script for the release's archive. * For each library's documentation directory, the directory could have a property describing the primary file. Each documentation file could have a property describing build directions, if needed. * For each library's testing directory, each test file could have a property describing which kind of test (compile, compile-fail, run, run-fail, etc.) it is. Jamfiles don't necessarily have to be included; they could be synthesized from the properties while the merge script builds an archive. And if we move to a different build system than Jam, then the properties could be used for the new system. * For the mandatory source files, a property could be added for distinct execution closures. As far as I know, this property wouldn't be needed except for three files in Boost.Test. Those files each include a "main" function, and so can't be mixed with each other or all other mandatory source. Each one of those files could have a distinct execution closure tag, which puts it in a separate "src" subdirectory, while all the other mandatory source files leave that property blank and all go into a main "src" subdirectory when merged. (I know we don't keep a root-level "src" directory; but with SCM separation of libraries and a merge script, we can!) Any special compilation directions could be placed in a property to be transfered to a Jamfile (or successor) for our build system. (Obviously this isn't 100% recommended since a user could use his/her own IDE to compile a source file and miss the property's directions.) There is a _one-time_ cost to separate each library/tool from the existing merged archive to distinct directories. That might take a while, but advantages of a separated system should be worth it. (It can be done in piecemeal; keep everything in the "General" directory and separate the libraries/tools out one at a time. We should probably do the leaf libraries [0 sibling dependencies] first. Actually, we should start with Boost.Config; it should have low dependencies, but a lot of other libraries depend on it.) I've heard that Windows, when moving the contents of one directory into another, will (recursively?) merge the contents of commonly-named directories. If that's accurate, then a Windows user could temporarily be a release manager until the merge script is made. I don't really know how to script, but hopefully a merge would be simple enough to write that the Windows-user workaround wouldn't be needed. (Macs use overwrite semantics, being consistent in not distinguishing between file objects based on the source's and destination's is-directory flags.) I know that there's a lot of automation. But, if it's possible to do this plan, we'll be working smarter, not harder, for maintenance and releases. -- Daryle Walker Mac, Internet, and Video Game Junkie darylew AT hotmail DOT com

1 0

SVN commit and inspection checks?
by John Maddock 05 Aug '07

05 Aug '07

Just wondering, but can we set up the SVN commit script to verify the file with our inspect program before a commit is allowed? No doubt folks will be greatly annoyed by this at first, but at least we should gradually get those inspection-failures fixed that way :-) John.

6 5

new proposal: boost-config
by Domenico Andreoli 05 Aug '07

05 Aug '07

Hi, Suppose two systems, a Fedora based on gcc 4.1 and a Debian based on gcc 4.2, both sporting Boost 1.35.0 built with --layout=system, for simplicity. Now Joe User writes his app on the Fedora system and links Boost.DateTime using the familiar -lboost_date_time switch. He builds the app and tries it on both his Fedora system and the friend's Debian one. What is going to happen? BTW, the user is a free software developer and his app is going to be ported also to other Microsoft, UNIX and popular embedded operating systems, where Boost has been built mixing --layout=system and --layout=versioned. Now he faces the problem of linking to the Boost library of interest. How he is supposed to solve the problem? This is a new summary of the binary and source portability problems that current build system is inflicting on the Boost libraries. My proposal is: 1) dump the --layout= thing, versioned/decorated sonames are always used 2) provide symlinks like the following, when appropriate: /usr/lib/libboost_date_time-gcc42-1_34_1.so -> libboost_date_time-gcc42-1_34_1.so.1.34.1 /usr/lib/libboost_date_time-gcc42-d-1_34_1.so -> libboost_date_time-gcc42-d-1_34_1.so.1.34.1 /usr/lib/libboost_date_time-gcc42-mt-1_34_1.so -> libboost_date_time-gcc42-mt-1_34_1.so.1.34.1 /usr/lib/libboost_date_time-gcc42-mt-d-1_34_1.so -> libboost_date_time-gcc42-mt-d-1_34_1.so.1.34.1 3) provide also these symlinks, if desired: /usr/lib/libboost_date_time.so -> libboost_date_time-gcc42-1_34_1.so /usr/lib/libboost_date_time-d.so -> libboost_date_time-gcc42-d-1_34_1.so /usr/lib/libboost_date_time-mt.so -> libboost_date_time-gcc42-mt-1_34_1.so /usr/lib/libboost_date_time-mt-d.so -> libboost_date_time-gcc42-mt-d-1_34_1.so 4) add more decorations as required. e.g. Python version to Boost.Python library name. This way multiple Boost.Python libraries, every built with a different Python version, could coexist on the same system. 5) provide a program, say boost-config, that may be invoked to find the right build parameters for a given library, toolset and variant(s). some examples (suppose default compiler is gcc 4.0, the one used to build Boost): $ boost-config --name=DateTime --ldflags -lboost_date_time-gcc40-1_34_1 $ boost-config --name=DateTime --toolset=gcc-4.1 --variant=mt,d --ldflags -lboost_date_time-gcc41-mt-d-1_34_1 $ boost-config --name=Threads --toolset=gcc-4.2 --ldflags -lboost_threads-gcc42-mt-1_34_1 $ boost-config --name=DateTime --toolset=gcc-4.2 --variant=python-2.5 --ldflags Error: unknown variant python-2.5 for the given library $ boost-config --name=Python --variant=python-2.4 --ldflags -lboost_python-gcc40-python24-1_34_1 $ boost-config --name=Python --toolset=gcc-4.2 --variant=python --cxxflags -I/usr/include/python if toolset is omitted, the default system compiler is used, if any (e.g. cc/c++ under linux), otherwise an error is reported. Point 1) is really optional. In case --layout is kept, the subsequent points would be related only to --layout=versioned and --layout=system should be documented as source of any sort of portability issues. Point 2) is required only on UNIX systems where GNU ld is used, it might have not sense with other linkers. Every linker has its own story. Point 3) is applicable only where 2) is and would be handy only when source portability is not an issue, to the user discretion. Big warning about source portability should be placed nearby its documentation. Point 4) would allow packaging Boost.Python on distributions in which multiple versions of Python may be available. Point 5) is the way to the complete source portability, at least across sane systems (read, probably not Windows/MSVC). Note that if Boost is built using a compiler different from the one asked to boost-config, the linker will complain about the inexistent library. It would be easy to make boost-config extract allowed parameter combinations from an XML file built by Boost.Build at build time. That's all, good night. Domenico -----[ Domenico Andreoli, aka cavok --[ http://www.dandreoli.com/gpgkey.asc ---[ 3A0F 2F80 F79C 678A 8936 4FEE 0677 9033 A20E BC50

5 9