- Boost-users - lists.boost.org

multi_array iterators ??
by dbkita 27 Mar '03

27 Mar '03

I am intersted in a simple way to iterate on a multi_array (or better yet a multi_array_view) regardless of dimension or ranges or order of access. I suppose for the entire multi_array one can use the data() method to return a T* and step through the contiguous memory block. But the case for a multi_array_view doesn't not seem nearly so simple taking into account strides, offsets, and degenerate ranges and all. Thanks in advance for any advice.

1 0

RE: [Boost-Users] Problem with 1.30.0 lexical_cast
by Tom Matelich 26 Mar '03

26 Mar '03

> From: Tom Matelich [mailto:tmatelich@zetec.com] > Sent: Wednesday, March 26, 2003 1:40 PM > > > Compiler: gcc 3.2 and 3.2.2 > > I believe this is actually a bug in gcc, but I'm going to > post it hopes that someone can help me. Well, I can't blame gcc. It happens on my Windows/Intel 7.0 box as well. I am really confused here. ----------------------------------------------------------------------- DISCLAIMER: Information contained in this message and/or attachment(s) may contain confidential information of Zetec, Inc. If you have received this transmission in error, please notify the sender by return email. -----------------------------------------------------------------------

1 0

boost/type_traits/config.hpp
by H. Morishima 26 Mar '03

26 Mar '03

My compiler issues the following warning message (boost v1.29.0, G++ 3.2 with warning level high): boost_1_29_0/boost/type_traits/config.hpp:90:55: warning: "BOOST_MSVC" is not defined boost/type_traits/config.hpp: line 90 is: # if (........ || BOOST_MSVC > 1301 || ........) Shouldn't it be as follows? # if (........ || #defined(BOOST_MSVC) && BOOST_MSVC > 1301 || ........) H. Morishima

4 5

BCB6 Internal compiler error in "linear_congruential.hpp" from the random library
by Eike Petersen 26 Mar '03

26 Mar '03

Hi, to whomever it may concern: I just downloaded boost 1.30 and tried to recompile my libraries and applications. Now just including the header "linear_congruential.hpp" from the random library produces an internal compiler error: "[C++ Fatal Error] linear_congruential.hpp(113): F1004 Internal compiler error at 0xc4c367 with base 0xc10000" [...] #ifndef BOOST_NO_MEMBER_TEMPLATE_FRIENDS template<class CharT, class Traits> friend std::basic_ostream<CharT,Traits>& operator<<(std::basic_ostream<CharT,Traits>& os, const linear_congruential& lcg) { os << lcg._x; return os; } template<class CharT, class Traits> friend std::basic_istream<CharT,Traits>& operator>>(std::basic_istream<CharT,Traits>& is, linear_congruential& lcg) { is >> lcg._x; return is; } #endif [...] As I do not require the streaming facilities I just commented that section out and everything works fine. Maybe not really a solution. Regards Eike P.S: BCB6 with UPD4 was used (BCC32 5.6.4)

1 0

Linking with Unit Test Framework on VC7
by d_zakaib 26 Mar '03

26 Mar '03

Hi, I've got the following program to test the unit test suite: --------------------------------- // ICFGTest.cpp : Defines the entry point for the console application. // #include <boost/test/unit_test.hpp> using namespace boost::unit_test_framework; void testPass() { BOOST_CHECK( true ); } test_suite* init_unit_test_suite( int argc, char* argv[] ) { test_suite* test= BOOST_TEST_SUITE( "Test test suite" ); test->add( BOOST_TEST_CASE( &testPass )); return test; } --------------------------------- when I link this with the boost v1.30 unit test framework, I get the following linker errors: Linking... libboost_unit_test_framework.lib(unit_test_suite.obj) : error LNK2005: "public: virtual unsigned long __thiscall boost::unit_test_framework::test_case::size(void)const " (?size@test_case@unit_test_framework@boost@@UBEKXZ) already defined in ICFGTest.obj ICFGTest.obj : error LNK2019: unresolved external symbol "bool __cdecl boost::test_toolbox::detail::test_and_continue_impl(bool,struct boost::test_toolbox::detail::wrapstrstream const &,char const *,int,bool,enum boost::unit_test_framework::report_level)" (?test_and_continue_impl@detail@test_toolbox@boost @@YA_N_NABUwrapstrstream@123@PBDH0W4report_level@u nit_test_framework@3@@Z) referenced in function "void __cdecl testPass(void)" (?testPass@@YAXXZ) ICFGTest.obj : error LNK2019: unresolved external symbol "public: __thiscall boost::unit_test_framework::test_suite::test_suite(char const *)" (??0test_suite@unit_test_framework@boost@@QAE@PBD@Z) referenced in function "class boost::unit_test_framework::test_suite * __cdecl init_unit_test_suite(int,char * * const)" (?init_unit_test_suite@@YAPAVtest_suite@unit_test_ framework@boost@@HQAPAD@Z) Debug/ICFGTest.exe : fatal error LNK1120: 2 unresolved externals ------------------------ The unresolved symbol test_and_continue_impl seems most curious since one of it's parameters expects a wrapstrstream, not a wrap_strstream as the function declaration itself would suggest. Any ideas what I'm doing wrong? (NOTE: I'm linking to the static multi-threaded lib). Thanks! Dan

2 3

Spirit semantic actions and closures
by venkatram_krishnaswamy 25 Mar '03

25 Mar '03

Hi I have a question about semantic actions which generate the equivalent of synthesized attributes. It seems that the right hand side of the expression below rule = element [rule.val = val_type(some_params)]; will require the type of val in the closure associated with rule to be val_type which has a constructor which looks like val_type::val_type(some_params). Its not clear to me however how I would synthesize an attribute which is a pointer to some type. For example, in the closure I would like the type of synthesized attribute to be val_type* and for the right hand side of assignment above to be val_type(some_params)() which returns a val_type* where the following was true of the () operator : const val_type* val_type::operator () {do something and eventually return a val_type*;} I'd be very grateful if someone could clue me in on how I might do this. thanks venkat

2 1

uBlas blas and lapack binds
by geert_ceuppens 25 Mar '03

25 Mar '03

When will the blas and lapack binds be included with uBlas? I hoped to see them in the 1-30 release : ( Thanks - Geert

2 1

ublas: questions from a newcomer
by stuart macgregor 25 Mar '03

25 Mar '03

I am interested in ublas for linear algebra. In addition to the simple operations supported by ublas I will need comprehensive access to lapack for the real work. I see in the wiki that some work has been done in this area. Is this numeric/binding stuff working, and can it be readily extended to the full set of lapack routines? Some kind of meta program to generate lapack interfaces from a parameter spec would be nice (ruby/perl? or just a description of what needs to be done) Then I could happily bring up the interfaces I need. Is there any way to generate vectore and matrices which do not own the data buffer which they provide access to - 'view' or 'sub' objects in other lin alg packages? This would be very valuable to me for interfacing existing code, without duplicating storage and doing unnecessary copies. I found it difficult to determine from the current documentation. I have one worry: Ublas, and most of the boost modules, seems to me not for the faint hearted. They are clearly powerful, but seem to expect a lot from a potential user. Are these facilities aimed at library writers rather than users whoes skill focus may lie in other domains? I am thinking of apl (and related J++ (not java)) which is very powerful, but has only minority appeal because it is too alien and unnatural for ordinary mortals. The advocates take great pride in how powerful a small and almost incomprehensible line of code can be (FFT in one short line etc.), and implicitly how clever they are to generate and understand it. I expect that a user level doc may eventually make ublas/lapack much more approachable by a non computer science mathematician or engineer. Forgive me if the above sounds critical and ungracious for free software, but I want to use boost and I am worried that it may be too demanding for its benefites to be justified for use by the group of people I work with. -- Stuart

3 2

RE: [Boost-Users] shared_array with memcpy, help request
by bjorn.karlsson＠readsoft.com 25 Mar '03

25 Mar '03

> From: Blake D [mailto:BlakeTNC@yahoo.com] > I am a new boost user, and I'm trying to convert a large > project to use the > smart pointers. I have a use for shared_array buy the memcpy > line from the > following code snippet(, and all memcpy's) throw an exception with the > shared_arrays and I don't know why. Am I doing something > obvious wrong? [snip] > boost::shared_array<uint8> p_data(new uint8[data_length]); The above declaration of a local variable called p_data is probably not what you intended (you want to initialize the member variable p_data). If you cannot (or won't) perform the initialization in the constructor initializer, you'll need to reset the shared_array like so: p_data.reset(new uint8[data_length]); Or, in the initializer: c_Packet::c_Packet (const c_Packet & r_packet) : p_data(new uint8[r_packed.data_length]) { data_length = r_packet.data_length; ... } ...and then perform the memcpy. By the way, you are actually sharing this data, right? If not, scoped_array would probably be a better choice for managing resource lifetime. Bjorn Karlsson

1 0

shared_array with memcpy, help request
by Blake D 25 Mar '03

25 Mar '03

Hello everyone :) I am a new boost user, and I'm trying to convert a large project to use the smart pointers. I have a use for shared_array buy the memcpy line from the following code snippet(, and all memcpy's) throw an exception with the shared_arrays and I don't know why. Am I doing something obvious wrong? Thank you, Blake //------------------class declaration snippet--------------------------------- // Pointer to the packet boost::shared_array<uint8> p_data; // uint8 * p_data; <--- old working line //------------------class cpp file snippet--------------------------------- // copy Constructor c_Packet::c_Packet (const c_Packet & r_packet) { data_length = r_packet.data_length; boost::shared_array<uint8> p_data(new uint8[data_length]); // p_data = new uint8[data_length]; <--- old working line // Copy data from our source object to this object memcpy(p_data.get(), r_packet.p_data.get(), data_length); // <- throws exception! // memcpy(p_data, r_packet.p_data, data_length); <---- old working line #ifdef DO_DEBUG // cout << "packet copy constructor called" << endl ; #endif // DO_DEBUG }

2 1