- Boost-users - lists.boost.org

boost::mpl::apply2
by Greg Emerson 02 Nov '04

02 Nov '04

Hi, I am using VC++ 7.1 and getting an internal compiler error when compiling in DEBUG mode: boost\mpl\aux_\preprocessed\plain\apply.hpp(50) : fatal error C1001: INTERNAL COMPILER ERROR. This is at the declaration of boost::mpl::apply2 This does not happen when compiling in RELEASE mode. When doing a full build, two files cause this error, say X.cpp and Y.cpp. If I first clean the build and compile X.cpp then Y.cpp, only Y.cpp will generate the error. Ditto for reversing the order. Has anybody else seen this inexplicable (to me) behavior? Thanks, Greg

2 1

uBLAS for signal processing?
by Paul Baxter 02 Nov '04

02 Nov '04

I'm looking for a vector/matrix library that is suitable for relatively simple vector maths (+-*/, x=Ax+By) with occasional use of matrices (simple covariance calcs, matrix inversion). My main concerns are being able to optimise for speed by being able to capitalise on vendor-tuned libs on a specific architecture(e.g. MKL, ATLAS ) and maintain portability across a wide range of platforms. I'm looking to support vectors and matrices of types float, double, complex<float> and complex<double>. uBLAS seems to support specification of a storage format that allows me to define/assume an underlying representation of contiguous floats/doubles (with stride info) suitable for typical C-optimised signal processing functions to be applied. (No doubt I will hide the signal processing functions behind an appropriate lightweight interface, but it is important to be able to avoid copies etc and get to hand-tuned FFTs etc that typically are only supplied for C interfaces.) Is uBLAS the right tool for the job? (http://itpp.sourceforge.net provides an idea of where I'd like to see a processing layer end up albeit it is GPL (commercial use a problem) and doesn't have a clear separation between the underlying matrix/vectors and the various types of processing functions) Some other questions and observations: 1) What is the state of the bindings aspect of uBLAS with Atlas et al (or is this a separate project that hasn't got quite the same impetus to it as the main uBLAS development.) 2) Is there any implementation of 'tiny' vectors and matrices that reduces the abstraction penalty of say 3x3 or say 8 element vectors when compared with C. Is this possible/desirable while maintaining the uBLAS interface? 3) At the moment from a users point of view I feel the ublas docs focus heavily on implementation detail and I haven't managed to find too much in the way of simple tutorial information (pointers appreciated) to encourage simplified usage. If uBLAS is the right way forward for me I would be happy to contribute to this documentation effort. (There is mention of newer post 1.32 docs - is this already being addressed?)

1 0

uBLAS past, present, and future.
by Daniel L Elliott 02 Nov '04

02 Nov '04

Hello, I am trying to better understand the current status of the uBLAS library. Below I have listed a few questions. Of course, any responses are completely off the record. We just need to get a better idea of the current state of uBLAS. Thank you, in advance, for any information you provide. - What is the history of uBLAS? What is the eventual goal? - What is the current status of uBLAS? How complete is it currently? Anything left unimplemented (Sparse stuff)? Should a project which relies upon uBLAS heavily *expect* to encounter bugs within uBLAS? - Is uBLAS expected to become a part of the C++ standard? - What advantages/disadvantages do you feel uBLAS has when compared to FORTRAN. Could it replace FORTRAN? Thank you to everyone for your time and effort on all BOOST libraries and for your answers. Sincerely, Dan Elliott

4 4

compile error - class reference_wrapper
by Stefano 01 Nov '04

01 Nov '04

Hello everybody While in the last week I succesfully compiled my code that included "boost/function.hpp", starting from today I have (for a reason that I ignore) the following error. The compiler (mingw32 with stlport) says: Executing make... make.exe -f "C:\temp\Makefile.win" all c++.exe -D__DEBUG__ -c main.cpp -o main.o -I"c:/mingw/STLport/stl" -I"C:/Dev-Cpp/the-agency/boost_1_31_0" -g3 In file included from C:/Dev-Cpp/the-agency/boost_1_31_0/boost/function/function_base.hpp:22, from C:/Dev-Cpp/the-agency/boost_1_31_0/boost/function/detail/prologue.hpp:16, from C:/Dev-Cpp/the-agency/boost_1_31_0/boost/function.hpp:22, from main.cpp:3: C:/Dev-Cpp/the-agency/boost_1_31_0/boost/ref.hpp:84: error: syntax error before `<' token C:/Dev-Cpp/the-agency/boost_1_31_0/boost/ref.hpp:84: error: `T' was not declared in this scope C:/Dev-Cpp/the-agency/boost_1_31_0/boost/ref.hpp:84: error: template argument 1 is invalid C:/Dev-Cpp/the-agency/boost_1_31_0/boost/ref.hpp:84: error: ISO C++ forbids declaration of `type name' with no type C:/Dev-Cpp/the-agency/boost_1_31_0/boost/ref.hpp:85: error: syntax error before `:' token This problem came out for the first time when I tried to build a static lib instead of an exe. Thanks for any hel Stefano

1 0

Variant class serialization
by Alexander Katasonov 01 Nov '04

01 Nov '04

It is possible to serialize variant template class using boost serialization library? I couldn't do it directly, like this boost::variant<int, int, int> var; std::ofstream ofs("./out.xml"); boost::archive::xml_oarchive oa(ofs); oa << boost::serialization::make_nvp("variant", var); ofs.close();

1 0

Boost (Test) lib. in VS2003
by Kovarththanan Rajaratnam 01 Nov '04

01 Nov '04

Hello Im trying to get Boost (Test library) working with Visual Studio .Net 2003, but Im having trouble getting a simple test compiling. Ive followed the steps in "Getting started" guide and compiled and installed it. What changes do I have to make in VS2003 to get it working? -- Best Regards Kovarththanan Rajaratnam

2 3

boost graph library bugs
by Qiaofeng Yang 31 Oct '04

31 Oct '04

Hi, Does anybody use boost graph library here? I have been using it for a while and found that there seem quite a few bugs in the library. For example, there are bugs in: 1. incremental_components functions 2. subgraph functions Does anybody have problems with boost graph library? Where to find listed bugs found in boost graph library? Thanks very much! Qiaofeng

2 1

Re: [Boost-users] shared_ptr<> w/ Boost::Python
by John Meinel 30 Oct '04

30 Oct '04

> >>-----Original Message----- >>From: boost-users-bounces(a)lists.boost.org [mailto:boost-users- >>bounces(a)lists.boost.org] On Behalf Of John Meinel >>Sent: Saturday, October 30, 2004 9:24 AM >>To: boost-users(a)lists.boost.org >>Subject: [Boost-users] shared_ptr<> w/ Boost::Python >> [...] > >>" No to_python (by-value) converter found for C++ type: class >>boost::shared_ptr<class mine> " >> >>I have a converter for "class mine". I actually thought that the >>lifetime managers were using a shared_ptr, so if I did it myself, it >>would just be transparent. > > > [Nat] We tell boost::python the smart pointer type we're using, like > this: > > class_<DrawableInterface, DrawablePtr, boost::noncopyable> > ("DrawableInterface", no_init) > ; > > where DrawablePtr is a typedef for the smart pointer type. > This does work, if done by itself. I can do: class_<mine, boost::shared_ptr<mine>, bases<parent> , boost::noncopyable>("mine", no_init) However, this class has virtual functions. And while not strictly required, I tried to follow the recommendation that you create wrappers for all the functions, so that you can sub-class the C++ object in python. So I already have a class of: class mine_w : public mine { public: PyObject *self; mine_w(PyObject *_self) : self(_self) {} virtual bool func1(int a) { return call_method<bool>("func1", a); } } So right now, by definition looks like: class_<mine, mine_w, boost::noncopyable>("mine", no_init); If I changing mine_w to shared_ptr<mine> allows it to work. But trying to do: class_<mine, boost::shared_ptr<mine_w>, bases<parent> , boost::noncopyable>("mine", no_init); Again complains about no to-python converter for the given type. And trying to supply both, with: class_<mine, boost::shared_ptr<mine>, mine_w, bases<parent> , boost::noncopyable>("mine", no_init); Complains that I have too many template arguments. Also, what about the (hypothetical) situation where I might return shared_ptr<mine> from one function, but auto_ptr<mine> from another? Also, another "bug". If I create a pure-virtual class, then I should set the no_init field. However, if I try to sub-class this object in Python, the C++ constructor cannot be called, and so I can't pass this object to C++ functions. I'm trying to create some opaque interface classes (callbacks, etc). Without a wrapping class, it won't compile without no_init, since it tries to compile a function that would generate one. With a wrapping class I don't need no_init, and if I put it, then I can't properly subclass my object. Are these just known problems, and people live with it, or has it just not really come up? John =:->

1 0

shared_ptr<> w/ Boost::Python
by John Meinel 30 Oct '04

30 Oct '04

I realize this may not be the right list, but since I'm already subscribed... I've been using boost::python to wrap some C++ code for quite a while now, and I've been quite happy with it. However, I decided to get into boost more, and I've found that shared_ptr/shared_array are quite nice. So I've started changing my functions from returning a raw pointer to returning a shared_ptr. In the boost::python tutorial, they talk about when you return a raw reference or pointer, you need to wrap it to manage lifetime of the object. http://www.boost.org/libs/python/doc/tutorial/doc/call_policies.html In the beginning of that page, they talk about how smart pointers are better for defining the scope and lifetime of objects, but sometimes raw pointers are necessary. I've gotten pretty good about when to manage_new_object, or return_internal_reference, etc. However, now that I have changed my return functions to actually return a smart pointer, it doesn't seem like I should need to wrap the return value anymore. Only now, when I try to do a "get" it gives me the error: " No to_python (by-value) converter found for C++ type: class boost::shared_ptr<class mine> " I have a converter for "class mine". I actually thought that the lifetime managers were using a shared_ptr, so if I did it myself, it would just be transparent. Does anyone know what the proper way to export a shared_ptr into python is? I suppose I could define the shared_ptr<class mine>, and only expose the "get()" function. But that would certainly be less than optimal. (I also obviously cannot wrap my function in another function that returns get(), because that would cause the shared_ptr to have the wrong lifetime.) Thanks for any help, John =:->

2 1

RE: [Boost-users] i am stuck since a week here: need help:scopingerrorwhen trying to make boost work with luabind
by Brian Braatz 30 Oct '04

30 Oct '04

> help:scopingerrorwhen trying to make boost work with luabind > > Rohit O chokhani writes: > > Hi, i am a rookie as far as boost is concerned and i > > am trying to make boost work but just cant...on the > > point of giving up on it...so please help asap.... > > > > i am trying to use a scripting language called lua > > with my c++ source code. FOr that I felt the need to > > use luabind library which is completely dependent on > > boost.(project specific reasons for selecting luabind) > > > > > > As a result i need to have boost on my system. For the > > past 3-4 days ever since i have been trying to make > > boost works i have been getting all sorts of > > compilation errors. > > mainly they are as follows: > > > > C:\Program Files\Microsoft Visual > > Studio\VC98\INCLUDE\memory(16) : error C2059: syntax > > error : 'string' > > C:\Program Files\Microsoft Visual > > Studio\VC98\INCLUDE\memory(17) : error C2091: function [Brian Braatz] " C:\Program Files\Microsoft Visual > > Studio\VC98\" This shows me you are using VC6. While you "can" do this, you are asking for more pain than anyone should be forced to have. (it is not very compliant and has lots of template quirks. AND you get pages (and pages and pages and pages) of template warnings on valid code (making debugging compile time issues much more difficult) My *strong* suggestion to you is you install at least Visual Studio .net 2003 which comes with the vc++ 7.1 compiler. If you cannot purchase this product, the command line compiler is available for free download from: http://msdn.microsoft.com/visualc/vctoolkit2003/ Hope this helps (been there, done that, got the tee-shirt :) )

1 0