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

Re: thread lib using workshop CC on solaris
by Christopher Currie 11 Apr '03

11 Apr '03

I tried to send this earlier using the newsgroup, but it seems to have been dropped on the floor. Sorry for the duplicate if it shows up. The latest version of boost has some support for some versions of this compiler. The appropriate jamfile is "sunpro-tools.jam" (Sunpro is an old name for this compiler.) Thus: cd $BOOST_ROOT/libs/thread/build bjam -sTOOLS=sunpro That said, your mileage may vary on this compiler. I have found that it is notoriously buggy, especially wrt templates, and boost code will often cause it heartache in obscure ways. My results have found: * Up-to-date patches for the compiler and the operating system are a must. Find them here: http://access1.sun.com/sundev/index.html * Both versions of this compiler that I have tested have issues with Boost.TypeTraits, generating loads of spurious "Anacronism" warnings wrt the typename keyword being absent or present. Unfortunately, sun has not provided a flag to silence these warnings, and adding typename to the locations it complains about breaks other compilers, notably g++. * Both versions of this compiler will have problems linking some Boost unit tests, due to odd template RTTI issues. Adding -sBUILD="<cxxflags>-instances=static" will sometimes fix this problem. I don't recommend making this flag a default, because of the code bloat that entails. * Sun CC 5.4 ( Workshop/Forte Developer/SunOne Studio 7 ) will successfully build Boost.Threads. * Sun CC 5.3 update 2 ( W/FD/SOS 6u2 ) will only build Boost.Threads in release mode. This compiler generates assertions when attempting to compile the debug libraries. * I have not tested any versions earlier than Workshop 6 update 2. "jenny_qzhang" <jenny_qzhang(a)yahoo.com> wrote in message news:b722dr+7f4@eGroups.com... > Hi, All > > I am working on porting an application from MSVC to solaris > workshop(the applicatoin is using boost thread lib). I could not > locate the makefile or jam file for this compiler. Is there anybody > did the same thing before? > > If you finially made it, can you share your experience, makefile > with me? Actually I tried to write a makefile myself, but it reported > a lot of errors related to template parameters :(. > > > Thanks very much! > > Qiu

1 0

Problems with iterator_adaptors
by Olaf Petzold 11 Apr '03

11 Apr '03

Hello, I try to write a cyclic Iterator using boost::iterator_adaptors. Unfortunally, the advance function doesn't work for negative distances correct: template<class Iterator> class cycle_iterator_policies { public: cycle_iterator_policies(const Iterator& begin, const Iterator& end) : m_begin( begin ), m_end( end ) { assert( m_begin != m_end ); } .... template<class IteratorAdaptor, class DifferenceType> void advance( IteratorAdaptor& x, DifferenceType n ) { n %= std::distance( m_begin, m_end ); DifferenceType rest = std::distance( x.base(), m_end ); if( n < rest ) std::advance( x.base(), n ); else std::advance( x.base() = m_begin, n - rest ); } .... private: Iterator m_begin; Iterator m_end; }; It seems to be an algorithmic problem for me. How can I corrected it? Thanks Olaf

1 0

Signals and noncopyable
by svanechel 11 Apr '03

11 Apr '03

Hi, Is there a reason why siganls aren't copyable? As far as I can tell signal base derives from noncopyable, but it references its implementation using shared_ptr. So I'm guessing in theory a signal is perfectly copyable. I must admit I came to this conclusion by briefly looking at the code, so I might be completely wrong. I want to store signals into a vector of function<void()>'s, together with bound arguments, to capture events and replay them later. Something similar to (simplified): class recorder { public: // this is the handler for some event // it is connected to another signal void some_event( int i) { events_.push_back( bind( ev, i ) ); } void replay() { vector< function<void()> >::const_iterator itr = events_.begin(); while ( itr != events_.end() ) { (*itr)(); ++itr; } } signal<void(int)> ev; private: vector< function<void()> > events_; }; recorder rec; // connect the recorder to the signals is uses ... // now replay the events rec.ev.connect( some_handler ); rec.replay(); The example above may no be entirely correct since I'm coding this directly without running it through a compiler, but I hope the intent is clear. If I remove the derivation from noncopyable from signal_base, a sigal can be assigned to a function, although I haven't tested it yet to see if it actually works (currently I do not have something I can start testing with). Is it safe to remove the noncopyable base class? If so can it be done in the next release of the boost distribution as well? Thanks in advance, Sven Van Echelpoel

1 0

Problem with boost::pool_alloc
by Ilya Chvetsov(work) 11 Apr '03

11 Apr '03

Hi! I try to use boost::pool_alloc with STLport-4.5-0119 snapshot. STLPort call pool_alloc::allocate(const size_type n) with n = 0. STLPort naitive allocator returns in such case NULL, but pool_alloc tries return memory. Method simple_segregated_storage<SizeType>::try_malloc_n( void * & start, size_type n, const size_type partition_size) has problem too if parameter n is 0. Problem is in while condition: while (--n != 0)... This simple program demonstrates a problem: #include <boost/pool/poolfwd.hpp> #include <boost/pool/pool_alloc.hpp> typedef boost::pool_allocator<int> alloc_t; int main(int argc, char* argv[]) { alloc_t alloc; alloc.allocate(0); alloc.allocate(0); alloc.allocate(0); alloc.allocate(0); alloc.allocate(0); alloc.allocate(0); alloc.allocate(0); alloc.allocate(0); alloc.allocate(0); alloc.allocate(0); alloc.allocate(0); alloc.allocate(0); alloc.allocate(0); alloc.allocate(0); alloc.allocate(0); alloc.allocate(0); alloc.allocate(0); alloc.allocate(0); alloc.allocate(0); alloc.allocate(0); alloc.allocate(0); alloc.allocate(0); alloc.allocate(0); alloc.allocate(0); alloc.allocate(0); alloc.allocate(0); alloc.allocate(0); alloc.allocate(0); alloc.allocate(0); alloc.allocate(0); alloc.allocate(0); alloc.allocate(0); alloc.allocate(0); alloc.allocate(0); alloc.allocate(0); alloc.allocate(0); return 0; } How can I solve this problem? Thanks -Ilya

1 0

Boost random's min < max assert
by Glen Knowles 10 Apr '03

10 Apr '03

Uniform int contains an assert if min < max. If I ask for a random between 1 and 1 I'm expecting a 1, not an assert. Is there some reason this was deemed inappropriate? Thanks, Glen [Non-text portions of this message have been removed]

3 2

preprocessor: convert to capitals
by Toon Knapen 10 Apr '03

10 Apr '03

In the ublas forum we're having a discussion on the best way to provide signatures in C for fortran libraries (like BLAS and LAPACK). For linking C with fortran, you sometimes need to add an underscore to the function in C, but on other platforms fortran will store the function-name in capitals. Thus on different platforms, we should preprocess our source to take the platforms' convention into account and we thus would need a macro to convert an identifier automatically to uppercase. Is that possible ? toon -- Toon Knapen http://www.fft.be Free Field Technologies tel:+32 10 45 12 26 16 Place de l'Universite fax:+32 10 45 46 26 1348 Louvain-la-Neuve http://www.femtown.org Belgium

3 5

thread lib using workshop CC on solaris
by jenny_qzhang 10 Apr '03

10 Apr '03

Hi, All I am working on porting an application from MSVC to solaris workshop(the applicatoin is using boost thread lib). I could not locate the makefile or jam file for this compiler. Is there anybody did the same thing before? If you finially made it, can you share your experience, makefile with me? Actually I tried to write a makefile myself, but it reported a lot of errors related to template parameters :(. Thanks very much! Qiu

2 2

ublas matrix slice bug?
by Stephan Puchegger 08 Apr '03

08 Apr '03

Dear ublas developers! (I am using boost 1.30 & gcc 3.2) the following program: #include <boost/numeric/ublas/matrix.hpp> #include <boost/numeric/ublas/io.hpp> int main () { using namespace boost::numeric::ublas; matrix<double> m (4, 4); for (unsigned int i = 0; i < m.size1 (); ++ i) for (unsigned int j = 0; j < m.size2 (); ++ j) m(i, j) = 1; std::cout << m << std::endl; // multiply a slice of the matrix with 2.... project (m, slice (2, 1, m.size1()-2), slice (1, 0, m.size1()-2)) *= 2; // interesting result ... the slice has been multiplied with 4 std::cout << m << std::endl; } gives the following output: [4,4]((1,1,1,1),(1,1,1,1),(1,1,1,1),(1,1,1,1)) [4,4]((1,1,1,1),(1,1,1,1),(1,4,1,1),(1,4,1,1)) Why is the slice multiplied with 4 and not with 2?? Do I make some fundamental mistake? Everything works fine if I am using a matrix_vector_slice. My second (stupid?) question is the following: Is it intentional, that it is not possible to compile: #include <boost/numeric/ublas/matrix.hpp> #include <boost/numeric/ublas/io.hpp> int main () { using namespace boost::numeric::ublas; matrix<double> m (4, 4); for (unsigned int i = 0; i < m.size1 (); ++ i) for (unsigned int j = 0; j < m.size2 (); ++ j) m(i, j) = 4*i+j; std::cout << m << std::endl; swap(row(m,0), row(m,2)); std::cout << m << std::endl; } whereas matrix_row<matrix<double> > l(m, 0); matrix_row<matrix<double> > r(m, 2); swap(l, r); /* swap the rows */ works fine. MTL has support for a similar syntax: swap(rows(m)[0], rows(m)[2]); best regards and thanks for your help! Stephan

3 7

Spirit PDF or something
by Edward Diener 08 Apr '03

08 Apr '03

I would like to print out the Spirit documentation as a whole for offline study. However Boost 1.30 Spirit documentation comes as a series of HTML pages. Is there an easy way to print out the documentation rather than cycling through all of it manually and printing out a page at a time ?

2 3

condition::wait() - Alertable in Win32
by Simon Bailey 08 Apr '03

08 Apr '03

What is the latest thinking on making condition::wait() and condition::timed_wait() "alertable" in the Win32 environment? Please consider this a "me too" request for such a feature! I'm trying to implement a cross-platform (Unix, Windows) implementation of a Proactor pattern that manages asynchronous sockets. It seems that the way to implement this pattern with as much code common to both platforms as possible is to use 1. Overlapped sockets that call back (not post messages) in Windows. 2. Signals in Unix (similar to the Windows call backs but with less- clear semantics in my mind). For this scheme to work, the wait functions need to be alertable in Windows, but the Unix system shouldn't need any changes. >From the research that I have done so far, in my particular case, I would only need wait and timed_wait to be alertable, and it would be appropriate that they were always altertable - I would not need a way to enable or disable this feature.

1 0