June 2007 - Boost - lists.boost.org

[multi_index] User-defined indices
by Andrey Semashev 12 Jun '07

12 Jun '07

Hello, Reading the Boost.MultiIndex docs I found that support for user-defined index types is planned. Quite occasionally recently I had the need of such functionality and finally developed my own container class for that. Are there any more concrete plans on this improvement of Boost.MultiIndex (a release version or a date)? I guess, the major part of it will be documenting the interface between indices and container itself? -- Best regards, Andrey mailto:andysem@mail.ru

5 13

[Report] 41 regressions on RC_1_34_0 (2007-06-12)
by Douglas Gregor 12 Jun '07

12 Jun '07

Boost Regression test failures Report time: 2007-06-12T00:54:54Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_34_0/developer/i… 41 failures in 4 libraries filesystem (1) program_options (5) test (33) wave (2) |filesystem| operations_test_dll: gcc-cygwin-3.4.4 |program_options| cmdline_test_dll: gcc-cygwin-3.4.4 options_description_test_dll: gcc-cygwin-3.4.4 parsers_test_dll: gcc-cygwin-3.4.4 positional_options_test_dll: gcc-cygwin-3.4.4 variable_map_test_dll: gcc-cygwin-3.4.4 |test| boost_check_equal_str: gcc-cygwin-3.4.4 gcc-mingw-3.4.2 gcc-mingw-3.4.5 errors_handling_test: gcc-cygwin-3.4.4 gcc-mingw-3.4.2 gcc-mingw-3.4.5 fixed_mapping_test: gcc-cygwin-3.4.4 gcc-mingw-3.4.2 gcc-mingw-3.4.5 ifstream_line_iterator_test: gcc-cygwin-3.4.4 gcc-mingw-3.4.2 gcc-mingw-3.4.5 output_test_stream_test: gcc-cygwin-3.4.4 gcc-mingw-3.4.2 gcc-mingw-3.4.5 parameterized_test_test: gcc-cygwin-3.4.4 gcc-mingw-3.4.2 gcc-mingw-3.4.5 result_report_test: gcc-cygwin-3.4.4 gcc-mingw-3.4.2 gcc-mingw-3.4.5 test_case_template_test: gcc-cygwin-3.4.4 gcc-mingw-3.4.2 gcc-mingw-3.4.5 test_fp_comparisons: gcc-cygwin-3.4.4 gcc-mingw-3.4.2 gcc-mingw-3.4.5 test_tools_test: gcc-cygwin-3.4.4 gcc-mingw-3.4.2 gcc-mingw-3.4.5 token_iterator_test: gcc-cygwin-3.4.4 gcc-mingw-3.4.2 gcc-mingw-3.4.5 |wave| testwave_dll: gcc-cygwin-3.4.4 gcc-mingw-3.4.5

1 0

Any interest in "flags" (type safety for enumeration bitsets)
by iain.denniston＠blueyonder.co.uk 12 Jun '07

12 Jun '07

Hi all, I wondered if anyone was interested is this idea - it's something I make a lot of use of, so figured it may be useful to others. I'm far from being expert on boost, the STL, or even C++ so it could easily be that this idea is encapsulated elsewhere and I've simply missed it - apologies if this is the case. Also I'm new to the whole contributing to boost thing, so I hope I've not done anything wrong in that respect. Description A class not dissimilar in operation to std::bitset, but specifically for enumeration flags/bitsets (i.e. combinations of enumerations - of a single enum type - or'd together). That is, a simple wrapper class around enumeration based flags - expected to be completely compiled out by any reasonable C++ compiler. Type safety for enumeration bitsets if you like. Motivation The goal is simple, push potential errors from run time, back to compile time. Additionally it should provide better self documenting code, and assist library users in understanding the arguments required and accepted by a function using the code. Take an example from the STL: void fstream::open(const char *_Filename, ios_base::openmode _Mode); which essentially translates to: void fstream::open(const char *_Filename, int _Mode); Meaning that the following code will compile: std::fstream strm; strm.open("file.txt", 666); Although the results will be anybody's guess - and more importantly may change if the library is changed, producing potentially horrid bugs (not something I would relish tracking down). The above example may be somewhat convoluted, but many times I've seen code where flags have been required as an argument, supposed to be from a specific enumeration only for users to use an enumeration of a different kind, or where a flag is required, but a user passes '0' which is not always a valid option. The new class would mean changing the above to: void fstream::open(const char *_Filename, boost::flags<openmode_enum> _Mode); which would result in an error for the given example (since "666" is not a valid openmode_enum enumeration). Any combination of or'd openmode_enums would, however, compile properly (and would behave as if the flags class did not exist). Obviously this is not a full proof solution - it's as easy to circumvent as enumerations themselves, importantly however someone circumventing it has to try - it'd be much more difficult to accidentally break. Anyways - I hope I've gotten the idea across (and that you all like it :o) Cheers for reading - all comments appreciated! Iain

2 4

[pool] Patches for #284 and #991 added
by Marcus Lindblom 12 Jun '07

12 Jun '07

Hi, I put up two minimal of patches for the pool library. I couldn't figure out how to build the tests (if at all possible for this lib without making my own build setup.). I've at least tested the mem-leak patch (http://svn.boost.org/trac/boost/ticket/284) with our app and vc 7.1 and it works there. :) Cheers, /Marcus

1 1

[integer]integer_traits_test incomplete?
by Larry Evans 12 Jun '07

12 Jun '07

The reason for the question in subject is explained in the following post: http://thread.gmane.org/gmane.comp.parsers.spirit.devel/3121/focus=3195

1 1

Re: [boost] [fusion] transitive const / mutable views?
by dan marsden 12 Jun '07

12 Jun '07

Martin Weiser wrote: >- const is transitive, i.e. dereferencing an iterator into a const vector >yields a reference to a const element and > >- transformation algorithms work on const sequences. > >Combined, these two imply that an in-place modification of a sequence >through a view generated by a transformation algorithm is impossible. >While this is perfectly reasonable for transform, it seems quite >restrictive for filter or erase. After all, filter_view accepts a >non-const input sequence. This is a known and currently deliberate restriction. We decided to adopt a simple programming model for the transformation algorithms, that their results are immutable, leading to a functional style of programming. For many algorithms this makes most sense, although filter is the key example of one where allowing you to write into the filtered output seems reasonable. For now we decided that if users needed mutable behaviour, they could use the equivalent views, such as filter_view, as you identified. We may loosen the above restrictions in future, depending on feedback such as yours about whether the restriction is a regular annoyance. Thanks Dan ___________________________________________________________ Yahoo! Mail is the world's favourite email. Don't settle for less, sign up for your free account today http://uk.rd.yahoo.com/evt=44106/*http://uk.docs.yahoo.com/mail/winter07.ht…

2 1

[filesystem] Handling of long names on windows.
by Loïc Joly 12 Jun '07

12 Jun '07

Hello, I'd like to know if the new release of the filesystem library can handle long file names (>MAX_PATH) on windows ? Those long file names require a wide char API, and that point seems ok in 1.34, but they also require parsing in native format path such as: \\?\D:\<path> \\?\UNC\<server>\<share> I could not find in the reference any file name that loocked that way. Regards, -- Loïc Joly

1 0

[filesystem] Checking if a file exists within a sepcific directory tree
by Michael Marcin 12 Jun '07

12 Jun '07

Suppose the following directory: C:\export As a command line argument in one of my applications, I get an absolute path to a file. I want to check if this file exists at some nested level inside of C:\export. Suppose the file passed in is: C:\export\blah\myfile.txt I would like to be able to call some sort of function that returns 'true' if the file (myfile.txt) exists within the directory tree rooted at C:\export. Now suppose this next file: C:\work\anotherfile.txt The function in question would return 'false' here since anotherfile.txt does not exist inside of c:\export. Something like the following would work for me. is_file_within_directory_tree( "C:\export", "C:\work\anotherfile.txt" ); // returns false is_file_within_directory_tree( "C:\export", "C:\export\blah\myfile.txt" ); // returns true Is there an easy way to do this with Boost.Filesystem? Thanks, Michael Marcin

2 2

[Important] Short outage of the Boost Subversion server
by Doug Gregor 11 Jun '07

11 Jun '07

There will be a short outage of the Boost Subversion server while we import some data into the Subversion repository. This outage will affect the sandbox and the Boost Trac. The outage will occur around 3:30PM EST (about 15 minutes from now) and should last less than an hour. We apologize for the inconvenience. - Doug

1 0

[Report] 41 regressions on RC_1_34_0 (2007-06-11)
by Douglas Gregor 11 Jun '07

11 Jun '07

Boost Regression test failures Report time: 2007-06-11T06:49:17Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_34_0/developer/i… 41 failures in 4 libraries filesystem (1) program_options (5) test (33) wave (2) |filesystem| operations_test_dll: gcc-cygwin-3.4.4 |program_options| cmdline_test_dll: gcc-cygwin-3.4.4 options_description_test_dll: gcc-cygwin-3.4.4 parsers_test_dll: gcc-cygwin-3.4.4 positional_options_test_dll: gcc-cygwin-3.4.4 variable_map_test_dll: gcc-cygwin-3.4.4 |test| boost_check_equal_str: gcc-cygwin-3.4.4 gcc-mingw-3.4.2 gcc-mingw-3.4.5 errors_handling_test: gcc-cygwin-3.4.4 gcc-mingw-3.4.2 gcc-mingw-3.4.5 fixed_mapping_test: gcc-cygwin-3.4.4 gcc-mingw-3.4.2 gcc-mingw-3.4.5 ifstream_line_iterator_test: gcc-cygwin-3.4.4 gcc-mingw-3.4.2 gcc-mingw-3.4.5 output_test_stream_test: gcc-cygwin-3.4.4 gcc-mingw-3.4.2 gcc-mingw-3.4.5 parameterized_test_test: gcc-cygwin-3.4.4 gcc-mingw-3.4.2 gcc-mingw-3.4.5 result_report_test: gcc-cygwin-3.4.4 gcc-mingw-3.4.2 gcc-mingw-3.4.5 test_case_template_test: gcc-cygwin-3.4.4 gcc-mingw-3.4.2 gcc-mingw-3.4.5 test_fp_comparisons: gcc-cygwin-3.4.4 gcc-mingw-3.4.2 gcc-mingw-3.4.5 test_tools_test: gcc-cygwin-3.4.4 gcc-mingw-3.4.2 gcc-mingw-3.4.5 token_iterator_test: gcc-cygwin-3.4.4 gcc-mingw-3.4.2 gcc-mingw-3.4.5 |wave| testwave_dll: gcc-cygwin-3.4.4 gcc-mingw-3.4.5

3 2