March 2008 - Boost-users - lists.preview.boost.org

boost exceptions on MacOS 10.5
by Lothar May 09 Mar '08

09 Mar '08

Hi, I've brought this up before, but I still have no solution for this issue, so I will give it another try: Does anyone have boost 1.34.1 compiled on MacOS 10.5 where exceptions can be caught? You might use the following code to test: --cut here-- #include <iostream> #include <boost/filesystem.hpp> using namespace std; using namespace boost::filesystem; int main() { try { directory_iterator i("does_not_exist"); } catch(...) { cout << "This is never printed on MacOS 10.5." << endl; } return 0; } --cut here-- If this works with your installation of boost on MacOS 10.5, please tell me which steps you did to compile boost, and whether you used the static or dynamic version. A related question is: Is boost "supposed to work" on MacOS 10.5? Thanks, Lothar

4 16

Pion Network Library 0.5.4
by Michael Dickey 09 Mar '08

09 Mar '08

In conjunction with the first alpha release of our Pion CEP Platform, Atomic Labs is happy to announce a new release (v0.5.4) of the Pion Network Library, an active, fully-functional and Boost-licensed HTTP 1.0/1.1 client/server library built on top of asio. This new release contains several enhancements, including the ability to define alternative thread management and work scheduling for each server instance (PionScheduler is no longer a singleton), and the ability to bind any function object (or function if you use boost::bind) to an HTTP resource (the use of WebService plugins is now optional). We've also added a std::basic_iostream wrapper for TCPConnection objects called TCPStream. In addition, we fixed several bugs that were identified within the last (v0.5.2) release, including issues with parsing chunked entity content, and with parsing responses that include neither "Content- Length" nor "Transfer-Encoding" HTTP headers. Also, the HTTPRequest and HTTPResponse objects now sort HTTP headers using a case- insensitive map, so lookups should now work properly regardless of the capitalization used (if any). Although we have several new things planned for the next few months (such as adding support for user authentication), the networking library is now mostly stabilized and ready for general use. The Pion CEP Platform is open source software, published under the GNU Affero GPL license. The platform is a real-time event processing engine that is designed to be extremely extensible through the use plugins. Plugins can be developed to provide specialized data processing logic, web services, and to enable support for different data encoding formats and databases. You can learn more and download releases at http://www.pion.org Take care, -Mike

1 0

[Review] Reminder: Proto review half way through now
by Hartmut Kaiser 09 Mar '08

09 Mar '08

Hi all, this is just a gentle reminder that currently we have the Proto review ongoing. It will last another week and will end on March 14th. We have not got enough response so far! If you're planning to submit a review, please do so soon. If you didn't have considered to submit one yet, please reconsider! Here is the initial announcement: The review of Eric Nieblers Proto library starts today, March 1st 2008, and will end on March 14th. I really hope to see your vote and your participation in the discussions on the Boost mailing lists! --------------------------------------------------- About the library: Proto is a framework for building Domain Specific Embedded Languages in C++. It provides tools for constructing, type-checking, transforming and executing expression templates. More specifically, Proto provides: * An expression tree data structure. * Operator overloads for building the tree from an expression. * Utilities for defining the grammar to which an expression must conform. * An extensible mechanism for immediately executing an expression template. * An extensible set of tree transformations to apply to expression trees. * A mechanism for giving expressions additional behaviors and members. Documentation is here: http://boost-sandbox.sourceforge.net/libs/proto Download proto.zip from here: http://www.boost-consulting.com/vault/index.php?directory=Template%20Metapro gramming Proto is a very important infrastructure library, IHMO. It has been used as the backbone for several other library writing efforts already, such as Xpressive and the rewrite of Spirit (there it has been used for all three parts: the parser, the lexer and the generator modules), and it is a key enabling technology in the long-planned unification of Phoenix and the Lambda Library. --------------------------------------------------- Please always state in your review, whether you think the library should be accepted as a Boost library! Additionally please consider giving feedback on the following general topics: - What is your evaluation of the design? - What is your evaluation of the implementation? - What is your evaluation of the documentation? - What is your evaluation of the potential usefulness of the library? - Did you try to use the library? With what compiler? Did you have any problems? - How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? - Are you knowledgeable about the problem domain? Regards Hartmut Review Manager

1 0

error: 'level' is not a member of 'boost::logging::formatter'
by Brad 09 Mar '08

09 Mar '08

Hello all, First post so be gentle with me :-) OK, I've been playing around with revision 43544 of boost::logging using the following code; #include <boost/logging/format.hpp> #include <boost/logging/format/formatter/tags.hpp> #include <boost/logging/format/destination/syslog.hpp> // uncomment if you're using Named Formatters and Destinations // #include <boost/logging/format/named_write.hpp> using namespace boost::logging; typedef boost::logging::logger_format_write< > log_type; BOOST_DEFINE_LOG(g_l, log_type) BOOST_DEFINE_LOG_FILTER(g_l_filter, boost::logging::level::holder) #define LAPP_ BOOST_LOG_USE_LOG_IF_LEVEL(g_l(), g_l_filter(), info ) int main( void ) { g_l()->writer().add_destination( destination::cout() ); g_l()->writer().add_destination( destination::syslog_no_levels() ); LAPP_ << "hi"; } when I compile it with "g++ -o syslog_test syslog_test.cpp -I/usr/include/ -lpthread" I get the following errors: /usr/include/boost/logging/format/destination/syslog.hpp:61: error: ‘level’ is not a member of ‘boost::logging::formatter’ /usr/include/boost/logging/format/destination/syslog.hpp:61: error: ‘level’ is not a member of ‘boost::logging::formatter’ /usr/include/boost/logging/format/destination/syslog.hpp:61: error: template argument 1 is invalid A quick look in boost/logging/format/formatter/tags.hpp and I see a typedef for level but no actual definition. If I change line 61 from: struct syslog : is_generic, formatter::uses_tag< formatter::level, ::boost::logging::tag::level >, boost::logging::op_equal::always_equal { to: struct syslog : is_generic, formatter::uses_tag< boost::logging::tag::level, ::boost::logging::tag::level >, boost::logging::op_equal::always_equal { It compiles and appears to work fine (I don't claim to understand the effects of this change). Forgive me if I'm missing something obvious or wasting anyones time. I'm thinking this is a bug but there's a high percentage chance it's an error on my part lol. Anyway, I'm having some great fun with boost (asio and logging so far) and appreciate the work some of you guys have put into these libs. Thanks, Brad

3 4

[mpi] Sending derived classes via MPI and serialize
by Number Cruncher 08 Mar '08

08 Mar '08

I'm trying to send polymorphic objects using boost::mpi, but I'm getting extensive "undefined reference" errors for the simple test case below. If I #include <boost/archive/text_oarchive.hpp> instead of the mpi/communicator, everything compiles fine. Any help greatly appreciated, Simon #include <boost/mpi/communicator.hpp> #include <boost/serialization/export.hpp> struct Base { virtual ~Base() {} virtual int id() const { return 1; } template<class Archive> void serialize(Archive &ar, const unsigned int) { ar & data; } int data; }; struct Derived : public Base { virtual int id() const { return 2; } }; BOOST_CLASS_EXPORT(Base) BOOST_CLASS_EXPORT(Derived) int main(int argc, char *argv[]) { Base *b = new Base; Base *d = new Derived; delete b; delete d; return 0; }

2 5

[boost graph] : trouble with the add_edge function
by Bernhard Lippmann 08 Mar '08

08 Mar '08

Hi, I use the add_edge () function to build my graph. Works almost perfect. While analysing my graph I found there have been add vertices created, I have have no idea where is is going to happen. Any helpmpossible ? I add a code snippet for the add_edge() function and my data log. vertices 12-15 are never created by me, but the are suddenly in my graph.... Best Bernhard >>>>>>>>>>>><SOURCE CODE Snippet >>>>>>>> iter = this->Elements.begin(); while(iter != this->Elements.end()) { aAtomicElement = (*iter).second; for (str_iter=aAtomicElement.AE_PinList.begin(); str_iter!= aAtomicElement.AE_PinList.end(); ++str_iter) { cout << "\n Params before call Add_edge(...) function (Bipartit Graph Type) \n "; cout << "edge [<std::string>]: "<< aAtomicElement.AE_Name << " ::" << *str_iter << " \n "; cout << "edge [<int> <int>]: "<< index_of_element( this->VertexNamesList, aAtomicElement.AE_Name) << " :: " << index_of_element( this->VertexNamesList, *str_iter) << " \n "; OneEdge.first = index_of_element( this->VertexNamesList, aAtomicElement.AE_Name); OneEdge.second = index_of_element( this->VertexNamesList, *str_iter); tie(e, inserted) = add_edge(OneEdge.first, OneEdge.second, g); if (inserted) { v = source(e, g); VertexNamesMap[v] = aAtomicElement.AE_Name ; v = target(e, g); VertexNamesMap[v] = *str_iter; EdgeNamesMap[e] = aAtomicElement.AE_Name + "-->" +*str_iter; cout << " by edge :" << EdgeNamesMap[e] << "\n"; WeightMap[e] = 1 ; } } iter ++; } // while ... <<<<<<< data log >>>>>>>>> Drücken Sie eine beliebige Taste . . . -------------------->>>>>>>>>><<<<<<<<<<------------------------- = Create the Edge Array and the Graph (V2).. Params before call Add_edge(...) function (Bipartit Graph Type) edge [<std::string>]: ptrans299 ::Z edge [<int> <int>]: 0 :: 1 by edge :ptrans299-->Z Params before call Add_edge(...) function (Bipartit Graph Type) edge [<std::string>]: ptrans299 ::A edge [<int> <int>]: 0 :: 2 by edge :ptrans299-->A Params before call Add_edge(...) function (Bipartit Graph Type) edge [<std::string>]: ptrans299 ::vdd! edge [<int> <int>]: 0 :: 3 by edge :ptrans299-->vdd! Params before call Add_edge(...) function (Bipartit Graph Type) edge [<std::string>]: ptrans299 ::vdd!s edge [<int> <int>]: 0 :: 4 by edge :ptrans299-->vdd!s Params before call Add_edge(...) function (Bipartit Graph Type) edge [<std::string>]: ptrans38 ::Z edge [<int> <int>]: 5 :: 1 by edge :ptrans38-->Z Params before call Add_edge(...) function (Bipartit Graph Type) edge [<std::string>]: ptrans38 ::B edge [<int> <int>]: 5 :: 6 by edge :ptrans38-->B Params before call Add_edge(...) function (Bipartit Graph Type) edge [<std::string>]: ptrans38 ::vdd! edge [<int> <int>]: 5 :: 3 by edge :ptrans38-->vdd! Params before call Add_edge(...) function (Bipartit Graph Type) edge [<std::string>]: ptrans38 ::vdd!s edge [<int> <int>]: 5 :: 4 by edge :ptrans38-->vdd!s Params before call Add_edge(...) function (Bipartit Graph Type) edge [<std::string>]: ntrans35 ::Z edge [<int> <int>]: 7 :: 1 by edge :ntrans35-->Z Params before call Add_edge(...) function (Bipartit Graph Type) edge [<std::string>]: ntrans35 ::A edge [<int> <int>]: 7 :: 2 by edge :ntrans35-->A Params before call Add_edge(...) function (Bipartit Graph Type) edge [<std::string>]: ntrans35 ::net25 edge [<int> <int>]: 7 :: 8 by edge :ntrans35-->net25 Params before call Add_edge(...) function (Bipartit Graph Type) edge [<std::string>]: ntrans35 ::vss!s edge [<int> <int>]: 7 :: 9 by edge :ntrans35-->vss!s Params before call Add_edge(...) function (Bipartit Graph Type) edge [<std::string>]: ntrans36 ::net25 edge [<int> <int>]: 10 :: 8 by edge :ntrans36-->net25 Params before call Add_edge(...) function (Bipartit Graph Type) edge [<std::string>]: ntrans36 ::B edge [<int> <int>]: 10 :: 6 by edge :ntrans36-->B Params before call Add_edge(...) function (Bipartit Graph Type) edge [<std::string>]: ntrans36 ::vss! edge [<int> <int>]: 10 :: 11 by edge :ntrans36-->vss! Params before call Add_edge(...) function (Bipartit Graph Type) edge [<std::string>]: ntrans36 ::vss!s edge [<int> <int>]: 10 :: 9 by edge :ntrans36-->vss!s Drücken Sie eine beliebige Taste . . . -------------------->>>>>>>>>><<<<<<<<<<------------------------- = http://www.graphviz.org/Download_windows.php write graph wizard file ... -------------------->>>>>>>>>><<<<<<<<<<------------------------- = vertices(g) = 0 : ptrans299 1 : Z 2 : A 3 : vdd! 4 : vdd!s 5 : ptrans38 6 : B 7 : ntrans35 8 : net25 9 : vss!s 10 : ntrans36 11 : vss! 12 : 13 : 14 : 15 : Drücken Sie eine beliebige Taste . . . -------------------->>>>>>>>>><<<<<<<<<<------------------------- = edges(g) = (0,1) =ptrans299-->Z (0,2) =ptrans299-->A (0,3) =ptrans299-->vdd! (0,4) = ns299-->vdd!s (5,1) =ptrans38-->Z (5,6) =ptrans38-->B (5,3) =ptrans38-->v (5,4) =ptrans38-->vdd!s (7,1) =ntrans35-->Z (7,2) =ntrans35-->A (7,8) =n s35-->net25 (7,9) =ntrans35-->vss!s (10,8) =ntrans36-->net25 (10,6) =ntra -->B (10,11) =ntrans36-->vss! (10,9) =ntrans36-->vss!s in-edges: (1,0) (2,0) (3,0) (4,0) in-edges: (0,1) (5,1) (7,1) in-edges: (0,2) (7,2) in-edges: (0,3) (5,3) in-edges: (0,4) (5,4) in-edges: (1,5) (6,5) (3,5) (4,5) in-edges: (5,6) (10,6) in-edges: (1,7) (2,7) (8,7) (9,7) in-edges: (7,8) (10,8) in-edges: (7,9) (10,9) in-edges: (8,10) (6,10) (11,10) (9,10) in-edges: (10,11) in-edges: in-edges: in-edges: in-edges: Drücken Sie eine beliebige Taste . . . -------------------->>>>>>>>>><<<<<<<<<<------------------------- No virus found in this outgoing message. Checked by AVG. Version: 7.5.518 / Virus Database: 269.21.6/1318 - Release Date: 07.03.2008 14:01

1 0

Platform-specific Boost filesystem warning
by Caleb Gingles 08 Mar '08

08 Mar '08

(Please forgive me if this has already been discussed, I'm new to the list and wasn't able to find it.) I'm using Boost 1.34.1 under MSVC8 and am experiencing a compile warning that I thought was a bit odd. Whenever I include convenience.hpp, I and up with the following warning: d:\prgrmmng\libraries\boost_1_34_1\boost\filesystem\convenience.hpp(46) : warning C4245: 'argument' : conversion from 'int' to 'boost::filesystem::system_error_type', signed/unsigned mismatch I eventually tracked this down to the following code in path.hpp: # ifdef BOOST_WINDOWS_API typedef unsigned system_error_type; BOOST_FILESYSTEM_DECL errno_type lookup_errno( system_error_type sys_err_code ); # else typedef int system_error_type; inline errno_type lookup_errno( system_error_type sys_err_code ) { return sys_err_code; } # endif Why is system_error_type given a different type depending on the platform?

1 0

Extending Multi Array
by Klett, Stefan 07 Mar '08

07 Mar '08

Hi list members, This is a more or less a general kind of " how to extend container classes" question - I'm trying to write a class which inherits from boost::multi_array - the to get a kind of matrix class with some additional service routines. Maybe it is a lack of experience - but I for the time being I don't know how to solve the problem to access the constructor of multi_array in my own class to initialize my matrix class - my current guess was to use the "this" pointer but it had not worked out like I supposed it to do. class NetworkMultiArray: public boost::multi_array<double,3> { public: NetworkMultiArray(int); virtual ~NetworkMultiArray(); }; Here is the constructor code: NetworkMultiArray::NetworkMultiArray(int length) { this::iterator iter3; typedef this::template subarray<2>::type::iterator iter2; typedef this::template subarray<1>::type::iterator iter1; for( iter1 i = *this.begin(); iter1 != *this.end(); iter1++){ for(iter2 ii = (*i).begin(); ii != (*i).end(); ii++){ for(iter3 iii = (*ii).begin(); iii != (*ii).end(); iii++){ *iii = 0.0 ; } } } } sure this does not work - and is the result from trying to adapt the iterator example from the documentation. my aim is to handle the NetworkMultiArray like a boost::multi_array and initialize it to zero - further it would be nice if somebody could tell me how I could assign a length to the array and the subarrays. The key-point is that I want to use my class (NetworkMultiArray) like a multi_array by inheritance of the multi_array features of boost:multi_array. Thank you very much in advance. Best regards Stefan -------------------------------------------------------- Stefan Klett (Dipl. Informatiker) | E-mail: stefan.klett(a)kit.edu Forschungszentrum Karlsruhe / KIT | Web: http://www.fzk.de SCC Steinbuch Centre for Computing| Phone: +49 (0)7247 828649 Hermann-von-Helmholtz-Platz 1 | Fax: +49 (0)7247 824972 D-76344 Eggenstein-Leopoldshafen | Mobile: +49 (0)176 20317250 -------------------------------------------------------------------

3 2

[python] redirecting PyErr_Print()
by Robert Dailey 07 Mar '08

07 Mar '08

Hi, Right now when an exception occurs in boost.python, I simply call PyErr_Print() to print the message to a console window. However, I would like to be able to have the option of redirecting the output of PyErr_Print() to a string, file, or any other ostream interface compatible object I choose. Is there an easy way to do this (possibly using boost)? My searching on the internet has not really shown any useful results. The answers I've seen involve creating pipes, which I don't want to do because it is non trivial. I was hoping boost could shine in this area since it seems to be a common issue.

2 2

ASIO: ssl - load_verify_file
by j.c. 07 Mar '08

07 Mar '08

Hello, I have implemented a TLS client/server application and will be using self-assigned certificates due to the small scale of distribution. I am currently using the function load_verify_file("ca.pem"), however I don't want to write the certificate to end-users disk. What would be the proper way to use an "in-memory or compiled" certificate for peer verification? Thanks, JC

2 4