- Boost-users - lists.preview.boost.org

[quickbook] two links side by side
by Andy Little 19 Jan '06

19 Jan '06

Hi. I'm not sure if this is correct list for quickbook matters. When using two links side by side eg [link x] [link y] in the qbk source, the resulting html puts no space between the two links. Is there a way around this? Quickbook is great BTW ! regards Andy Little

5 5

boost program_options: change program options
by Daniel Weiss 19 Jan '06

19 Jan '06

Hi Is there any possibility to posteriorily change the values stored in the options map read from the config file? I.e.: I have assigned the following option: ( "AutomZoneDetect", po::value<std::string>() ->default_value( "off" ), "To detect zones automatically" ); Now I would like to e.g. set this option to "on" at some point in my code... Greets, Dan! -- Lust, ein paar Euro nebenbei zu verdienen? Ohne Kosten, ohne Risiko! Satte Provisionen f�r GMX Partner: http://www.gmx.net/de/go/partner

3 2

Boost SmartPointer Library
by yinglcs2＠yahoo.com 19 Jan '06

19 Jan '06

Hi, Can I use Boost SmartPointer Library without enabling RTTI in the compiler options? If yes, can you please tell how to do that? Thank you. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 3

Problem with sun studio 11 and mersenne_twister.hpp
by William Deegan 19 Jan '06

19 Jan '06

Any body have a sugguestion on how to fix this error? Thanks, Bill "/home/bdeegan/dev/solaris/ext/boost/boost/include/boost/random/mersenne_twister.hpp", line 240: Error: twist(int) is not a member of boost::random::mersenne_twister<boost::random::UIntType, boost::random::w, boost::random::n, boost::random::m, boost::random::r, boost::random::a, boost::random::u, boost::random::s, boost::random::b, boost::random::t, boost::random::c, boost::random::l, boost::random::val>.

1 0

[multi_array] view-multi_array compatibility in assignments and parameter passing
by Antonio Piccolboni 18 Jan '06

18 Jan '06

I have a 4D multi_array and I define a 3D view on it. I can assign the view to a 3D multi array but I can't pass it directly to a constructor that takes a 3D multi_array. Isn't a 3d view on anything a model of a 3d multi_array? (for the sake of this discussion, element is always double). Code: #include <boost/multi_array.hpp> using namespace boost; class moviva { public: moviva(multi_array<double, 3> m) {} }; main(){ typedef multi_array<double, 4> array_type; typedef array_type::index_range range; multi_array<double, 4> ta4; multi_array<double, 3> ta3; ta3 = ta4[indices[range()][range()][range()][1]]; moviva ma(ta3); // compiles moviva ma1 (ta4[indices[range()][range()][range()][1]]); //does not, line 20 } Compilation view_test.cpp: In function `int main()': view_test.cpp:20: error: no matching function for call to `moviva::moviva( boost::detail::multi_array::multi_array_view<double, 3>)' view_test.cpp:5: error: candidates are: moviva::moviva(const moviva&) view_test.cpp:7: error: moviva::moviva(boost::multi_array<double, 3, std::allocator<double> >) Thanks Antonio

2 2

[multi_index][ann][rfc] Preview of Boost.MultiIndex 1.34 release
by Joaquín Mª López Muñoz 18 Jan '06

18 Jan '06

It is a pleasure for me to announce the availability of a preview version of Boost.MultiIndex as planned for shipping with Boost 1.34, downloadable at the Vault: http://www.boost-consulting.com/vault/index.php?&direction=0&order=&directo… (file multi_index.zip) This version includes several important new features: * New random access indices, which behave like sequenced indices with the added benefit of random access semantics. * Rearrange facilities in sequenced and random access indices, allowing for interoperability with external mutating algorithms. This is IMHO an important feature that can open up new usage scenarios for Boost.MultiIndex. * Several optimizations, of which the most important one relates to ordered indices headers, which are now 4 bytes shorter (on 32 bit systems): this optimization also leads to better performance for large numbers of elements. All in all, the upgrade is very extensive, so I'd appreciate if you test if for backwards compatibility even if you don't plan to use the new features. Additionally, I'd greatly welcome receiving any kind of feedback on the new stuff, the docs (which has been restructured and expanded) and whatever aspect you might think can be improved. I plan to commit this new version to the CVS in a couple of weeks or so, so if you have any comments please bring them here now! Thanks very much for your interest in the library, Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

1 0

<smart_ptr>: A newbie question (about BOOST_SP_USE_QUICK_ALLOCATOR)
by Svaley Streasm 18 Jan '06

18 Jan '06

Hi, I understand that shared_ptr uses the 'quick_allocator' when I compile the library with BOOST_SP_USE_QUICK_ALLOCATOR. But this means that I get the 'quick_allocator' working for every type that I use with shared_ptr, and this bothers me because this seems as a waste of memory for instances of classes that are not frequently used. Besides, the 'quick_allocator' unlike Scott Meyers suggestion (use a pool that can be destroyed) doesn't frees its free blocks which means that, shared_ptr of types that are used only in initialization stage will occupy memory which can not be recycled. Am I missing something? Thank you, Svaley --------------------------------- Yahoo! Photos Ring in the New Year with Photo Calendars. Add photos, events, holidays, whatever.

3 2

[posix_time] truncation warning from VC71
by Dale Wilson 18 Jan '06

18 Jan '06

Hi, (possible duplicate, but I think the original was rejected 'cause of a mail alias. If not, please forgive the noise.) I'm using boost 1.32 posix_time in some code that is intended to be portable (MS VC7.1 / Solaris gcc 3.3.1 / RHLinux gcc 3.3.1). When I build with VC 7.1.3088 on Windows XP Pro SP2 get warnings about integer trunction (see below). I can duplicate it by compiling a cpp file containing a single line: #include "boost/date_time/posix_time/posix_time.hpp" and I can work around it by: #ifdef _MSC_VER #pragma warning(push) #pragma warning(disable:4244) // boost/posix_time has truncation warnings #endif // _MSC_VER #include "boost/date_time/posix_time/posix_time.hpp" //include all types plus i/o #ifdef _MSC_VER #pragma warning(pop) #endif // _MSC_VER but this might hide real problems (or this might *BE* a real problem -- I haven't really looked into the difference between a boost::date_time::counted_time_rep<config>::int_type. and a boost::date_time::gregorian_calendar_base<ymd_type_,date_int_type_>::date_int_type Suggestions? Dale The warnings: c:\Boost\include\boost-1_32\boost\date_time\time_system_counted.hpp(57) : warning C4244: 'initializing' : conversion from 'boost::date_time::counted_time_rep<config>::int_type' to 'boost::date_time::gregorian_calendar_base<ymd_type_,date_int_type_>::date_int_type', possible loss of data with [ config=boost::posix_time::millisec_posix_time_system_config ] and [ ymd_type_=boost::gregorian::greg_year_month_day, date_int_type_=boost::date_time::int_adapter<unsigned long>::int_type ] c:\Boost\include\boost-1_32\boost\date_time\time_system_counted.hpp(52) : while compiling class-template member function 'boost::date_time::counted_time_rep<config>::date_type boost::date_time::counted_time_rep<config>::date(void) const' with [ config=boost::posix_time::millisec_posix_time_system_config ] c:\Boost\include\boost-1_32\boost\date_time\time_system_counted.hpp(111) : see reference to class template instantiation 'boost::date_time::counted_time_rep<config>' being compiled with [ config=boost::posix_time::millisec_posix_time_system_config ] c:\Boost\include\boost-1_32\boost\date_time\time.hpp(52) : see reference to class template instantiation 'boost::date_time::counted_time_system<time_rep>' being compiled with [ time_rep=boost::posix_time::int64_time_rep ] c:\Boost\include\boost-1_32\boost\date_time\posix_time\ptime.hpp(32) : see reference to class template instantiation 'boost::date_time::base_time<T,time_system>' being compiled with [ T=boost::posix_time::ptime, time_system=boost::posix_time::posix_time_system ] c:\Boost\include\boost-1_32\boost\date_time\date_parsing.hpp(211) : warning C4244: 'argument' : conversion from 'std::allocator<_Ty>::value_type' to 'char', possible loss of data with [ _Ty=wchar_t ] c:\Boost\include\boost-1_32\boost\date_time\date_parsing.hpp(253) : see reference to function template instantiation 'date_type boost::date_time::from_stream_type<date_type,std::basic_string<_Elem,_Traits,_Ax>::iterator>(iterator_type &,iterator_type &,wchar_t)' being compiled with [ date_type=boost::gregorian::date, _Elem=wchar_t, _Traits=std::char_traits<wchar_t>, _Ax=std::allocator<wchar_t>, iterator_type=std::basic_string<wchar_t,std::char_traits<wchar_t>,std::allocator<wchar_t>>::iterator ] c:\Boost\include\boost-1_32\boost\date_time\gregorian\parsers.hpp(78) : see reference to function template instantiation 'boost::date_time::period<point_rep,duration_rep> boost::date_time::from_simple_string_type<boost::gregorian::date,wchar_t>(const std::basic_string<_Elem,_Traits,_Ax> &)' being compiled with [ point_rep=boost::gregorian::date, duration_rep=boost::gregorian::date_duration, _Elem=wchar_t, _Traits=std::char_traits<wchar_t>, _Ax=std::allocator<wchar_t> ] -- ----------------------------------------------------- Dale Wilson, Senior Software Engineer Object Computing, Inc. (OCI) http://www.ociweb.com/ http://www.theaceorb.com/ ----------------------------------------------------

2 1

Boost Math Library
by yinglcs2＠yahoo.com 17 Jan '06

17 Jan '06

Hi, Does Boost Math Library support Statistic Calculation? (e.g. median, std deviation, etc)? >From here, it does not appear Boost Math library calculate has statistic algorithm. If not, can someone please recommend some c/c++ library which does statistics? Thank you. http://www.boost.org/libs/libraries.htm#Algorithms Math and numerics * math - Several contributions in the domain of mathematics, from various authors. * numeric/conversion - Optimized Policy-based Numeric Conversions, from Fernando Cacciola. * integer - Headers to ease dealing with integral types. * interval - Extends the usual arithmetic functions to mathematical intervals, from Guillaume Melquiond, Hervé Brönnimann and Sylvain Pion. * math/common_factor - Greatest common divisor and least common multiple, from Daryle Walker. * math/octonion - Octonions, from Hubert Holin. * math/quaternion - Quaternions, from Hubert Holin. * math/special_functions - Mathematical special functions such as atanh, sinc, and sinhc, from Hubert Holin. * multi_array - Multidimensional containers and adaptors for arrays of contiguous data, from Ron Garcia. * operators - Templates ease arithmetic classes and iterators, from Dave Abrahams and Jeremy Siek. * random - A complete system for random number generation, from Jens Maurer. * rational - A rational number class, from Paul Moore. * uBLAS - Basic linear algebra for dense, packed and sparse matrices, from Joerg Walter and Mathias Koch. __________________________________________ Yahoo! DSL Something to write home about. Just $16.99/mo. or less. dsl.yahoo.com

7 17

Serialization of static member variables?
by Joseph Turian 17 Jan '06

17 Jan '06

Hi, If see from the serialization documentation that if I serialize a pointer more than once, only one instance will appear in the archive. However, what about static member variables? Will they only be serialized once, even if I serialize multiple objects of the class type? e.g. class foo { private: int i; static int j; friend class boost::serialization::access; template<class Archive> void serialize(Archive& ar, const unsigned int version) { ar & i; ar & j; // Will j be serialized multiple times, i.e. once per foo instance? } }; Thanks, Joseph -- http://www.cs.nyu.edu/~turian/

2 3