- Boost - lists.boost.org

[Boost-bugs] [ boost-Bugs-940941 ] failure in boost jam unit tests on cygwin
by SourceForge.net 23 Apr '04

23 Apr '04

Bugs item #940941, was opened at 2004-04-23 12:45 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=940941&group_i… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Kannan Goundan (cakoose) Assigned to: Nobody/Anonymous (nobody) Summary: failure in boost jam unit tests on cygwin Initial Comment: Boost Jam Version 3.1.9 The unit tests seem to assume that the "/cygdrive" mount exists. I had changed mine to "/drive" and when I tried to build, I got an assertion failure: assertion "self->size < self->capacity" failed: file "strings.c", line 16 self->size == -165761813 self->capacity == 64 backtrace: assert_invariants (strings.c:15) string_free (strings.c:44) var_expand (expand.c:410) var_expand_unit_test (expand.c:696) run_unit_tets (jam.c:197) main (jam.c:299) Even if it's not worth it to accomodate non-standard Cygwin setups such as mine, I wouldn't expect the assertion failure to occur in strings.c. I think this can be reproduced by changing the "/cygdrive/c/foo/bar" string constants to invalid paths (in expand.c on lines 682 and 702) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=940941&group_i… ------------------------------------------------------- This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek For a limited time only, get FREE Ground shipping on all orders of $35 or more. Hurry up and shop folks, this offer expires April 30th! http://www.thinkgeek.com/freeshipping/?cpg=12297 _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

gcc34: undefined reference to `__gcov_init'
by Neal D. Becker 23 Apr '04

23 Apr '04

Any clues? I am trying to rebuild an app that worked with boost_1_31_0 and gcc3.3, now with gcc3.4. I completely rebuilt boost_1_31_0 libs using: PYTHON_ROOT=/usr PYTHON_VERSION=2.3 bjam -sTOOLS=gcc -sGXX=g++34 -sGCC=gcc34 PYTHON_ROOT=/usr PYTHON_VERSION=2.3 bjam -sTOOLS=gcc -sGXX=g++34 -sGCC=gcc34 stage Then I clean out all objects from my build, and rebuilt with g++34, but I got this error: g++34 -Wl,-rpath,/usr/local/src/boost_1_31_0.gcc34/stage/lib,-rpath,./ -o Test2 Test2.o -L/usr/local/src/boost_1_31_0.gcc34/stage/lib -L. -lshannon -lboost_program_options-gcc -lrfftw -lfftw Test2.o(.text+0x7d6e): In function `global constructors keyed to _Z21DesignImpulseResponseRKN10__gnu_norm6vectorISt7complexIdESaIS2_EEE_GCOV': /home/nbecker/shannon/TestAloha/Test2.cc:360: undefined reference to `__gcov_init'

2 1

[serialization] and shared_ptr
by Jeff Flinn 23 Apr '04

23 Apr '04

The following code produces and access violation when loading the NULL shared_ptr. Is this an issue of not having registered the type pointed to? What would I need to do to appropriately handle this situation? #include <boost/serialization/shared_ptr.hpp> #include <boost/serialization/string.hpp> #include <boost/archive/text_oarchive.hpp> #include <boost/archive/text_iarchive.hpp> #include <boost/archive/binary_oarchive.hpp> #include <boost/archive/binary_iarchive.hpp> #include <boost/archive/xml_oarchive.hpp> #include <boost/archive/xml_iarchive.hpp> #include <fstream> typedef std::string tName; class PointedToClass { tName mName; friend class boost::serialization::access; template< class Archive > void serialize( Archive &ar, unsigned int version ) { ar & boost::serialization::make_nvp( "Name", mName ); } public: ~PointedToClass(){} PointedToClass():mName("def"){} }; typedef boost::shared_ptr<PointedToClass> tPtr; class SomeClass { tName mName; tPtr mPtr; friend class boost::serialization::access; template< class Archive > void serialize( Archive &ar, unsigned int version ) { ar & boost::serialization::make_nvp( "Name", mName ); ar & boost::serialization::make_nvp( "Ptr", mPtr ); } public: SomeClass():mName("abc"),mPtr(){} }; int main( int argc, char* argv[] ) { SomeClass lSomeClass; { std::ofstream lOut( "SomeClass.archive", std::ios_base::out | std::ios_base::trunc ); if( lOut.good() ) { boost::archive::xml_oarchive oa( lOut ); oa & boost::serialization::make_nvp( "SomeClass", lSomeClass ); } } { std::ifstream lIn( "SomeClass.archive" ); if( lIn.good() ) { boost::archive::xml_iarchive ia( lIn ); ia & boost::serialization::make_nvp( "SomeClass", lSomeClass ); } } return 0; }

1 0

numeric_cast
by Dill, John 23 Apr '04

23 Apr '04

I am wondering about the use-case of numeric_cast in this sample. unsigned char uchar_max = std::numeric_limits<unsigned char>::max(); char schar_value = 0; try { schar_value = boost::numeric_cast<char>( uchar_max ); } catch ( boost::bad_numeric_cast ) { std::cout << "Overflow occurred..." << std::endl; } When I execute this sample, I don't get the exception. What's the background on this behavior? I'm using gcc 3.3.1. John

5 6

Assignment Library Review Result
by Tom Brinkman 23 Apr '04

23 Apr '04

Assignment Library Review Result Thanks to Thorsten Otteson for creating the Assignment Library. Review Comments: * Participation by boost members in the review was minimal, but the comments were generally constructive. * Considering that library is relatively small and the scope is fairly limited, less than normal review participation by boost members is to be expected. * The basic functionality of the library relieves the c++ developer from typing redundent c++ code for inserting/appending hard-coded data into containers. * Some issues about how the library is organized remain, but are easily resolved by seperating the headers and removing global dependencies. * There are many issues regarding the advanced functionality of this library that were not resolved during the review period. An additional review period should be provided to discuss advanced/optimized techniques for container population. * The name of the library should be changed. The name 'Assignment' does not fully describe the functionality of this library and could be improved. Review Conclusion: This library should be accpeted into boost under the following conditions: 1) Add a header file for each wrapped stl container. One header file containing all of the commonly used headers should also be provided. 2) Remove the global += operator. 3) Rename routines to reflect whether they are initializing, appending or inserting data. 4) Move all routines that extend boost libraries to the examples folder. 5) Documentation should broken up into a basic section and advanced section. 6) Documentation should add a short description about the advantages and disadvantage of each method provided by the library. 7) The library needs to add a boost test file. 8) Routines provided by the Assignment library having boost dependencies will require additional discussion during the post review period. 9) Basic library useage should not require any boost libraries outside of the boost::asignment library headers itself. 10) The techniques provided in the basic functionality of the library may not be optimal. Consideration of techniques for advanced generalized container initialization should be made. A post review period will be required to address advanced library useage. Thanks again and congratulations to Thorsten Otteson for creating a useful set of routines for the boost community. Review Manager, Tom Brinkman __________________________________ Do you Yahoo!? Yahoo! Photos: High-quality 4x6 digital prints for 25� http://photos.yahoo.com/ph/print_splash

1 0

lightweight replacement for boost::format
by John Torjo 23 Apr '04

23 Apr '04

Dear boosters, When needing to dump a lot of data into a string, we usually use boost::format. However, there have been lots of times when I needed a simple and lightweight replacement. I've used one for quite a while (see attachement). Basic usage: str_stream() << "str" << s << "int " << i; // automatic conversion to string. Example: std::string msg = str_stream() << "There have been " << users << " users logged on so far"; Also, attached an example. Any interest in something like this in boost? Best, John <cid:part1.07010200.01010400@torjo.com> ////////////////////////////////////////////////////////////////////// // example.cpp #include "str_stream.hpp" #include <iomanip> std::basic_ostream< wchar_t> & width_4( std::basic_ostream< wchar_t> & out) { out.width( 4); return out; } void print_c_like_str( const char * str) { std::cout << str << std::endl; } void test() { using namespace boost; // for wide strings. std::wstring str = wstr_stream() << std::oct << 8; str = wstr_stream() << std::setfill( L'0') << width_4 << 35 << std::endl; std::wcout << str; // for strings int users = 45; std::string s = str_stream() << "There have been " << users << " users logged on so far"; std::cout << s << std::endl; int words = 78; s = str_stream( "We found ") << words << " words."; std::cout << s << std::endl; // convert it to C-like string print_c_like_str( (str_stream() << "testing " << 1 << 2 << 3).c_str() ); std::cin.get(); } int main() { test(); } ////////////////////////////////////////////////////////////////////// // str_stream.h #ifndef BOOST_STR_STREAM__HPP_JT_2003MAR04 #define BOOST_STR_STREAM__HPP_JT_2003MAR04 // Copyright John Torjo 2003-2004 // Use, modification, and distribution is subject to the Boost Software // License, Version 1.0. (See accompanying file LICENSE_1_0.txt or copy at // http://www.boost.org/LICENSE_1_0.txt) #include <string> #include <sstream> #include <iosfwd> namespace boost { namespace stream_detail { template< class char_type, class char_traits> struct as_c_str_res { typedef std::basic_string<char_type,char_traits> str_type; as_c_str_res( const str_type & str) { m_str = str; } operator const char_type*() const { return m_str.c_str(); } private: str_type m_str; }; } // basic_str_stream - allow stream usage, and then conversion to string template< class char_type, class char_traits = std::char_traits<char_type> > class basic_str_stream { typedef std::basic_stringstream< char_type, char_traits> stringstream_type; typedef std::basic_string< char_type, char_traits> string_type; typedef stream_detail::as_c_str_res<char_type,char_traits> c_like_str_type; public: // default construction basic_str_stream() {} // allow to_string like usage template< class type> basic_str_stream( const type & value) { *this << value; } stringstream_type & underlying_stream() const { return m_out; } // implicit conversion operator string_type() const { return m_out.str(); } // explicit conversion to string string_type str() const { return m_out.str(); } // explicit conversion to C-like string c_like_str_type c_str() const { return c_like_str_type( m_out.str() ); } private: mutable stringstream_type m_out; #ifndef NDEBUG public: void recalculate_string() const { m_string = m_out.str(); } private: mutable string_type m_string; #endif }; // class basic_str_stream typedef basic_str_stream< char> str_stream; typedef basic_str_stream< wchar_t> wstr_stream; template< class char_type, class char_traits, class type> inline const basic_str_stream< char_type, char_traits> & operator<< ( const basic_str_stream< char_type, char_traits> & out, const type & value) { out.underlying_stream() << value; #ifndef NDEBUG out.recalculate_string(); #endif return out; } // allow function IO manipulators template< class char_type, class char_traits> inline const basic_str_stream< char_type, char_traits> & operator<< ( const basic_str_stream< char_type, char_traits> & out, std::ios_base & (*func)( std::ios_base&) ) { func( out.underlying_stream()); return out; } template< class char_type, class char_traits> inline const basic_str_stream< char_type, char_traits> & operator<< ( const basic_str_stream< char_type, char_traits> & out, std::basic_ios< char_type, char_traits> & (*func)( std::basic_ios< char_type, char_traits> &) ) { func( out.underlying_stream()); return out; } template< class char_type, class char_traits> inline const basic_str_stream< char_type, char_traits> & operator<< ( const basic_str_stream< char_type, char_traits> & out, std::basic_ostream< char_type, char_traits> & (*func)( std::basic_ostream< char_type, char_traits> &) ) { func( out.underlying_stream()); return out; } } // namespace boost #endif // End of file

5 10

Date-Time, microsec_time_clock.hpp, bug?
by Val Samko 22 Apr '04

22 Apr '04

What is the type of timeval, used in class microsec_clock? It is not declared anywhere, and thus a compile time error in microsec_time_clock.hpp. Val Samko http://val.digiways.com

2 2

Re: Re: [boost] Serialization Formal Review #2
by Robert Ramey 22 Apr '04

22 Apr '04

Matthias Troyer > On Apr 13, 2004, at 9:42 PM, Robert Ramey wrote: >> Making a new archive class is described in the section "New Archives - >> Implementation". The model for an archive class is: > >> ////////////////////////////////////////////////////////////////////// >> /// >> // class trivial_iarchive - read serialized objects from a input text >> stream >> class trivial_iarchive > >> : public boost::archive::common_iarchive<trivial_iarchive> >> { >> // permit serialization system priledged access to permit >> // implementation of inline templates for maximum speed. >> friend class boost::serialization::load_access; > >> // member template for loading primitive types. >> // Override for any types/templates that special treatment >> template<class T> >> void load(T & t); > >> public: >> ////////////////////////////////////////////////////////// >> // public interface used by programs that use the >> // serialization library > >> // the >>> operator >> template<class T> >> trivial_iarchive & operator>>(T & t){ >> boost::serialization::load(* This(), t); >> return * This(); >> } > >> // archives are expected to support this function >> void load_binary(void *address, size_t count); > >> }; > >> So in theory one has to implement the two undefined functions. > >> For each primitive data type, int, float, etc. or any type designated >> as primitive define a "load" template for function to read them from the >> file. > >> For each data type that you want to treat specially - rather than >> allowing the serialization library to do the job - define an overload >> for operator. > Just a quick question: what should the default load (I mean > template<class T>> void load(T & t);) function do? Do I guess correctly > that it should never be called and is thus undefined to cause link-time > errors? It should handle all primitives not otherwise handled specifically. For example the default load for text archives resolves to input_stream >> t While for binary archives it resolves to load_binary(sizeof(t), t). > Looking through the documentation I find references to virtual > functions: And? >> class trivial_iarchive >> // all input archives must be derived from this base class. This base >> // class defines the virtual functions necessary for the serialization >> // library to handle special types for the serialization system. > I guess that these are incorrect comments left over from an old version? Correct. Robert Ramey

3 2

"typeof" implementation idea
by Arkadiy Vertleyb 22 Apr '04

22 Apr '04

"David Abrahams" <dave(a)boost-consulting.com> wrote > That's the basic idea behind all typeof() emulations that I've ever > seen. They all require some type registration to associate a > compile-time integral constant with a type. The innovation that Steve > brought, IIUC, was that with the registration of only class types, the > rest of the transformations possible in the type system could be > encoded by the library automatically. For example, if you register > class Foo, then the library can generate encodings for Foo*, Foo[2], > Foo**, int (Foo), Foo(*)(Foo,Foo), etc., so you don't have to register > those types. The problem is that those numbers can get very large... Right. What I am even more interested in, is the ability to generate encodings of complicated templates. Say I registered int, std::vector, and mpl::vector2, and the library should be able to work with std::vector<int>, mpl::vector2<std::vector<int>, mpl::vector2<int, int> >, etc. It looks like this can be solved pretty easily. I imagine that Boost.Lambda, for example might also benefit from the ability to encode/decode templates (and maybe Spirit, but I am not sure). > My guess is that manipulating array types in that way has a lower > cost at compile-time than using a vector_c, though using mpl probably > yields much nicer library code and vector_c is more portable. I don't suspect my solution is very compile-time efficient. But I don't have enough knowledge of compilers internals to estimate this. I believe the real advantage is in is simplicity. Anyway, here it is... Let's recall that to achieve our goal we have to: 1) Pass our expression to a function template, like: template<class T> SOMETHING foo(const T&); 2) inside foo() encode our type into a compile-time list of integers; 3) somehow manage to pass this list through the function boundaries; 4) decode the type. The most chalanging is 3. Let's define the following template: template<class N> struct sizer { char_[N::value]; }; The whole purpose of this is to create classes with a given sizeof (to be completely accurate we have to then divide this by sizeof(char)). Next template is what it is all about: template<class IntList> struct multi_int { typedef IntList int_list; template<class T> sizer<typename mpl::apply_if< typename mpl::less<T, typename mpl::size<int_list>::type>, mpl::at<IntList, T>, mpl::identity<mpl::int_<1> > >::type> get(const T&); }; So, if we have an object of this class, x, then sizeof(x.get(mpl::int_<n>())) defines the nth element of the list, and out-of-range values produce 1. The list can be reproduced like, say: #define BOOST_RTL_TYPEITEM(Expr, N)\ mpl::int_<sizeof(Expr.get(mpl::int_<N>()))> mpl::vector<\ BOOST_RTL_TYPEITEM(x, 0) , BOOST_RTL_TYPEITEM(x, 1) ... , BOOST_RTL_TYPEITEM(x, N) > Where it can be generated by the preprocessor for a fairly large N. The reproduced list is larger than the original one, and is 1-padded. The encoding scheme I use does not require to know where the list ends, so this doesn't matter. This is basically it. The return type of the function foo above (sorry for such name) is going to be multi_int<encode<T>::type>, where T is the original type, and encode template works accordingly to some encoding scheme. The encoding scheme to choose is a separate issue. In my example I encode templates by adding the encodings of its parameters to the code of template itself. So, if int is 1, std::vector is 2, and mpl::vector2 is 3, the above example: mpl::vector2<std::vector<int>, mpl::vector2<int, int> > becomes 3 2 1 3 1 1 Also note that all templates with one parameter behave similarly, so only one registration macro is required. Another macro is required to register templates with two parameters, etc. > For what it's worth, I'm pretty sure I know how to solve the problem > that most typeof() implementations strip top-level references. See > boost/iterator/is_lvalue_iterator.hpp for a demonstration. Cool. I imagine pointers are pretty easy, but references surely represent a big problem... I will follow up with the working sketch... Regards, Arkadiy

4 8

thread API
by Christophe Meessen 22 Apr '04

22 Apr '04

Hello, I have axamined the thread_dev header file. Unfortunately the cpp file doesn't seem to correspond. I must admit that the proposed change is a great improvement and removes many objections I had regarding boost thread. Changing the thread object into a handle allows now to copy it. It is then possible to add a thread member variable to a class. A start method can then assign the started thread instance to it. So the gap between boost threads and start&run model gets narrow. The source is one year old. What is the time plan to release it ? -- Bien cordialement, Ch. Meessen

2 1