- Boost - lists.boost.org

Re: [boost] program_options with mingw
by Janusz Piwowarski 18 Jun '04

18 Jun '04

Janusz Piwowarski wrote: > BTW, i successfully compile program_options library and examples with > stlport 4.6.2; but my program, where i use boost::thread, don't want to > link. Sorry, i check it now - examples also don't link. Regards, Janusz

2 2

program_options with mingw
by Janusz Piwowarski 18 Jun '04

18 Jun '04

Hello, I attach a patch that allows use of program_options with mingw compiler. There isn't support for utf-8 conversion - maybe it is possible to convert without use of wstring? Regards, Janusz

3 5

Boost.Test
by Jagmohan S Nanaware 18 Jun '04

18 Jun '04

Hi, Is it possible to just carve out Boost.test package separately from entire Boost? regards, Jagmohan

2 1

Documentation
by David B. Held 18 Jun '04

18 Jun '04

Ok, if the Boost style documentation is too simple, and docs like Spirit are too cute, what is a nice, happy median? If we're going to demand uniformity in licensing, should we also demand more uniformity in documentation? I think a single documentation style across Boost would make it even easier to learn new libraries. I recently found it very difficult to find the information I wanted about the Boost.Test library, as well as Boost.Preprocessor. What can be done about these issues? Dave --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com) Version: 6.0.701 / Virus Database: 458 - Release Date: 6/7/2004

8 20

physical quantities
by Andy Little 17 Jun '04

17 Jun '04

The next version of my physical quantities libary pqs-1-01-04 is available on my site at: http://www.servocomm.freeserve.co.uk/Cpp/pqs-1-01-04/download.html The original type has now been augmented by another. The original type has now been renamed as a 'ct-quantity' representing a physical quantity whose units cannot be modified at run-time. The other type is the 'rt-quantity', whose units can be modified at run-time. The two types are of course compatible and the rt-quantity in particular is useful for further derivation, for instance into a physical quantity whose units can be set and interrogated via strings ie "mm, kgf" etc of which there is an example in the examples directory. The first question many will ask about such a library is : "How does the run-time speed/memory performance compare with using inbuilt types?." That is an important question, but to me not the most important one. (The answer is that this is implementation dependent and the current implementation is not optimal) Having used the library for some time its power seems to lie in the fact that it models a concept quite accurately from a programmers point of view. IOW what you can do with the type is restricted (by the compiler) to (some subset of) the entity that it models. The reason that this is powerful is difficult to define, but can be summed up in the saying: " a picture is worth a thousand words" I now see more clearly what those who wanted to see currency conversion and number of apples per kumquat or whatever where driving at. However these are not physical-quantities. C++ does have the ability to express those concepts, but they lie outside the remit of the concept that this library models. Nontheless such concepts would be useful. So in a network model a byte, packet etc would be a concept which would be modelled by a C++ type. Strongly enforcing the rules by which entities interact is satisfying , I guess, because it clarifies the mental picture of a program. Modelling everything by a double or an int (should number_of_bytes_received be convertible to double ... probably not etc) means everything is mush. So on a personal note designing the library has been very rewarding. As I spend much time GUI programming, it strikes me that the next useful concepts are those of model-space, view-space, paper-space etc. Here a point in space would be represented by different types which could only exist in the relevent space, but have the intelligence to perform transforms from one space to another. Similarly where one is modelling (say) magnetic flux density at a point x, y, z , the role of the view-space would be to convert form the entity in model-space to 'some representation ' in the view-space or the paper-space. The obvious candidates for the types in model-space being the ct-quantity of course. regards Andy Little

2 3

Using the Boost license
by Geoff Leyland 17 Jun '04

17 Jun '04

Hi, I have a couple of small libraries I'm "releasing" to a few other people (well, anybody really, but so far only a few). Can I use the BSL on my software even though it's not part of boost? Do I have to make any changes? thanks for your time, Geoff

2 2

RE: [boost] Re: static sized strings (non-virtual implementation)
by Reece Dunn 17 Jun '04

17 Jun '04

John Nagle wrote: >That's a much better approach than the previous one. >It's sound C++, and it's simple. >All the operations go in string_base. fixed_string >need only allocate space. I have now checked in a working implementation of the approach I suggested. It uses a trick to pass the information to the implementation via the basic_string_impl class and has a complicated implementation of swap (non-virtual :)!). The only functions not available to [w]char_string are substr and +, but these are available in fixed_string itself. I have also fixed the problems with fsstring.hpp and Borland, since Borland may make strcpy, etc macro functions to its intrinsic versions (__strcpy__, etc.) Regards, Reece _________________________________________________________________ Want to block unwanted pop-ups? Download the free MSN Toolbar now! http://toolbar.msn.co.uk/

1 0

type_traits for checking derived type
by D-Swat 17 Jun '04

17 Jun '04

Hi, some code: template <typename DerivedT> class A { BOOST_STATIC_ASSERT((boost::is_convertible<A<DerivedT>*, B*>::value)); [...] }; class B : public A<B> { }; I want to check if the template parameter really specifies a derived type. But the assert is always false. How can i solve this? bye

5 5

Re: Boost Digest, Vol 756, Issue 1
by Eric Ford 17 Jun '04

17 Jun '04

> The next version of my physical quantities library pqs-1-01-04 is > available on my site at: > > http://www.servocomm.freeserve.co.uk/Cpp/pqs-1-01-04/download.html > ... Andy, Thank you for your work on this very important area of development. From just quickly looking at the examples, it appears that you choose to use different types for quantities that have the same dimensions but different units. I don't think that is a good idea. You can search the archives for the discussions several of us had about similar issues, mostly a few years ago. If you still disagree, I'd like to hear why. Perhaps, you could summarize the main similarities and difference between your library and other similar libraries. For example, there's Walter Brown's SIUnits, as well as a couple of drafts that have been uploaded to the boost vault. I know I posted ebf_units a while back to give people something to work from. And I believe there were one or two others there as well. Thanks, Eric

2 1

applied patch to boost::tuple
by Toon Knapen 17 Jun '04

17 Jun '04

I just applied the patch below to boost/tuple/detail/tuple_basic.hpp to port it to IBM/VisualAge. I tried to contact Jaako Jarvi but the email address listed in the copyright statement is not valid anymore ;-( Index: tuple_basic.hpp =================================================================== RCS file: /cvsroot/boost/boost/boost/tuple/detail/tuple_basic.hpp,v retrieving revision 1.23 retrieving revision 1.24 diff -u -r1.23 -r1.24 --- tuple_basic.hpp 28 Oct 2003 09:42:43 -0000 1.23 +++ tuple_basic.hpp 17 Jun 2004 07:01:13 -0000 1.24 @@ -43,6 +43,8 @@ #include "boost/type_traits/cv_traits.hpp" #include "boost/type_traits/function_traits.hpp" +#include "boost/detail/workaround.hpp" // needed for BOOST_WORKAROUND + namespace boost { namespace tuples { @@ -97,12 +99,22 @@ template<class RET, class HT, class TT > inline static RET get(const cons<HT, TT>& t) { +#if BOOST_WORKAROUND(__IBMCPP__,==600) + // vacpp 6.0 is not very consistent regarding the member template keyword + // Here it generates an error when the template keyword is used. + return get_class<N-1>::get<RET>(t.tail); +#else return get_class<N-1>::BOOST_NESTED_TEMPLATE get<RET>(t.tail); +#endif } template<class RET, class HT, class TT > inline static RET get(cons<HT, TT>& t) { +#if BOOST_WORKAROUND(__IBMCPP__,==600) + return get_class<N-1>::get<RET>(t.tail); +#else return get_class<N-1>::BOOST_NESTED_TEMPLATE get<RET>(t.tail); +#endif } }; @@ -194,11 +206,17 @@ typename element<N, cons<HT, TT> >::type >::non_const_type get(cons<HT, TT>& c BOOST_APPEND_EXPLICIT_TEMPLATE_NON_TYPE(int, N)) { - return detail::get_class<N>::BOOST_NESTED_TEMPLATE +#if BOOST_WORKAROUND(__IBMCPP__,==600 ) + return get_class<N>:: +#else + return get_class<N>::BOOST_NESTED_TEMPLATE +#endif get< typename access_traits< typename element<N, cons<HT, TT> >::type - >::non_const_type>(c); + >::non_const_type, + HT,TT + >(c); } // get function for const cons-lists, returns a const reference to @@ -209,11 +227,17 @@ typename element<N, cons<HT, TT> >::type >::const_type get(const cons<HT, TT>& c BOOST_APPEND_EXPLICIT_TEMPLATE_NON_TYPE(int, N)) { +#if BOOST_WORKAROUND(__IBMCPP__,==600) + return detail::get_class<N>:: +#else return detail::get_class<N>::BOOST_NESTED_TEMPLATE +#endif get< typename access_traits< typename element<N, cons<HT, TT> >::type - >::const_type>(c); + >::const_type, + HT,TT + >(c); } // -- the cons template --------------------------------------------------

2 1