- Boost - lists.preview.boost.org

[IOStreams] Opinion on test case needed
by Frank Birbacher 06 Jan '08

06 Jan '08

Hi! I had problems using iostreams::stream<file_descriptor> with Windows and MSVC 8 Express. The file_descriptor had a bug and failed seeking. But the error had gone unnoticed. Because of this I wrote a test case for this in hope to discover an error in IOStreams (source: see below). I did not discover one. Instead the test runs fine on linux/gcc 4.1.2 but fails on Windows/MSVC8Express (test run: see below). I based the test on "Standard C++ IOStreams and Locales" (Langer&Kreft), Section 1.3 "The Stream State". And I found the IOStreams library is just using std::iostream for handling the errors. So is MSVC buggy in this regard? Or am I missing something? Source of test case in Trac SVN Browser: http://svn.boost.org/trac/boost/browser/sandbox-branches/birbacher/fix_iost… Result of test case on platform Windows/MSVC 8 Express: > ...using <p..\..\..\bin.v2\libs\iostreams\test\error_test.test\msvc-8.0express\debug>error_test.exe... > testing.capture-output ..\..\..\bin.v2\libs\iostreams\test\error_test.test\msvc-8.0express\debug\error_test.run > ====== BEGIN OUTPUT ====== > Running 12 test cases... > error_test.cpp(81): error in "wrap_nothrow <&test_seekg>": exception thrown by function(stream) > error_test.cpp(66): error in "wrap_nothrow <&test_seekg>": stream still good > error_test.cpp(68): error in "wrap_nothrow <&test_seekg>": stream did not set badbit > error_test.cpp(69): error in "wrap_nothrow <&test_seekg>": stream did not fail > error_test.cpp(71): error in "wrap_nothrow <&test_seekg>": stream does not report failure by operator ! > error_test.cpp(73): error in "wrap_nothrow <&test_seekg>": stream does not report failure by operator void* > error_test.cpp(66): error in "wrap_throw <&test_seekg>": stream still good > error_test.cpp(68): error in "wrap_throw <&test_seekg>": stream did not set badbit > error_test.cpp(69): error in "wrap_throw <&test_seekg>": stream did not fail > error_test.cpp(71): error in "wrap_throw <&test_seekg>": stream does not report failure by operator ! > error_test.cpp(73): error in "wrap_throw <&test_seekg>": stream does not report failure by operator void* > unknown location(0): fatal error in "wrap_throw_delayed<&test_seekg>": std::runtime_error: bad seek > error_test.cpp(73): last checkpoint > error_test.cpp(81): error in "wrap_nothrow <&test_seekp>": exception thrown by function(stream) > error_test.cpp(66): error in "wrap_nothrow <&test_seekp>": stream still good > error_test.cpp(68): error in "wrap_nothrow <&test_seekp>": stream did not set badbit > error_test.cpp(69): error in "wrap_nothrow <&test_seekp>": stream did not fail > error_test.cpp(71): error in "wrap_nothrow <&test_seekp>": stream does not report failure by operator ! > error_test.cpp(73): error in "wrap_nothrow <&test_seekp>": stream does not report failure by operator void* > error_test.cpp(66): error in "wrap_throw <&test_seekp>": stream still good > error_test.cpp(68): error in "wrap_throw <&test_seekp>": stream did not set badbit > error_test.cpp(69): error in "wrap_throw <&test_seekp>": stream did not fail > error_test.cpp(71): error in "wrap_throw <&test_seekp>": stream does not report failure by operator ! > error_test.cpp(73): error in "wrap_throw <&test_seekp>": stream does not report failure by operator void* > unknown location(0): fatal error in "wrap_throw_delayed<&test_seekp>": std::runtime_error: bad seek > error_test.cpp(73): last checkpoint > > *** 24 failures detected in test suite "Master Test Suite" > > EXIT STATUS: 201 > ====== END OUTPUT ====== Any opinions on this? Any suggestions on what to do about it? Frank

4 16

[www patch] CVS link on front page
by Jonathan Wakely 06 Jan '08

06 Jan '08

Hi all, and happy new year. the front page of www.boost.org still links to SourceForge for "Main CVS." I don't have an svn account so could someone please apply this. Thanks, Jon

2 3

Trac lists not all available libraries
by Jens Seidel 06 Jan '08

06 Jan '08

Hi, it happened already some times that I tried to report a bug in Trac but could not select the proper library. Yesterday I missed e.g. accumulators. Can you please update it? Is there an easy way to directly contact a submitter if I only know his Subversion account? Can I just append @boost.org or something like this? It is currently hard to find the email address even if one can guess the name as the address is often either just not displayed (web site, even on the people section) or obfuscated by the mail archive. Even spam protection does not excuse this. If one is willing to work on an Open Source project it should be possible to find contact data. Jens

2 2

Re: [boost] upcoming Switch library review Jan 5th - Jan 9th
by Tobias Schwinger 06 Jan '08

06 Jan '08

Forwarding this post from boost.user... Steven Watanabe wrote: > AMDG > > Tobias Schwinger <tschwinger <at> isonews2.com> writes: > >> dan marsden wrote: >>> Why is the fall through behaviour to throw an exception? >> I too tripped over this one, yesterday. >> >> <snip> > The other option is an assertion. Is that any better? I think the "default default behavior" should be to use the default constructor. This approach works nice with Any, Variant and Optional. > Or should a void return type be a special case? If 'Default's result type is 'void' although something else is expected, we should assert it never actually returns at runtime (note that it is possible to detect the result type with an overloaded comma operator and without requiring 'Default' to work with 'result_of' -- might also be faster). If assertions are disabled the behavior should be unspecified in that case. <snip> >> Of course there are no pointers to templates, so using a function >> pointer for anything but the default is pretty pointless. So is trying >> to handle varying result types -- maybe the result type should be passed >> in with another template parameter? > > I'd rather leave it as result_of<F()>::type. Actually 'result_of<F()>::type' determines the result of the nullary call to F. I don't think I like this sort of "result_of abuse"... The correct usage would be 'result_of<F(MPLConstant)>::type' but it's pointless since 'MPLConstant' varies and so may the whole type expression. So, if you insist on deducing the result type from the function object (instead of having it specified explicitly) my vote is 'F::result_type', however, I still find another template parameter more appropriate for the following good reasons: o The function object can work fine with result_of in a non-'switch_' context. The cases can return different things as long as they are convertible to the result of 'switch_', and o there is no way to determine this type with 'result_of. Regards, Tobias

2 1

Re: [boost] Trac lists not all available libraries
by Daniel James 06 Jan '08

06 Jan '08

On 06/01/2008, Marshall Clow <marshall(a)idio.com> wrote: > I'll add accumulators to the trac system. Please can you add unordered as well. thanks, Daniel

2 3

[Interprocess] Interprocess' reference documentation overwritten by Boostbook's.
by Daniel James 06 Jan '08

06 Jan '08

Hi Ion, The main page of the Interprocess reference documentation is created at '/doc/html/reference.html' which is the same location as the Boostbook reference documentation. When the combined documentation is generated is gets overwritten by boostbook. So can you change the location it's generated at? Thanks, Daniel

1 0

Re: [boost] Switch library overloads of call operator
by dan marsden 06 Jan '08

06 Jan '08

Steven Watanabe wrote: >dan marsden <danmarsden <at> yahoo.co.uk> writes: >> The documentation is not specific about which specific type >> (e.g. mpl::int_<1> for case 1 matching in the >> underlying switch statement) is going to be used. >The type that is passed to f is whatever is in the list of cases. Ok cool. >> It looks to me like >> it would be convenient to overload >> operator() for each case I want to service, but this will be >> awkward to do without knowing the exact type >> that will be incoming. >> >> <snip> > >If multiple cases are not grouped together, I don't >see how it's an advantage to use my library vs. using a >plain old hand-written switch. Would you mind elaborating? I think you're probably right, my original suggestion that multiple overloads of operator() would be likely is probably wrong. I can only suggest handling special cases such as divide by zero for example, but I think my original suggestion may be a red herring. Cheers Dan ___________________________________________________________ Support the World Aids Awareness campaign this month with Yahoo! For Good http://uk.promotions.yahoo.com/forgood/

2 1

Switch library overloads of call operator
by dan marsden 06 Jan '08

06 Jan '08

Hi Another question about the design / docs for the switch library under review. From what I understand switch takes a runtime integral value, uses a PP generated switch statement, and calls out using some sort of MPL integral constant to specify the switch case to be served. This is pretty cool, as we seem to be travelling back from runtime into compile time world. The documentation is not specific about which specific type (e.g. mpl::int_<1> for case 1 matching in the underlying switch statement) is going to be used. It looks to me like it would be convenient to overload operator() for each case I want to service, but this will be awkward to do without knowing the exact type that will be incoming. Otherwise I'm going to have to use enable_if or something to separate out the cases, which seems unnecessarily awkward. The example provided is fortunate that it behaves uniformly for each incoming value, so only 1 overload of operator() is required. IMO this will not be the common case, an example with differing behaviour would be helpful. I think the documentation could do with a bit of clarification in this area. Cheers Dan ___________________________________________________________ Support the World Aids Awareness campaign this month with Yahoo! For Good http://uk.promotions.yahoo.com/forgood/

3 2

Re: [boost] Iostreams and Network [asio]
by Jonathan Turkanis 05 Jan '08

05 Jan '08

Hi JD, JD wrote: > And also, is there any attempt to write a Source/Sink to read and write > from shared memory? Currently there is http://www.boost.org/libs/iostreams/doc/classes/mapped_file.html. While I have been away from Boost, the Interprocess library has been accepted, providing sophisticated support for shared memory and memory mapped files. I am planning to write devices to access the functionality of the Boost.Interprocess for 1.36. > JD >> Hi, >> >> Iostreams documentation states: "For example, Boost.Iostreams can be >> used to create streams to access TCP connections". Is there any such >> attempt to create a TCP/IP communicating Source/Sink couple? >> I know asio is doing this, but I was looking for an pure Iostreams >> solution. Currently there are no devices for TCP/IP communications. I am planning to implement blocking TCP/IO devices using asio for 1.36, but I also hope at some point to achieve a better degree of integration. Standard iostreams are not a very good way to access network connections, since they are designed for blocking i/o; however, Boost.Iostreams is also intended as a framework for filtering, and I was careful to design filter concepts that would work with asynchronous and non-blocking devices. When Boost.Asio was proposed, I was looking forward to the possibility of introducing asynchronous and non-blocking device concepts to make the libraries work together, but unfortunately I became so busy that I was not able to participate in the review process or collaborate with Chris Kohlhoff in the subsequent development of the library. Now that I have more time I am committed to trying to make the two libraries work together as much as possible. >> Regards, >> >> JD -- Jonathan Turkanis CodeRage http://www.coderage.com

1 0

[iostreams] understanding the models
by Benjamin Collins 05 Jan '08

05 Jan '08

I'm trying to write a device for iostreams, but I'm having a hard time understanding how the current sources and the models explained in the documentation are in agreement. Maybe I'm shooting myself in the foot by never being able to work on this for more than 30 minutes at a time and having that 30 minutes be late at night, but... Anyway, it seems odd to me - for example, the boost::iostreams::mapped_file_source class has the following category of source_tag + direct_tag + closable_tag, and has member functions open(), size(), data(), begin(), and end(). None of these are particularly surprising. After all - a mapped_file has to be open()ed at some point. But under what model as defined in the docs? In other words, how and when is that function called, and how does a stream_buffer know he can call open() on a particular device? Also, the documentation indicates that a source device needs to support the read() function - but mapped_file_source has no read() (maybe because it is convertible to 'direct'?). -- Benjamin A. Collins <ben.collins(a)acm.org> http://bloggoergosum.us

2 1

[iostreams] Patch for latest CodeGear (Borland) compiler
by Nicola Musatti 05 Jan '08

05 Jan '08

Hallo, The patch in http://svn.boost.org/trac/boost/ticket/1294 improves support for the latest version of bcc32, 5.9.2 . If I don't receive objections in two or three days I'll apply it. Cheers, Nicola -- Nicola.Musatti <at> gmail <dot> com Home: http://nicola.musatti.googlepages.com/home Blog: http://wthwdik.wordpress.com/

2 1

build error during integration of serialization lib
by Arunava Saha 05 Jan '08

05 Jan '08

Dear Robert/experts, I am getting build errors after the integration of versioning in serialization lib. I have included the version.hpp. The following is the error msgs I am getting. Can someone please point me to the issue? FYI, everything is working fine except this versioning stuff. error: 'version' is not a template error: explicit specialization of non-template error: 'mpl' has not been declared error: ISO C++ forbids declaration of 'int_' with no type error: expected ';' before '<' token error: 'mpl' has not been declared error: 'integral_c_tag' does not name a type Thanks, Arunava.

2 1

[1.35.0] Intel compiler - does anyone care?
by Beman Dawes 05 Jan '08

05 Jan '08

The great bulk of remaining 1.35.0 release test issues are with the Intel compiler. See http://beta.boost.org/development/tests/release/developer/issues.html Does anyone really care about this compiler? Should we drop it from the high priority list? If there are folks who do care, perhaps they could suggest a plan to eliminate the failures, or at least shed light on why so many tests are failing. --Beman

9 20

Switch library review begins today and ends on Jan 9th
by Stjepan Rajko 05 Jan '08

05 Jan '08

The review of the Switch library by Steven Watanabe begins today. Description: The built in C/C++ switch statement is very efficient. Unfortunately, unlike a chained if/else construct there is no easy way to use it when the number of cases depends on a template parameter. The Switch library addresses this issue. You can download the library from the Boost Vault: http://tinyurl.com/23qn7w For convenience, the docs have been uploaded here: http://tinyurl.com/2h6ut9 ... and the source file here: http://tinyurl.com/2cbfyk What to include in Review Comments Your comments may be brief or lengthy, but basically the Review Manager needs your evaluation of the library. If you identify problems along the way, please note if they are minor, serious, or showstoppers. Here are some questions you might want to answer in your review: * What is your evaluation of the design? * What is your evaluation of the implementation? * What is your evaluation of the documentation? * What is your evaluation of the potential usefulness of the library? * Did you try to use the library? With what compiler? Did you have any problems? * How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? * Are you knowledgeable about the problem domain? And finally, every review should answer this question: * Do you think the library should be accepted as a Boost library? Be sure to say this explicitly so that your other comments don't obscure your overall opinion. Thanks to Dan Marsden, Larry Evans, Tobias Schwinger, and Alexander Nasonov for already opening up the discussion in the following threads: http://tinyurl.com/2u6fjr [nabble/boost-user] http://tinyurl.com/267uj3 [nabble/boost-dev] Thank you for taking the time to look into this library, and I hope that some of you will be able to provide a full review for it. Regards, Stjepan

1 0

[compressed_pair] using compressed_pair to substitute a possibly empty member
by Tobias Schwinger 05 Jan '08

05 Jan '08

Hi, I'm using compressed_pair to substitute a possibly empty member whose type is specified by a template argument and experience difficulties: template< typename T > class A { T x; public: // [ctor, ...] void foo() const { // if T is a reference type, non-const access to the // object referenced by x is possible, here } }; // but: template< typename T > class changed_A : boost::compressed_pair<T,boost::blank> { public: // [ctor, ...] void foo() const { // first() always returns a reference to const // even if T is a reference to non-const } }; So: Did I find a subtle design flaw or bug in compressed_pair or is it just the use case I'm throwing at it? In case of the latter we should probably introduce a compressed_member (or so) and have it implement const semantics consistent with members. Regards, Tobias

1 0

[Interval] Conversion from integer types?
by John Maddock 04 Jan '08

04 Jan '08

Can someone explain what the issue is in converting an integer type to a boost::interval, and in performing mixed integer/floating point arithmetic and comparisons? Is it simply that the integer types may have more bits in their representation than floating point ones, and we may therefore loose precision? If so, can we not convert integers to intervals implicitly, complete with calculation of the error? That would auto-magically make mixed integer/floating point arithmetic work as well. And yes, I'm prepared to invest some time to make this work and do the right thing, if time is the only stumbling block :-) Thanks, John.

3 6

boost.test link error
by jerome.wacongne＠fxoverlay.com 04 Jan '08

04 Jan '08

Hi, My problem might be a beginner one, but I spent all day searching forums and mailing archives and it didn't help much, so I am asking at the source. The reason why I write this email is that modifying boost source helps but what I did is not enough. what I did : - a first test file using helper macros to test a class (works fine alone) : #define BOOST_TEST_MAIN #include <boost/test/unit_test.hpp> BOOST_AUTO_TEST_SUITE(Class1TestsSuite); BOOST_AUTO_TEST_CASE( test1 ){ BOOST_CHECK(1 == 2-1); } BOOST_AUTO_TEST_SUITE_END(); - add a second test file using helper macros to test an other class (compilation is OK, link KO) : #define BOOST_TEST_MAIN #include <boost/test/unit_test.hpp> BOOST_AUTO_TEST_SUITE(Class2TestsSuite); BOOST_AUTO_TEST_CASE( test2 ){ BOOST_CHECK(1 != 2); } BOOST_AUTO_TEST_SUITE_END(); Here are the errors : c:/dev/mingw/bin/../lib/gcc/i686-pc-mingw32/4.2.1-dw2/../../../../include/c++/4.2.1-dw2/new multiple definition of `init_unit_test_suite(int, char**)' line 105 tests\main.o:c:/dev/mingw/bin/../lib/gcc/i686-pc-mingw32/4.2.1-dw2/../../../../include/boost/test/unit_test_suite.hpp first defined here line 184 I have edited unit_test_suite.hpp to add inline decalration to init_unit_test_suite : #else inline ::boost::unit_test::test_suite* init_unit_test_suite( int, char* [] ) { #endif Doing so, first error is suppressed. I might need to rebuild boost test lib for the second, but I haven't the tools at workplace. I am using : - Windows XP - MinGW packaged with boost 1.34.1 (http://nuwen.net/mingw.html) - Eclipse CDT Regards, Jérôme. This message and any attachments (the "message") is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. Overlay AM (and its subsidiaries) shall (will) not therefore be liable for the message if modified. --------------------------------------------- Ce message et toutes les pieces jointes (ci-apres le "message") sont etablis a l'intention exclusive de ses destinataires et sont confidentiels. Si vous recevez ce message par erreur, merci de le detruire et d'en avertir immediatement l'expediteur. Toute utilisation de ce message non conforme a sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. L'internet ne permettant pas d'assurer l'integrite de ce message, Overlay AM (et ses filiales) decline(nt) toute responsabilite au titre de ce message, dans l'hypothese ou il aurait ete modifie.

2 1

Re: [boost] [1.35.0] Intel compiler - does anyone care?
by Chad Walters 04 Jan '08

04 Jan '08

Beman Dawes wrote: > If there are folks who do care, perhaps they could suggest a plan to > eliminate the failures, or at least shed light on why so many tests are > failing. I imagine that Intel should care. ;) One of my team members used to work on the Intel compiler - I'll ask him to ping his former colleagues to see if we can get some attention from them on this issue. Chad

1 0

Question regarding boost.unordered
by Lipik Contact 03 Jan '08

03 Jan '08

Hello list, I have downloaded unordered library from the vault and plan to start using it. However, looking at the documentation, there might be issues that prevent it being useful for me. Could someone please comment on the following: If the user holds a reference (or pointer) to some element in the container (e.g. T const *p = &*it), is that reference guaranteed to remain valid after the insertion/erase of some other elements? I ask because doc says that erasing through an iterator can be O(size) - which seems to suggest that erase can lead to a rehash, invalidating iterators. This appears to contradict the iterator lifetime guarantee posited by the standard (after all, tree based containers don't rebalance after erase, do they?) Another question: any thoughts on whether it is better to use boost::hash for pointers and wstrings, or would a modification of the FNV hash included with unordered give better results? Also, I'm assuming that I can plug this library into boost-1.33.1. Many thanks Amit

3 2

Trac open bugs - by assignee
by Marshall Clow 03 Jan '08

03 Jan '08

[ 190 open bugs today, 190 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 18 az_sw_dude 17 dgregor 15 djowel 12 doug_gregor 11 grafik 11 dave 11 None 10 agurtovoy 8 vladimir_prus 8 jsiek 7 johnmaddock 7 anthonyw 5 witt 4 bemandawes 3 rogeeff 3 pdimov 3 jmaurer 3 igaztanaga 3 ebf 3 danielw 2 urzuga 2 turkanis 2 pavol_droba 2 niels_dekker 2 nesotto 2 nasonov 2 matias 2 <Blank> 1 t_schwinger 1 speedsnail 1 shammah 1 samuel_krempp 1 ramey 1 marshall 1 kaalus 1 hljin 1 hkaiser 1 dlwalker 1 burbelgruff 1 aaron_windsor <Blank> 1307 [lambda] invalid boostbook <Blank> 1434 Boost.Preprocessor_ small fix for the documentation None 1068 Mersenne twister disables streaming for Visual C++ None 1094 Finding the correct library to link (feature request for pkg-config support)h None 1222 lambda::ret<T> should declare result_type. None 1247 Typos in "boost/random/additive_combine.hpp"_ lines 68-69 None 1270 uniform_smallint doesn't compile with lagged_fibonacci random number generators None 1407 Boost is doesn't install on MacPorts using Leopard None 1493 SVN files making it through to install None 1515 [lambda] C4512 warnings from VC8.0 None 1544 uniform_01 w/ref template param causes ref to ref error None 1546 Method boost::random::uniform_int::operator()(engine_ value) is missing None 1548 [variant][docs]typo: formal arg_ operand_ should be v in times_two arglist aaron_windsor 778 top-level configure is broken agurtovoy 1001 gcc 4.1.2 segfaults on mpl/test/apply.cpp agurtovoy 1051 MPL header ordering triggers bug agurtovoy 1099 unable to iterate through a "non-explicitly-declared" mpl::set agurtovoy 1215 Boost 1.34.1_ mpl: Wrong workaround detection using MinGW32 (or.hpp_ line #33) agurtovoy 1317 has_xxx randomly broken in msvc agurtovoy 1469 [mpl] nested typedef of set has two different meanings agurtovoy 1476 always<> is not nullary. agurtovoy 1528 g++ 4.3.0 reports error because of redeclaration of next agurtovoy 588 mpl::remove compile error with gcc 4.1.0 agurtovoy 640 documentation mistake 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 1547 [thread] error C2065: 'NULL' : undeclared identifier in thread_primitives.hpp anthonyw 876 xtime documentation incomplete anthonyw 881 errors when build with Apache stdcxx az_sw_dude 1028 typo in boost header: date_time/time_defs.hpp az_sw_dude 1078 from_iso_string cannot read the output from to_iso_string az_sw_dude 1098 Urgent libboost-date-time1.33.1 : bugs on ia64 ? az_sw_dude 1147 date_time library contains global #define ERROR az_sw_dude 1160 warning: month_format shadows a member of this az_sw_dude 1162 warning: ticks shadows a member of this az_sw_dude 1289 posix_time::time_facet forgets to pass a_ref argument to base class az_sw_dude 1299 change in typedef stringstream_type in format_date_parser.hpp causing compilation error az_sw_dude 1306 invalid docbook in date_period.xml az_sw_dude 1384 Linking problem with date_time library on Visual C++ 2008 Express az_sw_dude 1386 date_time documentation Jamfile breaks building of boost docs az_sw_dude 1524 format_date_parser.hpp(221) : cannot convert parameter 1 az_sw_dude 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 752 directory_iterator doesn't work with catch burbelgruff 1503 typeof bug (big integral constant) 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 865 Use of C++0x keyword as identifier dave 910 gcc strict-aliasing problems with python dgregor 1003 [iostreams] copy-paste error in typedefs for wchar multichar_filters dgregor 1139 [iostreams] Regex filter segfaults when zero matches found dgregor 1140 boost::iostreams linked_streambuf bug dgregor 1149 Minor doc error in basic_null_device dgregor 1164 Floyd Warshall broken with unsigned edge weights dgregor 1185 iostreams::direct_streambuf<T_Tr>::is_open always returns false if output iterator is not null dgregor 1192 [boostbook] problem when two files have the same name dgregor 1199 configure doesn't work with path containing whitespaces (MacOS X) dgregor 1232 mapped_file_source::is_open() is broken under windows 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 1394 Translate libs/graph/build/python/Jamfile to BBv2 dgregor 1395 Write Tests for Python Bindings dgregor 556 Bundled graph properties dgregor 732 Johnson All-Pairs needs better "no path" information dgregor 736 Const correctness violation djowel 1170 Emit Warnings instead of # symbols in the syntax highlighter djowel 1171 Quickbook title output djowel 1172 non-utf djowel 1176 Space after inline code djowel 1206 Escaping from within code? djowel 1273 CR+LF newlines in position_iterator djowel 1276 spirit problem with _GLIBCXX_DEBUG djowel 1277 Closing section like [pre with } causes Quickbok to crash djowel 1280 sections in imported source files get put inside <para> elements in docbook output djowel 1281 Quickbook produces invalid BoostBook/DocBook XML djowel 1324 tuple should have a swap() that operates element-by-element djowel 1396 wrong result_of invocation around transform_view djowel 1436 [quickbook] inline code inside headings djowel 1484 Quickbook produces illegal docbook for some docinfo fields. djowel 1500 [Spirit/Phoenix] C4512 Compiler warnings from VC8 dlwalker 613 boost/crc.hpp uses non-standard conforming syntax doug_gregor 1021 [Graph][reverse_graph] Problem using reverse_graph adapter with an adapted user defined graph doug_gregor 1076 compile error: disconnecting struct with operator()() doesn't work in VS2005 SP1 doug_gregor 375 LEDA graph adaptors do not handle hidden nodes properly doug_gregor 402 random_vertex/random_edge are unnecessarily inefficient doug_gregor 403 Document copy_component doug_gregor 447 reverse_graph and constness of property maps doug_gregor 708 Dijkstra no_init version should not require VertexListGraph doug_gregor 733 Numbered headers don't work with "preferred" syntax doug_gregor 735 Fruchterman-Reingold grid performance can be improved doug_gregor 738 Memory leaks with signal::connect? doug_gregor 829 Implicit graph not implement doug_gregor 852 Problem with Boost and GCC 4.1 ebf 1507 [variant] C4512 warnings from VC8.0 ebf 965 [doc] boost::variant tutorial - final example uses v1_v2 should be seq1_seq2 ebf 993 Variant should use least common multiple of alignments_ rather than maximum grafik 1041 Cygwin requires PATH setting. grafik 1062 Cygwin install stage fails with combination of patches grafik 1322 trac rejects patch attachment as spam grafik 1417 Regresson tests hang in Darwin (Tiger) grafik 1430 Regression fails under Cygwin grafik 1433 Trac's spam detection rejects too many valid messages grafik 1512 Broken link to vacpp in bjam docs. grafik 1513 Broken link to bcpp in bjam docs. grafik 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. hljin 1522 bit_range friend decl in bit_aligned_pixel_reference.hpp needs to be fully qualified for gcc 4.3 mainline 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 jmaurer 351 Diff in state of mersenne_twister gen between GCC3.41 & CW9 jmaurer 599 uniform_01 copies engine instead of using a reference jmaurer 819 uniform_int<> with type's maximum availaible range error johnmaddock 1081 Empty string rejected as perl-style regex johnmaddock 1314 Using SSE-intrinsics in VC8 causes static assert in type_with_alignment.hpp johnmaddock 1411 Fix BOOST_PARTIAL_SPECIALIZATION_EXPLICT_ARGS johnmaddock 1440 libs/config/test/link/Jamfile.v2 confuses process_jam_log johnmaddock 1446 POSIX API doesn't use C locale johnmaddock 1451 error: use of C99 long long integer constant johnmaddock 1511 Non latin symbols in regexp jsiek 1531 segfault in dynamic_bitset::reference assign operator jsiek 1540 Poisson distribution very slow for large mean (and may also overflow). jsiek 416 Spelling of Edmonds-Karp-Algorithm 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 marshall 1252 [pool] severe overhead with unaligned sizes. matias 1406 Understanding the Tables outdated matias 1539 Missing semi-colon in random library quitck start example nasonov 1220 lexical_cast requires RTTI nasonov 754 boost::any - typeid comparison across shared boundaries nesotto 1284 [range] sub_range assignment issue nesotto 1464 boost_range_array unused in several array_size() functions niels_dekker 1459 value_initialized leaves data uninitialized_ when using Borland niels_dekker 1491 value_initialized leaves data uninitialized_ when using GCC pavol_droba 1152 rle_example fails pavol_droba 1385 begin must be boost-qualified pdimov 1106 shared_ptr<T> should not convert to shared_ptr<U> when T* doesn't convert to U* pdimov 1444 scoped_ptr::operator== should be equivalent to a.get()==b.get()_ but is currently !!a==!!b pdimov 779 gcc-4.2 atomicity.h location ramey 1121 xml_archive_exception is missing seperate header file_ and documentation mismatch rogeeff 1383 signal.h features not found on Mac OS rogeeff 1489 BOOST_CHECK_CLOSE fails to compile with templated value type rogeeff 1542 [test] compiler errors when building with stdcxx library samuel_krempp 859 boost::format ignores a user defined locale shammah 386 boost::pool_allocator breaks with vector of vectors 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 1523 [iostreams] VC8/VC9 compiler warnings turkanis 1545 [boost/rational.hpp] 'noskipws' is not a member of 'std' urzuga 574 [boost::lambda] Compile error with libstdc++ debug mode urzuga 781 Lambda: (_1 + "y")(string("x")) Doesn't Compile vladimir_prus 1165 more quoting problems vladimir_prus 1274 Useless error message vladimir_prus 1321 invalid docbook in tool documentation vladimir_prus 1527 [program_options] Second (and subsequent) lines in tabbed text not aligned correctly vladimir_prus 1530 Program options documentation - Overview - Syntactic Information example typo vladimir_prus 1537 no value given in 'mysql_password =' vladimir_prus 469 multitoken broken vladimir_prus 689 [program_options] Endless loop with long default arguments witt 1046 Boost.Python quickstart instructions mention nonexistent target witt 583 Fixes for build on IBM pSeries for AIX and Linux witt 834 Homepage regression links witt 957 The "Getting Started" page does not mention the stdlib option witt 973 zip_iterator has value_type == reference -- -- Marshall Marshall Clow Qualcomm, Inc. <mailto:mclow@qualcomm.com> The famous British scientist, Lord Kelvin, said: "When you measure what you are speaking about and express it in numbers, you know something about it, but when you cannot (or do not) measure it, when you cannot (or do not) express it in numbers, then your knowledge is of a meagre and unsatisfactory kind."

1 0

Re: [boost] [Boost-users] upcoming Switch library review Jan 5th - Jan 9th
by Stjepan Rajko 03 Jan '08

03 Jan '08

On Jan 2, 2008 2:36 PM, dan marsden <danmarsden(a)yahoo.co.uk> wrote: > Stjepan Rajko wrote: > > If you are interested, please consider submitting a review of this > > library. I will send more detailed instructions on what to include in > > the review on the 5th. > > Can I jump the gun with with a few questions please? Of course - thanks for opening up the discussion! I'm just not sure whether Steven will be able to respond until the review officially starts. > > Why is the fall through behaviour to throw an exception? This is > not consistent with standard switch, possibly a motivation section is > needed in the docs to explain this type of decision? > > I'm not too clear with the documentation what the parameter 'n' can > be? It is of type 'Int' which is described as being an Integer in the > parameters section of the documentation. What does this mean, any > built in integral type, can I switch on a std::string? What are the > limitations? I got a bit lost here in the docs here, after admittedly only > a quick read. Maybe just some clarification is required? > > The parameter section does not specify the arities of the 2 function > object parameters, I had to deduce them from the example. Why do > these have to be function objects, and not just any callable type, > including ordinary functions (using the Boost.ResultOf mechanism to > sort out the return type)? I'm not sure how useful that would be for 'f', > but for 'default_' a full blow function object seems a bit much typing, > can't I just use a function. > > Also, why is 'default_' unary, the default in a standard switch > statement does not access the switch parameter, and the example > does not exploit this feature either. Why not just a nullary function? > Again some motivation might be nice. > > And finally, as the introduction mentions the efficiency of the standard > switch statement, could the docs show some performance stats for the > library code for comparison? > > Cheers > > Dan > Stjepan

1 0

optimization of boost::end
by Neal Becker 03 Jan '08

03 Jan '08

The common idiom is: for (; i != boost::end (vector); ++i) ... The compiler had damn well better realize that boost::end is a constant function that can be lifted from the loop, or performance can be severely impacted. Does anyone have any experience with this? Is there a portable way to give hints to the compiler? Should boost provide such a facility?

3 3

[review][unordered] Review summary
by Ion Gaztañaga 03 Jan '08

03 Jan '08

Hi to all, This post tries to summarize the review of the new Boost.Unordered library. In general, there were no serious implementation change requests and most reviewers had only documentation issues. Here we go: * * * begin of summary * * * Thosten Ottosen's review: ---------------------- (http://lists.boost.org/Archives/boost/2007/12/131372.php) Thorsten questioned about the convenience of supporting throwing hash or predicates. This started a thread about the exception safety guarantees of STL containers and Daniel explained the thread-safety guarantees of Unordered. Basically, Daniel's implementation uses an smart double-buffering technique to obtain strong safety guarantees (stricter than the requirements of the standard) in some operations. There's an slight size overhead (the container must allocate space for two equality functors and hashers) but according to Daniel, speed should not suffer. Chung Ping Wang's review: ---------------------- (http://lists.boost.org/Archives/boost/2007/12/131372.php) The only complain was the packaging of the library (there was an "unordered" directory at the top). Since the library has been accepted it will be packaged as the rest of Boost libraries so the problem disappears. Mathias Gaunard's comment: ---------------------- (http://lists.boost.org/Archives/boost/2007/12/131426.php) Mathias suggested adding move semantics and in-place construction. Daniel said that these features were likely to be added in the future. He pointed that we have no standard move emulation library in Boost so we'll need to push that first. Regarding in-place construction, there is a problem with allocators, since containers are now required to call allocator::construct() to construct values. Hervé Brönnimann's review: ---------------------- (http://lists.boost.org/Archives/boost/2007/12/131435.php) Hervé praised the library and suggested adding operator==(). Daniel replied that he was trying to limit himself to obvious design decisions for extensions so he didn't want to go into this area. He also cited some problems with non-unique key unordered containers. Hervé suggested extending the prime number list and Daniel agreed. Daniel also agreed to correct some documentation issues. "Swap" semantics wrt allocators was also discussed. "Swap" and its effect on containers is an active issue in the committee, so Daniel is free to implement what he thinks best until we have a firm resolution. John Torjo's review: ---------------------- (http://lists.boost.org/Archives/boost/2007/12/131557.php) A concise and positive review with no comments. Jamie Allsop's review: ---------------------- (http://lists.boost.org/Archives/boost/2007/12/131762.php) Documentation suggestions that Daniel found interesting and a request to include a comparison with other implementations. Steven Watanabe's comments ---------------------- (http://lists.boost.org/Archives/boost/2007/12/131817.php) Several implementation comments regarding (ADL, BOOST_DEDUCED_TYPENAME, warnings...). See the post for details. Cromwell Enage's review ---------------------- (http://lists.boost.org/boost-users/2007/12/32706.php) Suggested the addition of local_cbegin() and similar, and some documentation suggestions Daniel agreed to solve. Paul A Bristow's review ---------------------- (http://lists.boost.org/Archives/boost/2007/12/131545.php) A brief and positive review with no comments. * * * end of summary * * * Regards, Ion

3 2

Old Lambda support request....
by Marshall Clow 03 Jan '08

03 Jan '08

Three years old - looks like an easy answer. <http://svn.boost.org/trac/boost/ticket/426> Anyone? Anyone? Bueller? Thanks. -- -- 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.

4 3

[Accumulators] is there an updated version?
by Jamie Allsop 03 Jan '08

03 Jan '08

I recently had a need for some simple statistical analysis of performance data and thought rather than sit down and write my own functions for mean, variance etc. I'd take the time to learn and use the Accumulators library that was accepted into boost on February the 19th of this year, <http://lists.boost.org/boost-announce/2007/02/0114.php> The only version I could find was that in the vault, <http://www.boost-consulting.com/vault/index.php?action=downloadfile&filenam…> This appears to have been updated last on 21.09.2007 03:32. The first thing I am wondering is why this library is not in TRUNK now that it is a part of boost? Secondly I thought I'd comment briefly on something that I noticed came up during review but has (as yet) not been addressed in the vault version. I too assumed that using boost::accumulators::tag::variance would return a useful value for variance, unfortunately it returned (in my case) what appeared to be an erroneous negative value. The 'immediate_' form worked ok. My comment would be that after reading the review there was some debate about providing a naive implementation. My thought after spending time reading the reviews and browsing the code to try to figure out what was happening was that, if I wanted a naive implementation, I could provide that easily myself. However I turned to the library to a) save me writing and maintaining the code, and b) to enjoy a well thought out implementation by a domain knowledgeable implementor. I therefore think that the natural choices should be accurate implementations. If I know enough about my data to realise I can get away with a naive implementation that sacrifices accuracy (perhaps for performance reasons) then I can select one purposefully. My first experience with the accumulators library was a mixed bag, but I have not used it enough to really form too many opinions on it. I suppose when I initially looked at it I thought I would have access to statistical algorithms that I could apply to my data, but in fact it works differently than that (and I am sure there was a good reason for that approach). I'll have to revisit the doc to see if I can find understand the motivation better. It works well as it is mind you. Beyond that the library appears useful and I look forward to making more use of it. I'd be very interested in seeing a newer version of the library that addresses the many points highlighted during the review or at least know that the library is currently being tidied up and will make into a boost release soon :) Thanks, Jamie

2 4