June 2006 - Boost - lists.preview.boost.org

[timer] throwing constructor?
by Gennaro Prota 07 Jun '06

07 Jun '06

Hi guys, just thought to resurrect the following old post http://article.gmane.org/gmane.comp.lib.boost.devel/100829 Opinions? --Gennaro.

2 2

Re: [boost] [Review][PQS] Physical Quantities System review (May31through June 9)
by Martin Bonner 07 Jun '06

07 Jun '06

----Original Message---- From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] On Behalf Of Paul Giaccone Sent: 07 June 2006 12:20 To: boost(a)lists.boost.org Subject: Re: [boost] [Review][PQS] Physical Quantities System review (May31through June 9) > Andy Little wrote: >> Hi Paul, >> >> "Paul A Bristow" <pbristow(a)hetp.u-net.com> wrote in message >> news:E1FneN9-00014T-OY@he303war.uk.vianw.net... >> >>> 4 It isn't immediately obvious to me how to ensure output in SI >>> 'engineering' multiples, depending on the value. >>> For example, 0.123 m outputs as 1.23 mm, but 1234.5 m outputs as >>> 1.2345 km. >>> > > ...and this point too: 0.123 m = 123 mm or 1.23 decametres (but not > 1.23 mm), so either the above is a bug or incorrectly transcribed. <nit> 0.123 m = 1.23 decimetres = 0.0123 decametres. </nit> You can see why SI deprecated deca and deci. :-) -- Martin Bonner Martin.Bonner(a)Pitechnology.com Pi Technology, Milton Hall, Ely Road, Milton, Cambridge, CB4 6WZ, ENGLAND Tel: +44 (0)1223 203894

2 1

[review] Fusion Library Accepted
by Ronald Garcia 07 Jun '06

07 Jun '06

Dear All, I am pleased to announce that the Fusion compile-time/run-time hybrid heterogeneous container and algorithm library by Joel de Guzman and Dan Marsden has been accepted into Boost. The library received 7 YES votes and 0 NO votes, with one abstention. Detailed Review Comments ------------------------ The following comments refer to issues that the library authors should address prior to merging the library into CVS: * Documentation: Many of the reviewers stated that they would like to see more tutorial documentation that demonstrates not only what the particular constructs in Fusion do, but also how they are expected to be used. A reasonably concise motivating example has been requested. It has already been pointed out that Fusion is used for some other boost libraries. A well-developed and self-contained case study of when and how to use Fusion would be greatly appreciated. The relationship between this library and the current Boost.Tuple library, as well as Boost.Mpl, should be discussed. The reference documentation is quite thorough and detailed comments regarding them have already been addressed by the authors. However the notion of "views" requires greater documentation. The examples in the algorithm sections currently do little more than demonstrate the syntax by which they can be called. Examples that more specifically express intent would be a notable improvement. (see for example Matt Austern's "Generic Programming and the STL"). In general the documentation would benefit from copy-editing. * Several commented on the use of the name "pair" for the fusion type that has typedefs for two types but only contains the second type. Although the typedefs and member names are consistent with the std::pair object, the name "pair" is confusing. The compile-time/run-time hybrid nature of this library makes it difficult to find perfect metaphors for constructs in the library. In this case, it seems better to find a term for this template (and the concept that it models) that more directly states its purpose. The name "tag_of" would also benefit from renaming. * The behavior of Fusion functions in the face of argument-dependent lookup (ADL) is not well specified. This should be made explicit in the reference documentation. The following comments refer to issues that, while not mandatory, deserve consideration: * The library name "Fusion", though not arbitrary, says little about the library's purpose. There is precedent for this within boost, however. A name change is not mandatory for the library's acceptance, but it would be worth while for the authors to consider a more telling name. * The mechanism for extending Fusion with new containers and iterators is complex and involves implementing a number of components, especially regarding iterators. An adaptation layer that is analogous to the Boost.Iterator library would be a fine addition to Fusion. * It would be beneficial to supply Boost.Serialization support for the Fusion container types. I am sure, as mentioned, that the authors of this library would accept a volunteer to implement this functionality. I would like to thank all the people who reviewed the library, voted, and otherwise participated in the discussion. Congratulations to Joel and Dan and I look forward to seeing Fusion in the Boost CVS soon. Ron Garcia

6 9

[range] calling front() on iterator_range of const elements
by Valentin Samko 06 Jun '06

06 Jun '06

Is it intentional that one can not call range.front() on an iterator range of const values? #include <boost/range/iterator_range.hpp> int main() { typedef const char* iterator; iterator p = "test"; boost::iterator_range<iterator> range(p, p+1); range.front(); } This fails to compile as value_type& front() const { ... return *m_Begin; } in iterator_range.hpp tries to bind a const char lvalue to a non const reference. The same happens with back() and operator[]. The fix is to return typename std::iterator_traits<IteratorT>::reference and not value_type& Thanks, Valentin

2 1

[io] [RC_1_34_0] Borland fix broke I/O lib
by Markus Schöpflin 06 Jun '06

06 Jun '06

Since the last borland fix the ios_state_unit_test is failing for _every_ toolset on the release branch. Please revert the check-in or fix it. Markus <rant> PS: Why do this sort of errors happen? I would think that anyone checking in something on the release branch keeps an eye open if this is causing major breakage. </rant>

3 2

[Review][PQS] Review from Bill Myers
by fred bertsch 06 Jun '06

06 Jun '06

With Bill's permission, I'm forwarding his review to the list. -Fred ---------- Forwarded message ---------- From: Bill Myers <wlmyers at stellarscience dot com> Date: Jun 6, 2006 10:14 AM Subject: Review of Andy Little's Physical Quantities System To: fred.bertsch(a)gmail.com Cc: Andy Little <andy(a)servocomm.freeserve.co.uk> == Summary: recommend accept. Please! :-) == Design: My perspective is a component user; I have little expertise in constructing boost-level-of-sophistication components. The user API is fine. == Implementation: I've compiled and run all the pqs example programs. They compile with no warnings and execute correctly. I've added a user-defined t1_quantity, fluence. I did this before documentation was available; Andy was cheerfully helpful in walking me through the steps, but it's daunting for the casual user (as Andy notes in the documentation). == Documentation: The PDF version of the document has considerable content, with a few editorial issues (typography, spelling, and such). I spent a couple of hours reading through all of it; I found it no more dense than existing boost component documentation, and certainly more up-to-date than some of them (unit test). == Usefulness: PQS fills a critical need for which there is no alternative C++ solution. Even though some may regard the present implementation as incomplete (Andy himself notes important TODOs), I believe that it is very useful as it now stands, and I need a "stamp of approval" so that I can begin introducing it into our scientific analysis projects. == Background: My platform is Apple (gcc 4.0.1, Mac OS X 10.4.6). I'm using boost 1_33_1 obtained via darwinports. My coworkers are pretty much all on WindowsXP with VisualStudio -- anything I create has to work on that platform; they are also using boost 1_33_1. I've been experimenting with pqs since January 2005, although none of our code can depend on pqs until it becomes a formal boost library. Bill Myers

1 0

[BGL] [concept_check] new naming convention
by Cromwell Enage 06 Jun '06

06 Jun '06

I've tracked down the cause of my errors wrt kruskal_minimum_spanning_tree. Recently the Boost Concept Checking Library adopted a new naming scheme, deprecating those classes whose names that have the "Concept" suffix in favor of the corresponding classes without the suffix. AFAICS the BGL algorithms are still using the concept checking classes with the old names, which should be okay until a future release removes the old classes. The problem lies in <boost/concept/detail/concept_def.hpp>, line 26: the ctor that was supposed to satisfy GCC 3.4.4 is fouling up my own compiler, GCC 3.4.2 (MinGW). The ideal solution would be to update the BGL algorithms to use the new naming scheme. Cromwell D. Enage __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 1

Boost and gcc4?
by jmzorko＠mac.com 06 Jun '06

06 Jun '06

Hello, all ... I searched in the old ActiveState message archive, but didn't find anything about this. When I compile my Boost experiments with gcc3.3, everything seems to be fine; when I compile them with gcc4, however, I get things like this (from the simple_ls example): pugsleybutt:~/devstuff/c++/boost jmzorko$ ./simple_ls usage: simple_ls [path] In directory: /Users/jmzorko/devstuff/c++/boost filesystem simple_ls(27587) malloc: *** Deallocation of a pointer not malloced: 0x2801b18; This could be a double free(), or free() called with the middle of an allocated block; Try setting environment variable MallocHelp to see tools to help debug filesystem.cpp simple_ls(27587) malloc: *** Deallocation of a pointer not malloced: 0x2801d00; This could be a double free(), or free() called with the middle of an allocated block; Try setting environment variable MallocHelp to see tools to help debug simple_ls simple_ls(27587) malloc: *** Deallocation of a pointer not malloced: 0x2801b00; This could be a double free(), or free() called with the middle of an allocated block; Try setting environment variable MallocHelp to see tools to help debug simple_ls.cpp simple_ls(27587) malloc: *** Deallocation of a pointer not malloced: 0x2801ce0; This could be a double free(), or free() called with the middle of an allocated block; Try setting environment variable MallocHelp to see tools to help debug 4 files 0 directories 0 errors pugsleybutt:~/devstuff/c++/boost jmzorko$ The Boost version is 1.31 and my platform is Mac OSX 10.4.6 (PowerPC), if that matters ... i'd like to use gcc4 if possible, can anyone tell me how to achieve this? Regards, John Falling You - exploring the beauty of voice and sound http://www.fallingyou.com

5 7

[timer] throwing constructor?
by Gennaro Prota 06 Jun '06

06 Jun '06

{Note: this could be a duplicated post; I already sent this message on June 5 but that copy hasn't appeared yet} Hi guys, just thought to resurrect the following old post http://article.gmane.org/gmane.comp.lib.boost.devel/100829 Opinions? --Gennaro.

1 0

[log] __FILE__ & __LINE__
by Loïc Joly 06 Jun '06

06 Jun '06

Sorry for posting a question about a non-accepted (yet, I hope) library, but I desperately need to introduce some logging in my application, and cannot wait, so I try to use the current version, which is still the most interesting one I've seen so far... Is there any way to get __LINE__ or __FILE__ written as a modifier for a log? Best regards, -- Loïc

1 0