November 2008 - Boost - lists.preview.boost.org

[threadpool] recursive fork/join (fibers removed)
by k-oli＠gmx.de 05 Nov '08

05 Nov '08

Hello, http://www.boostpro.com/vault/index.php?action=downloadfile&filename=boost-… I've uploaded a new version of threadpool - fibers are remove so that fork/join is provided via recursive execution of sub-tasks (enqueued in local worker-queue). One open item is the synchronization of parent-task und sub-task (signaling via condition variables) - maybe solveable via fibers. regards, Oliver

1 0

Is there any need for a math library doing vectors and matrices operations?
by Christophe Riccio 05 Nov '08

05 Nov '08

Hi, For a 3D programmers using vectors and matrices is as common as using integers. Actually, it's probably even more common! For this reason, every 3D programmer relies on a math library but as they usually don't need much … they implement their own basic math library and that fine. However, most of the time a single graphics software could uses several math libraries because it uses several external libraries that each of them use there own math library. It involves: - A lot of unnecessary copy and conversion of data. - Different meanings for overloaded operators. - Unspecified conventions: row major matrix, column major matrix, left or right handed? - Use of poor math libraries. - Several libraries to understand, to learn: a waste of time for trivial and common need! GPU programmers get some really convenient languages to do graphics on GPU. Cg: http://developer.download.nvidia.com/cg/Cg_2.0/2.1.0012/Cg-2.1_October2008_… HLSL: http://msdn.microsoft.com/en-us/library/bb509561(VS.85).aspx<http://msdn.microsoft.com/en-us/library/bb509561%28VS.85%29.aspx> GLSL: http://www.opengl.org/registry/doc/GLSLangSpec.Full.1.30.08.withchanges.pdf These languages are the result of a lot of experimented developers in 3D graphics and are basically the same. I decided to build a C++ math library based on all the rules that those developers agreed to be good rules and it result in GLM: http://glm.g-truc.net. However, those GPU languages provide good features but limited features: No quaternion, no transformation, lot of limitation on types and rules that couldn't apply directly in C++ (swizzle operators). GLM has limitations because it results of too few developers to think about it. I would like to get more feedback and makes it even more useful. I would lie to making it better find more agreement so that one day it could be ready to be integrated to Boost and hopefully to C++ standard. I'm afraid that such kind of library already have been submitted and rejected, I know it need more work but I believe on my approach and I'm not afraid to change the library so that everyone agree it's good. Thanks, Christophe Riccio

7 9

[Boost.Build] boost.python tutorial is not compiling
by Sandeep Gupta 05 Nov '08

05 Nov '08

Hi, I am reasonably sure that this is due to omission in the configuration file. I checkout from the trunk and all compilation went without problem. But the hello world example within the boost.python is failing with error: LINK : fatal error LNK1104: cannot open file 'boost_python-vc80-mt-gd-1_38. lib' call "f:\Program Files\Microsoft Visual Studio 8\VC\vcvarsall.bat" x86 >nul link /NOLOGO /INCREMENTAL:NO /DLL /DEBUG /subsystem:console /out:"bin\msvc-8.0\debug\hello_ext.pyd" /IMPLIB:"bin\msvc-8.0\debug\hello_ext.lib" /LIBPATH:"F:\CodeBase\Libs\Python-2.5.2\PCbuild8\win32release" @"bin\msvc-8.0\debug\hello_ext.pyd.rsp" .... .... >From what I can make that LIBPATH doesn't have path to boost_python-vc80-mt-gd-1_38.lib. The lib in question is build at its requisite place. Appreciate any help. Thanks sandeep

1 0

[uuid] width
by Kenneth Laskoski 05 Nov '08

05 Nov '08

Hello, I was reading/using/copying your code when I spotted a possible bug in the inserter operator<<. The standard result for built-in types is to align the output and set the ostream width property back to zero, which does not happen when I use your class. For example: int main() { uuid x; cout << 'a' << setw(40) << x << 'a' << endl; } output is a00000000-0000-0000-0000-000000000000 a but should be a 00000000-0000-0000-0000-000000000000a If this is the intended behavior, please document it. If not, maybe the attached patch will help put things back on rail. Regards, Kenneth

2 1

[thread] hardware_concurrency() not working on all platforms?
by Oliver Kowalke 05 Nov '08

05 Nov '08

Hello, boost::thread::hardware_concurrency() seams not to work on all platforms (xBSD, OpenSolaris). Is there some ongoing work to provide this functionaly on the other platforms too? regards, Oliver -- Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer

2 1

Boost.Build changes for 1.38
by Vladimir Prus 04 Nov '08

04 Nov '08

As we're nearing 1.37, and the time for big changes that follows after, I wanted to discuss one Boost.Build change I want to make. Right now, we have two ways to build Boost -- using bjam directly, and using configure and make (which are wrappers over boost.build). The first approach may be a bit hard, and the second is very nice when it works, but it leads to other problems: - users start to assume it's "real" configure, and get upset when various variables that CXXFLAGS have no effect - if users want to do anything custom, like mingw cross compilation, they have to go back to direct use of bjam anyway. So, I'd like to suggest a solution where building of boost involves three steps: 1. ./bootstrap.sh or ./bootstrap.bat This step just builds bjam and puts it into boost root 2. ./bjam [--build-type=complete] [--layout=xxx] [properties] configure This step: - Tries to detect what compilers you have - Figures which optional libraries you have, and which you don't (e.g. ICU) - Writes a file project-config.jam with all the discovered information. 3. ./bjam This step can be usually invoked with no parameters, reads the configuration information from project-config.jam, and builds everything. For new users, this solution is only marginally more complex that configure/make, and does not create the false impression it's autoconf. For power users, the file produced in (2) can be tweaked and extra options can be specified in (3). For all users, this means that various properties can be specified only once in (2) and need not be repeated on every build, which is clearly a convenient thing. Anybody has comments about this plan? - Volodya -- Vladimir Prus http://vladimir_prus.blogspot.com Boost.Build V2: http://boost.org/boost-build2

11 20

Documentation and directory structure
by Robert Ramey 04 Nov '08

04 Nov '08

I've just downloaded the 1.37 release. I have the svn tree, but I wanted the pre-built documentation. I was very disappointed that I found the documentation in different places depending on how it was generated. So for some libraries its in ../doc/html and for others its in libs/<library_name>/doc. This is really confusing. It also suggests that the documentation build is some humungous script which builds all the documentation at once. I realise that boost likes to do things like this way - but never the less its very inconvenient for those of us who just want to use a small portion of boost in any given project. Can't we rationalize the documentation build in to something like the following? a) directory structure .../libs/<library_name>/doc Jamfile.v2 (optional) html .... docbook ... quickbook ... whatever. b) ability to build documentation for one library at a time by invoking bjam or whatever Advantages a) consistent directory structure b) release could but would necessarily have to include the prebuilt documentation c) easier for developers to fiddle with documentation of one library at a time d) easier to extract one library from boost e) easier to understand and use the documentation build process Robert Ramey

2 1

CMake build system is Merged into Trunk
by Michael Jackson 04 Nov '08

04 Nov '08

With the encouragement of Doug Gregor and the support of other Boost moderators I have merged the work from the CMake branch into trunk. The CMake branch was a branch to develop a new build system for boost based on the opensource CMake build system (www.cmake.org) The current state of the build system is unstable and still has work to be done. Compiling of the static libraries on at least one system (OS X 10.5.5 Intel) was completed and the installation of the libraries and headers was performed. There is still much work to be done but we are hoping to quickly improve the state of the cmake build system so that it becomes usable. NOTHING has been done to compromise the current build system based on BJam. For more information on getting started with CMake and boost please take a look at this page: <https://svn.boost.org/trac/boost/wiki/CMake> I will be adding to the CMake documentation on the wiki as soon as I can. For those familiar with CMake here is the 2 second how to (For Unix/ line command): Install CMake 2.6.2 from www.cmake.org Update your Boost trunk. Open boost/CMakeLists.txt and comment out the following line: message(FATAL_ERROR "") Create a build directory for boost (I suggest 'Build' within the boost directory) cd into Build cmake ../ .. Let that go for a little while make modularize .. Let that go for a while. This WILL change the layout of the boost working directory so WATCH OUT for this. Once this is complete there is NO 'undo' so the only way to get your working directory back the way it was is to do a revert from svn. Once this runs the bjam system WILL break. So ONLY do this if you want to either work on the CMake system or try it out. And finally run make Windows Users: Run the 'cmake-gui.exe' app and point it to your working directory. Tell the app where to put its build files (Binary directory) and hit configure. Pick what type of build files you want generated, and then let it "configure" After it is done configuring click the "Generate" button. Your project files, makefiles, or Visual Studio files should now be created. Testing is NOT complete as of yet. I am still getting all the cmake files updated. If you have comments, feedback or anything else either file a bug in the trac system or come join us on the boost-cmake mailing list <http://lists.boost.org/mailman/listinfo.cgi/boost-cmake > Again, I would like to stress that NOTHING has been done to change the current bjam based build system. If it DID break let me know ASAP and I will fix it. Thanks _________________________________________________________ Mike Jackson mike.jackson(a)bluequartz.net BlueQuartz Software www.bluequartz.net Principal Software Engineer Dayton, Ohio

3 3

Serialization - basic_text_iprimitive destructor throws
by John Salmon 04 Nov '08

04 Nov '08

I tried turning on exceptions on the input stream that I use for a text_iarchive, hoping to catch user-level errors such as an attempt to treat a non-archive file as an archive. It seems that when exceptions are enabled on the underlying stream, the basic_text_iprimitive destructor throws a second(?) basic_ios::failure exception, during stack unwinding, which lands me unhappily in the terminate handler. Can the basic_text_iprimitive destructor be protected against accidentally throwing? Here's an demonstration. This is on a Linux system with gcc/4.1.2. John Salmon salmonj(a)drdblogin6.en.desres$ cat ser.cpp #include <boost/archive/text_iarchive.hpp> #include <boost/serialization/serialization.hpp> #include <stdexcept> #include <fstream> struct Foo{ int i, j; private: friend class boost::serialization::access; template <class Archive> void serialize(Archive & ar, const unsigned int version) { ar & i & j; } }; int main(){ Foo foo; std::ifstream ifs("/dev/null"); ifs.exceptions(std::istream::failbit | std::istream::badbit); try{ boost::archive::text_iarchive tia(ifs); tia >> foo; }catch(std::ios_base::failure &e){ std::cerr << "Caught std::ios_base::failure. What: " << e.what() << "\n"; }catch(std::exception &e){ std::cerr << "Caught exception. What: " << e.what() << "\n"; } return 0; } salmonj(a)drdblogin6.en.desres$ xmk g++ -I/proj/desres/root/Linux/x86_64/boost/1_37_0-13/Release/include -g -L/proj/desres/root/Linux/x86_64/boost/1_37_0-13/Release/lib -Wl,-rpath,/proj/desres/root/Linux/x86_64/boost/1_37_0-13/Release/lib ser.cpp -lboost_serialization -o ser salmonj(a)drdblogin6.en.desres$ ser terminate called after throwing an instance of 'std::ios_base::failure' what(): basic_ios::clear Aborted (core dumped) salmonj(a)drdblogin6.en.desres$ gdb -c drdblogin6.en.desres.deshaw.com-6718.core ser GNU gdb 6.8 Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-unknown-linux-gnu"... Reading symbols from /proj/desrad-c/root/Linux/x86_64/boost/1_37_0-13/Release/lib/libboost_serialization.so...done. Loaded symbols for /proj/desres/root/Linux/x86_64/boost/1_37_0-13/Release/lib/libboost_serialization.so Reading symbols from /proj/desrad-c/root/Linux/x86_64/gcc/4.1.2-10/lib64/libstdc++.so.6...done. Loaded symbols for /proj/desres/root/Linux/x86_64/gcc/4.1.2-10/lib64/libstdc++.so.6 Reading symbols from /lib64/tls/libm.so.6...done. Loaded symbols for /lib64/tls/libm.so.6 Reading symbols from /proj/desrad-c/root/Linux/x86_64/gcc/4.1.2-10/lib64/libgcc_s.so.1...done. Loaded symbols for /proj/desres/root/Linux/x86_64/gcc/4.1.2-10/lib64/libgcc_s.so.1 Reading symbols from /lib64/tls/libc.so.6...done. Loaded symbols for /lib64/tls/libc.so.6 Reading symbols from /lib64/ld-linux-x86-64.so.2...done. Loaded symbols for /lib64/ld-linux-x86-64.so.2 Core was generated by `ser'. Program terminated with signal 6, Aborted. [New process 6718] #0 0x0000003f72a2e25d in raise () from /lib64/tls/libc.so.6 (gdb) where #0 0x0000003f72a2e25d in raise () from /lib64/tls/libc.so.6 #1 0x0000003f72a2fa5e in abort () from /lib64/tls/libc.so.6 #2 0x00002b5ab82f5f84 in __gnu_cxx::__verbose_terminate_handler () at /state/partition1/tmp/tmpXcQw4O/gcc-4.1.2-10/gcc-4.1.2/libstdc++-v3/libsupc++/vterminate.cc:97 #3 0x00002b5ab82f4106 in __cxxabiv1::__terminate (handler=0x1a3e) at /state/partition1/tmp/tmpXcQw4O/gcc-4.1.2-10/gcc-4.1.2/libstdc++-v3/libsupc++/eh_terminate.cc:43 #4 0x00002b5ab82f350b in __cxa_call_terminate (ue_header=0x50b730) at /state/partition1/tmp/tmpXcQw4O/gcc-4.1.2-10/gcc-4.1.2/libstdc++-v3/libsupc++/eh_call.cc:60 #5 0x00002b5ab82f3fa7 in __gxx_personality_v0 ( version=<value optimized out>, actions=6, exception_class=<value optimized out>, ue_header=0x50b730, context=0x7ffff29e5610) at /state/partition1/tmp/tmpXcQw4O/gcc-4.1.2-10/gcc-4.1.2/libstdc++-v3/libsupc++/eh_personality.cc:637 #6 0x00002b5ab846a068 in _Unwind_RaiseException_Phase2 (exc=0x50b730, context=0x7ffff29e5610) at /state/partition1/tmp/tmpXcQw4O/gcc-4.1.2-10/gcc-4.1.2/gcc/unwind.inc:66 #7 0x00002b5ab846a2db in _Unwind_Resume (exc=0x50b730) at /state/partition1/tmp/tmpXcQw4O/gcc-4.1.2-10/gcc-4.1.2/gcc/unwind.inc:234 #8 0x00002b5ab80fd790 in boost::archive::basic_text_iprimitive<std::istream>::~basic_text_iprimitive () from /proj/desres/root/Linux/x86_64/boost/1_37_0-13/Release/lib/libboost_serialization.so #9 0x00002b5ab8109e0c in boost::archive::text_iarchive_impl<boost::archive::text_iarchive>::text_iarchive_impl () from /proj/desres/root/Linux/x86_64/boost/1_37_0-13/Release/lib/libboost_serialization.so #10 0x00000000004045ab in text_iarchive (this=0x7ffff29e5ae0, is=@0x7ffff29e58d0, flags=0) at /proj/desres/root/Linux/x86_64/boost/1_37_0-13/Release/include/boost/archive/text_iarchive.hpp:110 #11 0x0000000000402c84 in main () at ser.cpp:24 (gdb) quit salmonj(a)drdblogin6.en.desres$

1 0

boost::integer library request
by Jorge Lodos Vigil 04 Nov '08

04 Nov '08

Hi Is there any chance the code below could be added to the integer library? More specifically, to the integer_mask.hpp header? If there is, I would be happy to provide tests and documentation. We use it to get significant parts of unsigned integer values, it is a superset of LOBYTE, HIBYTE, LOWORD and HIWORD windows macros and generates no binary code in optimized compilations. Thanks in advance. template < std::size_t Bits, typename Unsigned > inline typename uint_t<Bits>::least lobits(Unsigned n) { n &= low_bits_mask_t<Bits>::sig_bits; return (uint_t<Bits>::least)n; } template < std::size_t Bits, typename Unsigned > inline typename uint_t<Bits>::least hibits(Unsigned n) { n >>= (std::numeric_limits<Unsigned>::digits - low_bits_mask_t<Bits>::bit_count); return (uint_t<Bits>::least)n; } template <typename Unsigned> inline uint8_t lobyte(Unsigned n) { return lobits<8, Unsigned>(n); } template <typename Unsigned> inline uint8_t hibyte(Unsigned n) { return hibits<8, Unsigned>(n); } template <typename Unsigned> inline uint16_t loword16(Unsigned n) { return lobits<16, Unsigned>(n); } template <typename Unsigned> inline uint16_t hiword16(Unsigned n) { return hibits<16, Unsigned>(n); } template <typename Unsigned> inline uint32_t loword32(Unsigned n) { return lobits<32, Unsigned>(n); } template <typename Unsigned> inline uint32_t hiword32(Unsigned n) { return hibits<32, Unsigned>(n); } Best regards Jorge

1 0