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

building 32 and 64-bit Boost on the same platform
by Damien Hocking 30 Jan '09

30 Jan '09

Hi all, I'm working on a cross-platform project that needs 32 and 64-bit Boost on Windows, Linux and OS X. I can happily build the individual versions on each platform, e.g. bjam --build-dir=./build64 --toolset=darwin address-model=64 architecture=x86 --build-type=complete stage for OS X, but is there a way to get the stage directory renamed to say stage 64 so I can batch all this up and build the 32 and 64-bit versions without any intervention by me? I can write shell or batch scripts to copy or rename the stage directory, but if there's an option in the build system I'd like to know about it. Thanks in advance. Damien

3 3

Flushing a filtering_ostreambuf
by jean-louis.a.leroy＠fortis.com 30 Jan '09

30 Jan '09

I have implemented a stream that sends output to the debugger (using OutputDebugString() in Windows): class debug_output_sink : public boost::iostreams::sink { public: debug_output_sink(int) { } std::streamsize write(const char* s, std::streamsize n); // also tried with: // struct category : boost::iostreams::sink::category, boost::iostreams::flushable_tag { }; // bool flush() { return true; } }; When I use it directly, flush() works fine: stream_buffer<debug_output_sink> debug_streambuf(debug_sink); ostream debug_stream(&debug_streambuf); debug_stream << "test\n"; debug_stream.flush(); // characters appear immediately However, when I put it in a filter, flushing the filter doesn't flush the stream: // scope { stream_buffer<debug_output_sink> debug_streambuf(debug_sink); ostream debug_stream(&debug_streambuf); filtering_ostreambuf filtering_buf; filtering_buf.push(debug_stream); ostream os(&filtering_buf); os << "test"; os.flush(); // nothing filtering_buf.pubsync(); // nothing either filtering_buf.strict_sync(); // still nothing } // characters appear at last ! What I am missing here? Thanks, Jean-Louis Leroy

2 1

enable_if for class members
by Christopher Jefferson 30 Jan '09

30 Jan '09

In a class, I want to have one member function which has different implementations depending on one of the template parameters. I tried to use enable_if template<bool b> struct foo { typename boost::enable_if_c<b, int>::type get_val( ) { return 2; } typename boost::disable_if_c<b, int>::type get_val() { return 3; } }; But when I use foo in code, it doesn't work, complaning that: error: no type named 'type' in 'struct boost::enable_if_c<true, int>' Am I not using enable_if in the correct way? Is there any easy way to do waht I'm trying to do? I used to do this by declaring an inner class and overloading that, but then it is necessary to pass in the class and the code looks very messy. Thanks, Chris

3 2

newbie question - how to test
by Saibal Ghosh 30 Jan '09

30 Jan '09

Hi, I am building BOOST (the libraries) on solaris platform using SunStudio 11 compiler. But how to test whether all libraries are build properly? Does BOOST has some tests which i can run to verify the build ? regards, Saibal

1 0

serialization deserialization through the pointer
by niranjan bangera 30 Jan '09

30 Jan '09

hi all, i am facing some problem in my code. Please help me to tackle it. BOOST Version : 1.36.0 compliler : gnu-gcc-/4.1.1-binutils-2.16.1/x86_64-pc-linux2.4/bin/gcc example of my prog: header: my.h ---- class my { int var1; int var2; structure object; // structure is the some other structure which is defined(i have defied the serialization function for this also... /*serialization function*/ friend class boost::serialization::access; template<class Archive> void serialize(Archive & ar, const unsigned int file_version) { ar & var1; ar & var2; ar & object; } }; mymain.cpp ---------- #include "boost/archive/text_iarchive.hpp" #include "boost/archive/text_oarchive.hpp" #include "boost/serialization/access.hpp" #include "boost/serialization/serialization.hpp" #include "boost/serialization/collection_traits.hpp" #include "boost/serialization/utility.hpp" #include "my.h" class mymain { protected: my * ptr; public: void mytake_arch(); void myretrive_arch(); }; void mymain::mytake_arch() { std::ofstream ofs("filename"); { boost::archive::text_oarchive oa(ofs); oa << ptr; } } void mymain::myretrive_arch() { mymain *ptr = NULL; //// Confused in this, This is correct or wrong, if wront what else i can use std::ifstream ifs("filename"); boost::archive::text_iarchive ia(ifs); ia >> ptr; } int main() { mymain obj; obj.mytake_arch(); obj.myretrive_arch(); } Problem: ------- I have some confusion in retriving, Whether the way in which i retrieved is correct or wrong. Any other replacement or modification can be done for the retriving part(myretrive_arch() function). Please let me know. because the retrived ptr(pointer retrived) causes segmentation fault whenenver i use it for some other application. Any suggestions will be apprciated. Thanks, Niranjan

2 1

Cross compiling
by Yepez, Esteban 30 Jan '09

30 Jan '09

Hello, I am trying to cross compile boost for an embedded processor that has its own gcc and g++ compiler. What are the options I need to invoke so that the make uses these compilers instead of gcc? Also, can you tell me the simpliest way to test it? Thanks, Esteban

3 11

Compiler Error With boost::bind and boost::signals
by KERSAM 30 Jan '09

30 Jan '09

Hello. I have a compiler error when I try to use boost::bind and boost::signals. Here is the code: -------------------- #include<boost/bind.hpp> #include<boost/signals.hpp> class MyBoostTest { public: void testFunction(int x, int y) {} }; void doConnect() { boost::signal2<void, int, int> signal; signal.connect(boost::bind<void>(&MyBoostTest::testFunction, new MyBoostTest, _1)); } ----------------------------------- The compiler gives me the following error: c:\3rdparty\boost\boost\bind.hpp(289) : error C2064: term does not evaluate to a function taking 2 arguments class does not define an 'operator()' or a user defined conversion operator to a pointer-to-function or reference-to-function that takes appropriate number of arguments What am I doing wrong? Regards -- View this message in context: http://www.nabble.com/Compiler-Error-With-boost%3A%3Abind-and-boost%3A%3Asi… Sent from the Boost - Users mailing list archive at Nabble.com.

1 0

Re: [Boost-users] RBGL use with BGL minCut() function
by Gianni Loiacono 30 Jan '09

30 Jan '09

Thanks another time Mr. Sutton for the answer. This is my goal: "I have made a project that use efficiently BGL library. Now I have the necessity to use the Gomory-Hu algorithm......then I have searched on the net some source "boost compatible" that makes this algorithm ;)" But nothing, on the net there isn't this function.....I'm surprised because it is a fundamental algorithm of graph theory :o) Thanks a lot and sorry for my eng :) Bye.

1 0

Re: [Boost-users] [BGL] Bundled properties and property maps
by Andrew Sutton 30 Jan '09

30 Jan '09

On Tue, Jan 13, 2009 at 9:56 AM, Andrew Sutton <andrew.n.sutton(a)gmail.com>wrote: > Hi Andrew, apologies for writing directly to you, I just thought I'd try to >> get your attention this way since you hadn't yet replied to my last post on >> the above topic in the mailing list. >> > > Sorry about that, I've been swamped since new years. I'm going to bounce > this back to the list > > I would avoid declaring property maps as const. Somewhere in your posted > code you have: > > const property_map<...>::const_type map; // or something similar. > > For all property maps, map = get(...) is a valid expression, regardless of > whether your map is a ::type or ::const_type. By declaring it const, and > then instantiating a template with the const pmap, you're going to run into > problems - probably the problem you reported earlier. > > Andrew Sutton > andrew.n.sutton(a)gmail.com >

2 9

Boost 1.38.0 beta 2 available
by Beman Dawes 30 Jan '09

30 Jan '09

Boost 1.38.0 beta 2 available is available from SourceForge. http://sourceforge.net/project/showfiles.php?group_id=7586&package_id=8041&… Please report any problems or comments to the users or developers mailing lists. ------------- Version 1.38.0 New Libraries * Flyweight: + Design pattern to manage large quantities of highly redundant objects, from Joaquín M López Muñoz. * ScopeExit: + Execute arbitrary code at scope exit, from Alexander Nasonov. * Swap: + Enhanced generic swap function, from Joseph Gauterin. Updated Libraries * Accumulators: + Add rolling_sum, rolling_count and rolling_mean accumulators. * Date_Time: + Added support for formatting and reading time durations longer than 24 hours with new formatter: %0. + Removed the testfrmwk.hpp file from the public include directory. + Fixed several bugs and compile errors. + For full details see the change history * Exception: + Improved and more customizable diagnostic_information output. * Hash: + boost/functional/detail/container_fwd.hpp has been moved to boost/detail/container_fwd.hpp. The current location is deprecated. + For more detail, see the library changelog. * Interprocess: + Updated documentation to show rvalue-references funcions instead of emulation functions. + More non-copyable classes are now movable. + Move-constructor and assignments now leave moved object in default-constructed state instead of just swapping contents. + Several bugfixes (#2391, #2431, #1390, #2570, #2528). * Intrusive: + New treap-based containers: treap, treap_set, treap_multiset. + Corrected compilation bug for Windows-based 64 bit compilers. + Corrected exception-safety bugs in container constructors. + Updated documentation to show rvalue-references funcions instead of emulation functions. * Math: + Added Johan Råde's optimised floating point classification routines. + Fixed code so that it compiles in GCC's -pedantic mode (bug report #1451). * Multi-index Containers: Some redundant type definitions have been deprecated. Consult the library release notes for further information. * Proto: + Fix problem with SFINAE of binary operators (Bug 2407). + Fix proto::call transform for callable transforms with >3 arguments. + result_of::value changed behavior for array-by-value terminals. + unpack_expr requires only Forward Sequences rather than Random Access Sequences. + Deprecate legacy undocumented BOOST_PROTO_DEFINE_(VARARG_)FUNCTION_TEMPLATE macros. + Add BOOST_PROTO_REPEAT and BOOST_PROTO_LOCAL_ITERATE macros to help with repetitive code generation + Support for nullary expressions with tag types other than proto::tag::terminal + Allow 0- and 1-argument variants of proto::or_ and proto::and_ * Regex: + Breaking change: empty expressions, and empty alternatives are now allowed when using the Perl regular expression syntax. This change has been added for Perl compatibility, when the new syntax_option_type no_empty_expressions is set then the old behaviour is preserved and empty expressions are prohibited. This is issue #1081. + Added support for Perl style ${n} expressions in format strings (issue #2556). + Added support for accessing the location of sub-expressions within the regular expression string (issue #2269). + Fixed compiler compatibility issues #2244, #2514, and #2458. * Unordered: + Use boost::swap. + Use a larger prime number list for selecting the number of buckets. + Use aligned storage to store the types. + Add support for C++0x initializer lists where they're available. + For more detail, see the library changelog. * Xpressive: + basic_regex gets nested syntax_option_flags and value_type typedef, for compatibility with std::basic_regex + Ported to Proto v4; Proto v2 at boost/xpressive/proto has been removed. + regex_error inherits from boost::exception Other Changes Experimental support for building Boost with CMake has been introduced in this version. For more details see the wiki, Discussion is taking place on the Boost-cmake mailing list. Compilers Tested Boost's primary test compilers are: * TODO * GCC 4.0.1 on OS X 10.4.10 and 10.5.2 on Intel and 10.4.9 on Power PC. * GCC 4.3.2 on Ubuntu Linux. * GCC 4.3.3 on Unstable Debian. * GCC 4.2.1 on HP-UX 64-bit. * HP C/aC++ B3910B A.06.17 on HP-UX 64-bit. * Visual C++ 7.1 SP1, 8.0 SP1 and 9.0 SP1 on Windows XP. Boost's additional test compilers include: * OS X: + GCC 4.0.1 on OS X 10.4.10 and 10.5.2 on Intel, OS X 10.4.9 on PowerPC + Intel 9.1, 10.0 on OS X 10.4.10 + Intel 10.1, 11.0 on OS X 10.5.2 * On Linux: + GCC 4.1.1, 4.2.1 on 64-bit Red Hat Enterprise Linux + GCC 4.1.2 on 64-bit Redhat Server 5.1 + GCC 3.4.3, GCC 4.0.1, GCC 4.2.4 and GCC 4.3.2 on Red Hat Enterprise Linux + GCC 4.3.2 with C++0x extensions + GCC 4.2.1 on OpenSuSE Linux + pgCC 8.0-0a 64-bit target on Red Hat Enterprise Linux + QLogic PathScale(TM) Compiler Suite: Version 3.1 on Red Hat Enterprise Linux * IBM XL C/C++ Enterprise Edition for AIX, V10.1.0.0, on AIX Version 5.3.0.40 * GCC 4.2.1 on FreeBSD 7. * GCC 4.2.1 on HP-UX Integrity * HP C/aC++ B3910B A.06.17 on HP-UX 64-bit. Acknowledgements TODO

1 0