- Boost - lists.boost.org

Boost::log : File rotation based on day of week
by Rajpal Dangi 24 Sep '08

24 Sep '08

Is it possible to configure Boost::log to rotate log files based on day of week in addition to size of file? What I'm targeting is a logger putting files in separate directory for each day of week and automatic cleanup of logs older than a week. Rajpal

2 1

[log] RFC: An alternative implementation is coming up
by Andrey Semashev 23 Sep '08

23 Sep '08

Hi, After more than a year of development my implementation of logging library is coming to its first release. Here are some feature highlights: * independent logger/sink and multimodule-friendly design with great extensibility potential * support for both embedded and global loggers * full-fledged attribute support (global, thread-specific and logger-specific attributes supported) * filtering and formatting support, including lambda expressions for filters and formatters construction * support for writing log to streams (files, console), rotating files support * support for Syslog API * support for library initialization helpers, including settings file support * thread safety support with least possible locking * wide-character logging support The library documentation can be found online on SourceForge: http://tinyurl.com/5e4fd7 Some requirements background can also be found on this Wiki: http://tinyurl.com/2fndfg The library code is quite stable, however, minor changes are still possible. The code can be checked out from the SourceForge CVS, the detailed instructions can be found here: http://tinyurl.com/6k9vvp There are currently no automatic tests, but there are some examples, which were compiled and run on Linux and Windows. I would like to see what Boost community thinks of this library, whether it worth submitting, has any critical flaws or any other thoughts. I also would appreciate if Gennadiy Rozental and John Torjo expressed their thoughts on possibility to review this library in parallel with John's solution, which is currently in the review queue. I would gladly discuss this privately, if they find it more suitable.

3 5

[asio] Compiler error with Sun C++ 5.9 on Solaris
by Boris 23 Sep '08

23 Sep '08

I sent this bug report to the Asio mailing list. As it didn't show up I send it here again. Sun C++ 5.9 on Solaris has a problem with the following conversions: "../../../boost/asio/detail/socket_ops.hpp", line 218: Error: Cannot assign void* to char*. "../../../boost/asio/detail/socket_ops.hpp", line 229: Error: Cannot assign void* to char*. "../../../boost/asio/detail/descriptor_ops.hpp", line 66: Error: Cannot assign void* to char*. "../../../boost/asio/detail/descriptor_ops.hpp", line 72: Error: Cannot assign void* to char*. Boris

2 1

[UUID] Still alive?
by Burc Arpat 23 Sep '08

23 Sep '08

Hi, Any idea what happened to the UUID library? I believe the mini review that was supposed to happen after the library got accepted provisionally never happened, right? Thanks, G. Burc ARPAT burcarpat.com pdgm.com

5 18

[gil] new io extension
by Christian Henning 23 Sep '08

23 Sep '08

Hi there, I've been busy working on the next version of gil's IO extension. The last iteration was very slow to compile especially when reading or writing tiff images. This and other problems have been fixed. As a result compilation is a lot faster but also a lot more tiff formats can now be read or written. Please grab the latest from: http://gil-contributions.googlecode.com/svn/trunk/gil_2/boost/gil/extension… This download is a little bigger than to usual since there are test images included. Please see my original announcement below for documentation. The goal of this extension is to substitute the original io lib which is part of gil, and though shipped with boost. To do this a review is probably needed. I'll work on a proper documentation as the next step. Can anyone tell me where to find a tutorial for creating quickdoc? There is one problem I cannot fix and would like to ask the experts on this list. Please read the readme.txt in libs\gil\io_new\unit_test which explains the scenario. This problem has something to do with erroneously choosing the wrong functions by the compiler. The enable_if metafunction doesn't work correctly here. As usual any feedback is welcome. Thanks, Christian ------------------------------------------------------- Hi there, over the past few months I have been working on a new version of gil's io extension. In this release I've added support for: * more image formats, most importantly bit_aligned images ( like 1bit images ), * reading of subimages like one row at a time for huge images, * reading image information, only. * having a unified interface for all sorts of devices, subimages, and converter objects. So far, png, jpeg, and tiff images are supported. In the not so distant future there will be bmp and pnm images added. You can grab the current version via subversion from: https://gil-contributions.googlecode.com/svn/trunk/gil_2/boost/gil/extensio… If desired I can supply a zip file to the vault. The images libraries can be grabbed from: ftp://ftp.uu.net/graphics/jpeg/jpegsrc.v6b.tar.gz ( www.ijg.org isn't responding ) http://www.libpng.org/pub/png/libpng.html http://www.libtiff.org/ It's highly advised to built your own version of the image lib you need. I installed the GNU's binaries for Windows, but unfortunately, I only had problems with them. The library is still header-only. When using boost::filesystem's paths, of course, you add a dependency to the filesystem lib. The Read Interface ------------------------ Reading an image can be done in multiple ways depending on what your need is. Like the old io lib there are 4 different ways of reading images. As there are: * read_image: Read image, the right amount of memory will be allocated beforehand. The supplied image type needs to be compatible with actual image file. * read_view: Read image, the image's memory must be already allocated. The supplied image type needs to be compatible with actual image file. * read_and_convert_image: Same as read_image, but the user can specify an color converter. * read_and_convert_view: Same as read_view, but the user can specify an color converter. There is a new function for reading image information. Since every image format has it's own set of tags, the library defines seperate image_read_info<format_tag> structures. Please see, for instance, the jpeg_tags.hpp header. As for the function parameters the following sections in the same order. 1. String for file name ( std::string, std::wstring, char*, boost::filesystem::path ) OR devices ( FILE*, TIFF*, std::ifstream ) 2. Image or view type 3. Optional: Subimage definition ( top_left corner + dimensions ) 4. Optional: Color converter. This parameter is only valid for converting functions. The default parameter is gil's default_color_converter 5. Format Tag. Reading the image information only takes parameter 1 and 5. Here are some examples for reading images: #include <boost/gil/extension/io_new/jpeg_read.hpp> // Read image information std::string filename( "..\\test_images\\jpg\\found online\\test.jpg" ); image_read_info< jpeg_tag > info = read_image_info( filename, tag_t() ); // Read image FILE* file = fopen( filename.c_str(), "rb" ); rgb8_image_t img; read_image( file, img, tag_t() ); // Read image ifstream in( filename.c_str(), ios::in | ios::binary ); rgb8_image_t img( 136, 98 ); read_view( in, view( img ), tag_t() ); // Read and convert image, use gil's default converter. rgb8_image_t img; read_and_convert_image( filename, img, tag_t() ); // Read a 10x10 subimage, starting from the top_left corner. rgb8_image_t img; read_image( filename, img, point_t( 0,0 ), point_t( 10, 10 ), tag_t() ); I have created some header files to support the old read interface. For example: #include <boost/gil/extension/io_new/jpeg_io_old.hpp> std::string filename( "..\\test_images\\jpg\\found online\\test.jpg" ); rgb8_image_t img( 136, 98 ); jpeg_read_view( filename, view( img ) ); The Write Interface --------------------------- The write interface is a much simpler than the read interface. Here, we only have write_view as the entry point. As for parameters the following sections are supported: 1. String for file name ( std::string, std::wstring, char*, boost::filesystem::path ) or devices ( FILE*, TIFF*, std::ofstream ) 2. View type 3. Optional: image_write_info< FormatTag > 4. Format type The image_write_info<...> structure defines a format specific properties which can be used when writing an image. A good example is jpeg's image quality value. Examples: #include <boost/gil/extension/io_new/tiff_write.hpp> // Write image string filename( "..\\test\\tiff\\test1.tif" ); gray8_image_t img( 320, 240 ); write_view( filename, view( img ), tiff_tag() ); // Write image string filename( "..\\test\\tiff\\test2.tif" ); TIFF* file = TIFFOpen( filename.c_str(), "w" ); rgb8_image_t img( 320, 240 ); write_view( file, view( img ), tag_t() ); I have created some header files to support the old write interface. For example: #include <boost/gil/extension/io_new/tiff_io_old.hpp> string filename( "..\\test\\tiff\\test3.tif" ); gray8_image_t img( 320, 240 ); tiff_write_view( filename, view( img ) ); The primary goal of this new version is to eventually replace the old io library which is part of boost's distribution. Do I need to apply for a review? I'm not sure how to go from here. I know there is still some work to do before a possible review. Documentation is lacking and support for dynamic image needs to be added. But what I want for now is to get some feedback on design and implementation. I would like to thank Lubomir Bourdev and Andreas Pokorny for their most valueable input. Thanks, Christian

1 0

[filesystem] has_branch_path()
by Robert Jones 23 Sep '08

23 Sep '08

I'm upgrading the Boost release in use at work from 1.33.1 to 1.36.0, with surprisingly few issues actually, but I am stuck on one thing. There's a function in 1.33.1, has_branch_path(), for which I cannot see the equivalent functionality in 1.36. Part of my difficulty is that the 1.33.1 header declares but does not define the function, and I cannot see where the body code is! Any suggestions would be appreciated at this point. Thanks. - Rob.

1 0

Re: [boost] [Review] Phoenix review starts today, September 21st
by dan marsden 23 Sep '08

23 Sep '08

Joel de Guzman wrote: >Mathias Gaunard wrote: >> Joel de Guzman wrote: >> Isn't the move to first-class Boost citizen a good opportunity to change >> some parts of the interface, and thus give a new version number? > >Indeed. As noted in the review blurb, V3 will be the future of phoenix. >The V3 interface will be assumed. The most major interface shifts are: > >1) ET engine: Use of Boost.Proto >2) Result type deduction: Use of Boost.Typeof >3) Type deduction protocol: Use of Boost.Resultof > >As far as the interface goes, we can take all that for granted. >We have the proof of concept. > I think I'd add to your list of major interface shifts: 4) Extension protocol: The current extension approach is tightly coupled to the hand rolled expression templates, and will need changing for a proto based v3, unless if I've missed yet more genius from Eric? Cheers Dan

2 1

[asio]Proper way to restart io_service
by Urberg, John 23 Sep '08

23 Sep '08

I have an application using boost::asio (v 1.35.0) that creates a udp multicast socket and an acceptor using an io_service and then calls io_service.run(). Additional sockets are created from acceptor.async_accept. My code needs to stop all the sockets and then restart them at a later point. When stopping the sockets, I close all the sockets I opened before deleting them. I then call io_service.stop(). When I restart things, I call io_service.reset(), recreate the udp multicast and acceptor sockets on the io_service and then call io_service.run(). When the io_service starts up again, it seems to have old operations on the queue and it tries to process them. I will usually get either a "vector iterator not dereferencable" error from a buffer on a deleted class or an error in a deleted version of the class that was processing async_accept before I stopped. Is there something additional I should be doing to clear the queue in the io_service? Thanks, John

1 1

asio and shared libraries problem (linux only)
by Berserker 23 Sep '08

23 Sep '08

io_service and shared libraries problem (linux only) Short question: is it safe to share asio "objects" (io_services, sockets and so on...) across shared libraries/modules? Long story: we are porting our project from Windows to Linux (actually we are working on Ubuntu with GCC 4.2.3) and we discovered a problem when an io_service is shared between modules: creating an io_service, for example, in the main executable and passing that to a shared library causes on Linux problems with handler's invocation. I stress that on Windows we have never reported the problem (with and without IOCP defining BOOST_ASIO_DISABLE_IOCP), instead on Linux it's always reproducible (event disabling the epoll implementation with BOOST_ASIO_DISABLE_EPOLL). The following example can reproduce the problem: "test_working_asio_example" let the shared library to create the io_service and in this case the "handle_timeout" and "handle_connection" are invoked as expected, instead "test_not_working_asio_example" freezes in the io_service::run invocation because the timeout is never invoked. ////////////////////////////////////////////////////////////////////////////////////////////////////////////////////// // Shared library code: ////////////////////////////////////////////////////////////////////////////////////////////////////////////////////// // connection.h //////////////////////////////////////////////////////////////////////////////////////////////////// #include <boost/asio.hpp> #include <boost/enable_shared_from_this.hpp> // NetExport on Windows is defined as _declspec(dllexport)/_declspec(dllimport) and on Linux is defined as __attribute__ ((visibility("default"))) class NetExport connection : public boost::enable_shared_from_this<connection> { public: connection(shared_ptr<boost::asio::io_service> service = shared_ptr<boost::asio::io_service>()); virtual ~connection(); boost::asio::io_service & service(); virtual void handle_connect(const boost::system::error_code &e); virtual void handle_timeout(); void connect(const boost::asio::ip::tcp::endpoint &endpoint, const boost::posix_time::time_duration &timeout); protected: shared_ptr<boost::asio::io_service> m_service; boost::asio::deadline_timer m_timeout; boost::asio::ip::tcp::socket m_socket; }; // connection.cpp //////////////////////////////////////////////////////////////////////////////////////////////////// #include "connection.h" #include <boost/bind.hpp> connection::connection(shared_ptr<boost::asio::io_service> service) : m_service(service ? service : shared_ptr<boost::asio::io_service>(new boost::asio::io_service())), m_timeout(*m_service), m_socket(*m_service) { std::cout << "connection::ctor" << std::endl; } connection::~connection() { std::cout << "connection::dctor" << std::endl; } boost::asio::io_service & connection::service() { return m_socket.io_service(); } void connection::handle_connect(const boost::system::error_code &e) { m_timeout.cancel(); if(e == boost::asio::error::operation_aborted) { std::cout << "connection::handle_connect (aborted)" << std::endl; return; } if(e) std::cout << "connection::handle_connect (error)" << std::endl; else std::cout << "connection::handle_connect (success)" << std::endl; } void connection::handle_timeout() { std::cout << "connection::handle_timeout" << std::endl; m_socket.close(); } void connection::connect(const boost::asio::ip::tcp::endpoint &endpoint, const boost::posix_time::time_duration &timeout) { m_socket.async_connect(endpoint, boost::bind(&connection::handle_connect, shared_from_this(), boost::asio::placeholders::error)); m_timeout.expires_from_now(timeout); m_timeout.async_wait(boost::bind(&connection::handle_timeout, shared_from_this())); } ////////////////////////////////////////////////////////////////////////////////////////////////////////////////////// // Main executable code: ////////////////////////////////////////////////////////////////////////////////////////////////////////////////////// void test_working_asio_example(const boost::asio::ip::tcp::endpoint &endpoint, const boost::posix_time::time_duration &timeout) { try { shared_ptr<connection> c(new connection()); c->connect(endpoint, timeout); c->service().run(); } catch(std::exception &e) { std::cerr << "Exception: " << e.what() << std::endl; } } void test_not_working_asio_example(const boost::asio::ip::tcp::endpoint &endpoint, const boost::posix_time::time_duration &timeout) { try { shared_ptr<connection> c(new connection(shared_ptr<boost::asio::io_service>(new boost::asio::io_service()))); c->connect(endpoint, timeout); c->service().run(); } catch(std::exception &e) { std::cerr << "Exception: " << e.what() << std::endl; } } int main(int argc, char *argv[]) { // 88.149.0.2:32123 is just a dummy endpoint that will "probably" timeout in 1 second ( if not try another fake one :) ) boost::asio::ip::tcp::endpoint endpoint(boost::asio::ip::address_v4::from_string("88.149.0.2"), 32123); boost::posix_time::time_duration timeout = boost::posix_time::seconds(1); test_working_asio_example(endpoint, timeout); test_not_working_asio_example(endpoint, timeout); return 0; } _________________________________________________________________ Stanco della solita finestra? Personalizza la tua Hotmail! http://www.messenger.it/personalizza.html#sfondi

1 0

bitmask operations (2)
by Arno Schödl 23 Sep '08

23 Sep '08

Sorry, _REGEX_BITMASK_OPS is from Dinkumware's library, so disregard:-( What is the boost way to define an enum enum EBitmask { ebitmaskFLAGA=1, ebitmaskFLAGB=2 }; such that operations like ebitmask |= ebitmaskFLAGA; can be used? In boost.regex, it is currently implemented specifically for match_flags: #if BOOST_WORKAROUND(BOOST_MSVC, < 1300) || BOOST_WORKAROUND(__BORLANDC__, BOOST_TESTED_AT(0x564)) typedef unsigned long match_flag_type; #else typedef match_flags match_flag_type; #ifdef __cplusplus inline match_flags operator&(match_flags m1, match_flags m2) { return static_cast<match_flags>(static_cast<boost::int32_t>(m1) & static_cast<boost::int32_t>(m2)); } inline match_flags operator|(match_flags m1, match_flags m2) { return static_cast<match_flags>(static_cast<boost::int32_t>(m1) | static_cast<boost::int32_t>(m2)); } inline match_flags operator^(match_flags m1, match_flags m2) { return static_cast<match_flags>(static_cast<boost::int32_t>(m1) ^ static_cast<boost::int32_t>(m2)); } inline match_flags operator~(match_flags m1) { return static_cast<match_flags>(~static_cast<boost::int32_t>(m1)); } inline match_flags& operator&=(match_flags& m1, match_flags m2) { m1 = m1&m2; return m1; } inline match_flags& operator|=(match_flags& m1, match_flags m2) { m1 = m1|m2; return m1; } inline match_flags& operator^=(match_flags& m1, match_flags m2) { m1 = m1^m2; return m1; } #endif #endif Regards, Arno -- Dr. Arno Schoedl · aschoedl(a)think-cell.com Technical Director think-cell Software GmbH · Invalidenstr. 34 · 10115 Berlin, Germany http://www.think-cell.com · phone +49-30-666473-10 · toll-free (US) +1-800-891-8091 Directors: Dr. Markus Hannebauer, Dr. Arno Schoedl · Amtsgericht Charlottenburg, HRB 85229

1 0