- Boost-users - lists.boost.org

[multiIndex] modify_key
by Jeffrey Holle 29 Nov '06

29 Nov '06

I'm using boost version 1.33.1 and am contemplating using a multiIndex container in my application. The held object will be something like: class element { int x; int y; Object *pObject; }; I need 2 ordered_non_unique indices using x and y and one ordered_unique index on pObject. The problem is that the values of x and y will need to be modified during the life of this container. Since the documentation says these indices are implemented using red-black trees, I think I'm heading for trouble. However, the multiIndex container seems to have a "modify_key" method. I can guarantee that the pObject value will not change, so if I obtain an iterator to an element based on this index, will I be able to modify either x or y and expect their related indices to still work?

2 2

Re: [Boost-users] Suggestion for boost`s smart pointers
by Sohail Somani 28 Nov '06

28 Nov '06

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Maitre Bart > Sent: Tuesday, November 28, 2006 12:36 PM > To: boost-users(a)lists.boost.org > Subject: [Boost-users] Suggestion for boost`s smart pointers > > I am assuming I am at the right tribune! (Let me know otherwise) > > I would suggest to add a constructor (as well as the > supporting members and > rules) to scoped_ptr<> that could allow specifying a deleter, as per: > > template<class Y, class D> scoped_ptr(Y * p, D d); > > as the same exists for shared_ptr<>. > > The deleter feature in shared_ptr is very useful for raii > with any kind of > resource (variables, functions, objects, etc.). Having it in > scoped_ptr will > offer the same advantage for noncopyable pointers. > > Thank you. +1 from me too but I think the reason is that people wanted sizeof(scoped_ptr<T>) to be sizeof(T *) (or they don't want it to change)

1 0

Suggestion for boost`s smart pointers
by Maitre Bart 28 Nov '06

28 Nov '06

I am assuming I am at the right tribune! (Let me know otherwise) I would suggest to add a constructor (as well as the supporting members and rules) to scoped_ptr<> that could allow specifying a deleter, as per: template<class Y, class D> scoped_ptr(Y * p, D d); as the same exists for shared_ptr<>. The deleter feature in shared_ptr is very useful for raii with any kind of resource (variables, functions, objects, etc.). Having it in scoped_ptr will offer the same advantage for noncopyable pointers. Thank you.

1 0

boost + linux + mingw ( g++: unrecognized option `-pthread' , cannot find -lrt )
by sfinks 28 Nov '06

28 Nov '06

Hi. Has anyone compiled boost on linux+mingw ? I have Debian Etch, mingw32 mingw32-binutils mingw32-runtime installed. mingw binaries linked as so: (CHROOT-wine-386)root@kroko386:~/boost_1_33_1# find /usr/bin/ -type l -ls|grep 586 9601281 0 lrwxrwxrwx 1 root root 26 Nov 24 08:16 /usr/bin/gcc-3.4.5 -> i586-mingw32msvc-gcc-3.4.5 9601293 0 lrwxrwxrwx 1 root root 24 Nov 24 08:16 /usr/bin/windres -> i586-mingw32msvc-windres 9601260 0 lrwxrwxrwx 1 root root 19 Nov 24 08:16 /usr/bin/cc -> i586-mingw32msvc-cc 9601282 0 lrwxrwxrwx 1 root root 23 Nov 24 08:16 /usr/bin/gccbug -> i586-mingw32msvc-gccbug 9601259 0 lrwxrwxrwx 1 root root 20 Nov 24 08:16 /usr/bin/c++ -> i586-mingw32msvc-c++ 9601275 0 lrwxrwxrwx 1 root root 20 Nov 24 08:14 /usr/bin/i586-mingw32msvc-cc -> i586-mingw32msvc-gcc 9601264 0 lrwxrwxrwx 1 root root 24 Nov 24 08:16 /usr/bin/c++filt -> i586-mingw32msvc-c++filt 9601284 0 lrwxrwxrwx 1 root root 19 Nov 24 08:16 /usr/bin/ld -> i586-mingw32msvc-ld 9601290 0 lrwxrwxrwx 1 root root 21 Nov 24 08:16 /usr/bin/size -> i586-mingw32msvc-size 9601278 0 lrwxrwxrwx 1 root root 20 Nov 24 08:16 /usr/bin/gcc -> i586-mingw32msvc-gcc 9601292 0 lrwxrwxrwx 1 root root 22 Nov 24 08:16 /usr/bin/strip -> i586-mingw32msvc-strip 9601285 0 lrwxrwxrwx 1 root root 19 Nov 24 08:16 /usr/bin/nm -> i586-mingw32msvc-nm 9601286 0 lrwxrwxrwx 1 root root 24 Nov 24 08:16 /usr/bin/objcopy -> i586-mingw32msvc-objcopy 9601283 0 lrwxrwxrwx 1 root root 21 Nov 24 08:16 /usr/bin/gcov -> i586-mingw32msvc-gcov 9601291 0 lrwxrwxrwx 1 root root 24 Nov 24 08:16 /usr/bin/strings -> i586-mingw32msvc-strings 9601271 0 lrwxrwxrwx 1 root root 24 Nov 24 08:16 /usr/bin/dllwrap -> i586-mingw32msvc-dllwrap 9601277 0 lrwxrwxrwx 1 root root 20 Nov 24 08:16 /usr/bin/g++ -> i586-mingw32msvc-g++ 9601287 0 lrwxrwxrwx 1 root root 24 Nov 24 08:16 /usr/bin/objdump -> i586-mingw32msvc-objdump 9601258 0 lrwxrwxrwx 1 root root 19 Nov 24 08:16 /usr/bin/as -> i586-mingw32msvc-as 9601027 0 lrwxrwxrwx 1 root root 26 Nov 24 08:16 /usr/bin/addr2line -> i586-mingw32msvc-addr2line 9601265 0 lrwxrwxrwx 1 root root 20 Nov 24 08:16 /usr/bin/cpp -> i586-mingw32msvc-cpp 9601289 0 lrwxrwxrwx 1 root root 24 Nov 24 08:16 /usr/bin/readelf -> i586-mingw32msvc-readelf 9601223 0 lrwxrwxrwx 1 root root 19 Nov 24 08:16 /usr/bin/ar -> i586-mingw32msvc-ar 9601266 0 lrwxrwxrwx 1 root root 24 Nov 24 08:16 /usr/bin/dlltool -> i586-mingw32msvc-dlltool 9601288 0 lrwxrwxrwx 1 root root 23 Nov 24 08:16 /usr/bin/ranlib -> i586-mingw32msvc-ranlib (CHROOT-wine-386)root@kroko386:~/boost_1_33_1# now I try to build with command: ~/bjam -sTOOLS=mingw -sGCC_INCLUDE_DIRECTORY=/usr/i586-mingw32msvc/include/ -sGCC_STDLIB_DIRECTORY=/usr/i586-mingw32msvc/lib/ --prefix=/opt/ gcc-C++-action bin/boost/libs/date_time/build/libboost_date_time.so/mingw/debug/shared-linkable-true/threading-multi/greg_month.o g++: unrecognized option `-pthread' /root/boost_1_33_1/libs/date_time/build/../src/gregorian/greg_month.cpp:1: warning: -fPIC ignored for target (all code is position independent) gcc-C++-action bin/boost/libs/date_time/build/libboost_date_time.so/mingw/debug/shared-linkable-true/threading-multi/greg_weekday.o g++: unrecognized option `-pthread' /root/boost_1_33_1/libs/date_time/build/../src/gregorian/greg_weekday.cpp:1: warning: -fPIC ignored for target (all code is position independent) gcc-C++-action bin/boost/libs/date_time/build/libboost_date_time.so/mingw/debug/shared-linkable-true/threading-multi/date_generators.o g++: unrecognized option `-pthread' /root/boost_1_33_1/libs/date_time/build/../src/gregorian/date_generators.cpp:1: warning: -fPIC ignored for target (all code is position independent) gcc-Link-action bin/boost/libs/date_time/build/libboost_date_time.so/mingw/debug/shared-linkable-true/threading-multi/libboost_date_time-mgw-mt-d-1_33_1.so g++: unrecognized option `-pthread' /usr/lib/gcc/i586-mingw32msvc/3.4.5/../../../../i586-mingw32msvc/bin/ld: cannot find -lrt collect2: ld returned 1 exit status What about those: 1) g++: unrecognized option `-pthread' 2) /usr/lib/gcc/i586-mingw32msvc/3.4.5/../../../../i586-mingw32msvc/bin/ld: cannot find -lrt collect2: ld returned 1 exit status Thanks..

5 9

Re: [Boost-users] Boost-Jam - Building Boost.Python extensions
by Lawrence Spector 28 Nov '06

28 Nov '06

Oops. Thanks for the assistance and quick response! =) -----Original Message----- From: boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Vladimir Prus Sent: Monday, November 27, 2006 9:54 AM To: boost-users(a)lists.boost.org Subject: Re: [Boost-users] Boost-Jam - Building Boost.Python extensions Lawrence Spector wrote: > Hello all. Quick question on boost-jam, because I couldn't get it work > right on my system. When I went into the > $BOOST_ROOT_DIR\libs\python\example\tutorial directory and build as > follows: > > > > bjam -sTOOLS=vc-7_1 > > > > It built with no problems. > > > I then took the tutorial example and moved it outside the boost tree. I > edited the Jamrules so that: > > > > path-global BOOST_ROOT : ../../../.. ; You need to *also* set BOOST_ROOT in environment. The above is Boost.Build definition, and for it to have any effect, or be even read, bjam must be able to find Boost.Build first. - Volodya _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

1 0

Graph: bug with gcc 4.1.1 and headers
by Todd A. Gibson 28 Nov '06

28 Nov '06

Problem: transitive_closure.hpp won't compile if depth_first_search.hpp is included before including transitive_closure.hpp . This problem occurs when compiling with gcc 4.1.1. This problem does not occur with gcc 3.3.5 To reproduce: Edit example/transitive_closure.cpp and add: #include <boost/graph/depth_first_search.hpp> before #include <boost/graph/transitive_closure.hpp> Thanks, -TAG

1 0

[Boost.Test] multithreading
by Andrea Murru 28 Nov '06

28 Nov '06

Hi! I have started some experiment with boost.test library, and I found it very flexible and quite simple to use. My question is very simple: what are guaranties about multithreading ? Can I call BOOST_CHECK from different threads ? Can I check predicates that internally call synchronization functions (i.e. waitformultipleobjects) ? Thank a lot for any suggestion. Andrea

2 1

Re: [Boost-users] output to multiple streams
by Eric MALENFANT 27 Nov '06

27 Nov '06

Andrew Schweitzer a écrit: > Is there a standard way to output to multiple streams at the same > time? > > I would like to pass an ostream to a function, write output > strings into that stream, and have them go to both cout and a > file. I'd like something like this: > > void DoSomething(ostream& ros) > { > ros << "This goes should go to cout and to a file" << > endl; } multi_stream ms; fstream f("out.txt"); ms.add(cout); > ms.add(f); DoSomething(ms); > > Any suggestions? > > Is this supported by the iostream library? > tee_device is probably what you're looking for.

2 1

output to multiple streams
by Andrew Schweitzer 27 Nov '06

27 Nov '06

Is there a standard way to output to multiple streams at the same time? I would like to pass an ostream to a function, write output strings into that stream, and have them go to both cout and a file. I'd like something like this: void DoSomething(ostream& ros) { ros << "This goes should go to cout and to a file" << endl; } multi_stream ms; fstream f("out.txt"); ms.add(cout); ms.add(f); DoSomething(ms); Any suggestions? Is this supported by the iostream library? I took a brief look at iostream doc and without really absorbing it, it doesn't seem to directly support this functionality. Maybe I need to read more carefully. Thanks, Andy

2 1

[serialization] - creating own archive?
by Oliver.Kowalke＠qimonda.com 27 Nov '06

27 Nov '06

Hi, Can I get an example (HOWTO, pseudo code etc.) which creates ist own archive which does not require streams (using another basis)? Regards, Oliver

2 1