- Boost - lists.preview.boost.org

New Library Proposals
by Lemings, Eric B. 13 Oct '04

13 Oct '04

Hi, I'd like to solicit interest in the following brief proposals for inclusion in the Boost library. cla (Command-Line Arguments) - A generic C++ framework for parsing command-line arguments. The library design would be based on the popt (http://www.rpm.org/dark_corners/popt/) library. uom (Units Of Measure) - A generic C++ framework for arithmetic calculations and conversions between different units of measure. The library design would be based on The Units Of Measure Library (http://tuoml.sourceforge.net/) Questions and comments welcomed. Thanks, Eric.

7 6

[array] bug, interface change and more
by Joao Abecasis 13 Oct '04

13 Oct '04

Hi all! 1) I want to report that array::at throws range_error when it should throw out_of_range to comply to Sequence requirements. After I decided to report this issue I learned that Nicolai Josuttis maintains a parallel version boost/array.hpp on his website that corrects this and has a few other changes. Namely, an overload for 0-sized arrays was added and c_array has been renamed to data. I believe these changes were made after discussion for proposed inclusion in TR1. 2) Now I'm wondering if c_array should be renamed to data before the next release, to avoid having to change the interface later. 3) Could get<Index> functions be added to array, in order to mimick tuple? There are probably other things that can be done to make boost::array behave like a tuple. I think array could also be considered for inclusion in fusion. 4) On a side note, I wrote an initialized_array class that is very much like array but provides the constructors (and thus cannot provide aggregate initialization syntax): * default element construction * default array construction (boost::array provides this) * initialized_array<T, N>(T const & val) // elements initialized to val * initialized_array<T, N>(T const (&vals)[ N2 ]) // elements initialized with array. If N2 < N remaining elements are default constructed * initialized_array<T, N>(InputIterator start, InputIterator finish) // similar to previous but with iterators Exception behaviour is the same as for arrays (accomplished with a linear hierarchy of base classes) and each element is initialized exactly once (except with default array construction). Is there any interest in this class? br, João Abecasis

2 1

signals: vc7.1 warning in named_slot_map.hpp
by Eric Niebler 13 Oct '04

13 Oct '04

This is actually an error for me since I have "warnings as errors" turned on. For the Dinkumware lib, type_info::operator== and operator!= return int instead of bool. This causes problems with the any_bridge_compare class in named_slot_map.hpp template<typename Compare, typename Key> class any_bridge_compare { ... bool operator()(const any& k1, const any& k2) const { if (k1.type() == typeid(front_type)) return k2.type() != typeid(front_type); -------------^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ This results in warning C4800: 'int' : forcing value to bool 'true' or 'false' (performance warning) I recommend changing the line in question to: return !(k2.type() == typeid(front_type)); -- Eric Niebler Boost Consulting www.boost-consulting.com

2 1

Need more Boost.Build files for CodeWarrior?
by Daryle Walker 13 Oct '04

13 Oct '04

I noticed that there are *.jam files for CodeWarrior 8.3, 9.2, and 9.3. I also noticed that there are separate *.jam files for the Linux and Windows-32 versions of Intel's compiler. But CodeWarrior also comes for multiple platforms (Windows and Mac). Shouldn't the CodeWarrior *.jam files be split up as well? (Unless we're certain that CW reacts exactly the same way for the two platforms.) -- Daryle Walker Mac, Internet, and Video Game Junkie darylew AT hotmail DOT com

2 1

Re: [boost] Re: [Poll] New look-n-feel for Boost documentation
by brangdon＠cix.compulink.co.uk 13 Oct '04

13 Oct '04

In-Reply-To: <415CBB84.1050608(a)boost-consulting.com> joel(a)boost-consulting.com (Joel) wrote (abridged): > <http://tinyurl.com/5emyz> > > Serif or sans serif? > For continuous reading in print, serif fonts are generally more > readable than sans serif. However, on the web, the opposite is true. > Serifs are tiny, subtle strokes which, on screen in a small size, > become a rather crude series of little square bitmaps. Their absence > makes the font more readable. On my 1280x1024 desktop machine, the serif on the middle bar of my default Times New Roman 'F' is drawn with 12 pixels and 4 different colours. Maybe the studies you cite were done before anti-aliasing was common? Regardless, I think it should be up to the user. -- Dave Harris, Nottingham, UK

3 2

[scoped_ptr] Invalid example in the documentation.
by Jurko Gospodneti� 13 Oct '04

13 Oct '04

Hi all. The example at the bottom of http://www.boost.org/libs/smart_ptr/scoped_ptr.htm specifies void as the return type for main() which is not valid C++. Could someone please fix this? Thanks, Jurko Gospodnetiæ

1 0

[filesystem] Failures on FAT32
by Stefan Slapeta 12 Oct '04

12 Oct '04

Hi all, there are two failures reported for the intel-win32-8.1 toolset (both in operations_test): http://tinyurl.com/5dbla After some investigation I've found out now that the tests fail only because they are run on a FAT32 disk! It was just coincidence that the failures popped up in the Intel 8.1 tests (...and it's quite amusing to say that we would need another toolset dimension for the filesystem :) ) Anyway, here some analysis (the second failure seems to be a general design problem!): First failure: operations_test.cpp(287): test time_diff >= 0.0 && time_diff < 60.0 failed --> the actual difference is -2! Second failure: std::exception: boost::filesystem::last_write_time ("wrong parameter") last_write_time contains this code: ::utimbuf buf; buf.actime = std::time_t(); ^^^^^^^^^^^^^ buf.modtime = new_time; This means that the last access (!) time is set to 1970-01-01-... when the last write time is changed by this call! IMO that's absolutely incorrect because it's a side effect which I'm sure the user wouldn't expect to happen! Furthermore - a nice coincidence again - it seems not to be allowed to set this early access time for FAT32. I didn't investigate too much, but what I can say for sure is that it works to set an access time of this year, but not for 1970 (-> results in an error "wrong parameter"). Stefan

3 5

as_sequence<R(T0,T1)> ?
by Alexander Nasonov 12 Oct '04

12 Oct '04

I have one addition to '[type_traits] "member_function_pointer_traits" ?' thread started long time ago (29 Jul 2004) by Tobias Schwinger. Is it makes sense to modify as_sequence to convert function type into a sequence? Eg: as_sequence<R (T0,T1)> ---> vector<R,T0,T1> as_sequence<R(*)(T0,T1)> ---> vector<R,T0,T1> as_sequence<R(&)(T0,T1)> ---> vector<R,T0,T1> as_sequence<R(C::*)(T0,T1)> ---> vector<R,C,T0,T1> -- Alexander Nasonov

5 16

Boost.Build V2 link on top-level page?
by Vladimir Prus 12 Oct '04

12 Oct '04

Are there any objection to my adding Boost.Build V2 link (http://boost.org/boost-build2) to the top-level "index.htm", under "Official branch sites", using the patch below? - Volodya

2 3

Review of Daryle Walker's "More IO" library begins today, August 21, 2004.
by tom brinkman 12 Oct '04

12 Oct '04

The review of Daryle Walker's "More IO" library begins today, August 21, 2004. Download: http://groups.yahoo.com/group/boost/files/more_io_4.zip [or] http://boost-sandbox.sourceforge.net/more_io_4.zip Description: Provides a multitude of I/O-oriented extensions. Some are extra manipulators; variants of "std::endl", a resetting manipulator, and a configurable manipulator. The library includes a set of base class templates for wrapping a new stream-buffer type around a stream class. Changes from the last interim version (called "more_io_3b.zip"): * split the manipulator header into several headers * refined the license statements in some already-affected files Changes from the first formal review (called "more_io.zip"): * refined the interface and implementation of array-streams and stream-buffer wrappers (including a wrapping example) * added the null-stream, value-stream, and pointer-stream headers * added generalizations to the new-line and skip-line manipulators * added the non-oriented 'reset' and 'form' manipulators * split the manipulator header into several headers * changed the license statements 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. For information about submitting a Formal Review, see http://www.boost.org/more/formal_review_process.htm The Review manager is: Tom Brinkman reportbase(a)yahoo.com

9 56