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

[iostreams and serialization] serialize via iostreams
by Pooyan McSporran 15 Jan '08

15 Jan '08

I'm trying to use a combination of the iostreams library and the serialization library in order to be able to serialise objects and send them over a socket. I've written a class called "SocketDevice" which implements a bidirectional iostreams instance, and I'm trying to use this with serialization, in particular the binary_oarchive and binary_iarchive archive models. The problem is that when I do this, the code ends up calling a copy constructor (which doesn't exist) on my SocketDevice class. However I don't want to implement a copy constructor for this class as it doesn't make sense (as it manages a socket and a buffer for that socket, etc). The interface of my SocketDevice class looks like this: class SocketDevice : public boost::iostreams::device<boost::iostreams::bidirectional> { public: typedef char char_type; SocketDevice (int sock); ~SocketDevice (); std::streamsize read (char *s, std::streamsize n); std::streamsize write (const char *s, std::streamsize n); private: const int sock; char *buffer; size_t bufferSize; }; and I'm trying to do the object sending/receiving via template methods, eg: template<class C> void sendObject (const C& data, int sock) { boost::iostreams::stream_buffer<SocketDevice> buf (sock); std::ostream s (&buf); boost::archive::binary_oarchive oa (s); oa << data; } The copy constructor appears to be synthesised when the 'buf' object is instantiated in the above template method. My guess is that I'm doing something wrong, but I can't see what. I've also tried splitting my SocketDevice class from a bidirectional one to a pair of input & output ones, but with the same result. I've also tried making sendObject() a normal (non-template) method, this makes no difference. I realise that there are issues with trying to combine socket communications with object serialisation, but I'm still curious as to why I have this copy constructor issue.

2 2

Re: [Boost-users] templates w/ non-type arguments
by Hicham Mouline 15 Jan '08

15 Jan '08

I realize my question was not complete! Is it possible to write the 3 x 3 x 3 explicit instantiations, not with 27 lines of code, but perhaps in some kind of loop? Rds, -----Original Message----- From: boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Michael Gopshtein Sent: 15 January 2008 08:51 To: boost-users(a)lists.boost.org Subject: Re: [Boost-users] templates w/ non-type arguments "Hicham Mouline" <hicham(a)mouline.org> wrote in message news:20080114191355.0EA71200C2@ws6-7.us4.outblaze.com... > Hello, > > I have: > enum ParamType { FLAT, CURVE1D, CURVE2D }; > > template<ParamType r, ParamType q, ParamType v> > class TIP: > { > }; > > I would like to explicitly write all the possible full specializations of > TIP... > template class TIP<FLAT, FLAT, FLAT>; template<> class TIP<FLAT, FLAT, FLAT> {}; template<> class TIP<FLAT, FLAT, CURVE1D> {}; etc. > ... > > regards,

2 1

Boost.Test Framework to test a DLL
by Plonka Christian 15 Jan '08

15 Jan '08

Hi, I'm planning to change from CppUnit to Boost.Test for unit testing since it is now possible to integrate unit tests also in a DLL. Nevertheless I do encounter some problems here. The code is (I guess you'll recognize it): //---------------------------------------------------------------------- --- #define BOOST_TEST_DYN_LINK #include <boost/test/unit_test.hpp> using namespace boost::unit_test; BOOST_AUTO_TEST_CASE( test1 ) // void test1() { int i = 0; BOOST_CHECK_EQUAL( i, 2 ); } BOOST_AUTO_TEST_CASE( test2 ) { BOOST_CHECKPOINT("About to force division by zero!"); int i = 1, j = 0; i = i / j; } extern "C" { __declspec(dllexport) bool init_unit_test() { printf("Initializing\n"); framework::master_test_suite().p_name.value = "Test runner test"; // framework::master_test_suite().add( BOOST_TEST_CASE( &test1 ) ); return true; } } //---------------------------------------------------------------------- --- I the sample (test_runner_test.dll) it works fine but when I use it in my DLL I get: C:\Projekte\Test\NetControl\bin>console_test_runner --test NetCtrld.dll Initializing Test setup error: test tree is empty I also tried the commented version using master_test_suite().add() without any change. Any hint what I can try or how I can debug this? Thanks, Christian

2 1

MetaComm and Boost Consulting SVN daily snapshot services
by Joaquín Mª López Muñoz 15 Jan '08

15 Jan '08

Hello, Some time ago, there were two places where users could download daily snapshots of the Boost repository: * http://engineering.meta-comm.com/boost.aspx (linked from boost.org) * http://www.boost-consulting.com/boost.tar.bz2 Alas, none of them are being updated anymore. It'd be great if at least one could be put back in business, as this is a very useful service for casual Boost users without SVN tools. Thank you, Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

1 0

[DateTime] format flag to print single-digit hour?
by Boris 15 Jan '08

15 Jan '08

I'm using the Boost.DateTime IO system to create customized date/time strings. While the library supports quite a lot of format flags out of the box I'm missing a format flag to print a single-digit hour. There is the format flag %k though (see http://www.boost.org/doc/html/date_time/date_time_io.html#date_time.format_…) - however it adds a preceding blank for single-digit hours. I guess there is currently no format flag for single-digit hours? Is it possible then to extend the Boost.DateTime IO system somehow to add your own format flag? While I could use another library like Boost.Format additionally I prefer to stick to one (it might make more sense then to switch to Boost.Format completely)? Boris

1 0

templates w/ non-type arguments
by Hicham Mouline 15 Jan '08

15 Jan '08

Hello, I have: enum ParamType { FLAT, CURVE1D, CURVE2D }; template<ParamType r, ParamType q, ParamType v> class TIP: { }; I would like to explicitly write all the possible full specializations of TIP... template class TIP<FLAT, FLAT, FLAT>; ... regards,

2 1

Re: [Boost-users] [boost] [switch_] Compound Cases [was Case Concept]
by Steven Watanabe 15 Jan '08

15 Jan '08

AMDG Joel de Guzman wrote: > Steven Watanabe wrote: > >> My concern is >> 1) fall-through can't easily be added to the interface. >> > > I have an idea I'd like to post in another update to the > case concept. > Great. > The point is that it is just another case. Whatever the > sequenced_case is, it's just a model of the case concept. > Sure it still has to be documented, but not as a separate > concept, but as a model of it. > > Also, to me, it's most trivial to just make it an ET > tree: > > template< class CaseL, class CaseR > > struct binary_case > { > CaseL l; > CaseR r; > > binary_case(CaseL const& l, CaseR const& r) > : l(l), r(r) {} > > typedef mpl::joint_view< > typename CaseL::labels, typename CaseR::labels > > labels; > > template< typename Result, class I > > Result apply(I); > }; > > Key points: > > * apply is part of the concept. In this case, it dispatches > to l or r depending on I > > * hmmm.... maybe labels should be an mpl set. > No, thank you. mpl set is buggy and slow. Also, one thing that needs to be nailed down is: What Is I? Tobias was using it as the index into the list of labels: mpl::int_<0>, mpl::int_<1>, mpl::int_<2>, ... In my original interface and as you seem to be using it I is one of: mpl::at_c<labels, 0>::type, mpl::at_c<labels, 1>::type, mpl::at_c<labels, 2>::type In Christ, Steven Watanabe

1 0

Re: [Boost-users] [boost] [switch_] Case Concept [ was Re: formal review of Switch library...]
by Steven Watanabe 14 Jan '08

14 Jan '08

AMDG Joel de Guzman wrote: > Valid Expressions: > > Expression Semantics > ---------- > -------------------------------------------------------- > C::labels An MPL Sequence of Integral Constants > I think that a case should only have a single label. Allowing multiple labels makes the implementation harder without adding any significant utility. See below. > case_<I>(f) Returns a Case object with supplied > <snip more generators> > These can return fusion sequences of cases instead of plain cases. This has the additional benefit that switch_ can be specified as taking a fusion sequence of cases, without having to handle a single case specially. > default_(f) Returns a Case object with an empty labels list. > forwarding to the encapsulated function object f. > From the standpoint of the implementor of switch_, how do I figure out which Case is the default? > * case_c and case_range_c are simple shortcuts. The type of > integral constant is int. The actual type can be casted to > the actual switch parameter. I think this is safe Since the value is known at compile time the cast can be checked at compile time to detect overflow. In Christ, Steven Watanabe

2 3

Re: [Boost-users] [boost] [switch_] Case Concept [ was Re: formal review of Switch library...]
by Steven Watanabe 14 Jan '08

14 Jan '08

AMDG Tobias Schwinger wrote: > Joel de Guzman wrote: > >> c0, c1, ... cN Returns a fusion sequence of Case objects >> > > seemingly equivalent to > > (c0, c1, ... cN) > > (note: Application of comma operator ;-)). > > > ?! Why doesn't it just return another (compound) Case object and leave > the Sequence an unspecified implementation detail... > So you want switch_ to be template<class R, class I, class Cases> requires Case<Cases> && BuiltInIntegerOrEnum<I> R switch(I i, Cases cases); IMO, There is a very big problem here. Suppose that you have a fusion sequence that holds your cases and function objects coming from somewhere else. The problem of adapting it to switch_ is no easier than it would be with my original interface. In Christ, Steven Watanabe

3 6

Re: [Boost-users] [boost::logging] using rolling files failed
by John Torjo 14 Jan '08

14 Jan '08

Hi Benjamin, Sorry for that. It's because I introduced a breaking change: after you initialize the log, call: g_logger->turn_cache_off(); That should do the trick. Best, John > Hi John, > > I'm working on integrating your last modifications about flushing > rolling files, but I encounter some problems. > > With version V0.11.7, I change rolling_file.hpp (see attached file) to > flush logs each time. It works fine. > > /destination::rolling_file_settings settings; > settings.file_count( 10 ); > settings.max_size_bytes( 5242880 ); > destination::rolling_file loggerFile( logFile.GetPath(), settings ); > g_logger->writer().add_destination( loggerFile ); > / > > With last version (revision 42765), I just add one line. / > / > > /destination::rolling_file_settings settings;/ > /settings.file_count( 10 );/ > /settings.max_size_bytes( 5242880 ); / > */=> settings.flush_each_time(true); // add this line/* > /destination::rolling_file loggerFile( logFile.GetPath(), settings );/ > /g_logger->writer().add_destination( loggerFile );/ > > Then it doesn't work. > I put a break point in rolling_file_info#write but my program does not > enter in it anymore ! > I think that rolling file objects are not instanciated because output > files are MY_FILE.txt and not MY_FILE.txt.1 > > Even if it will not compile alone, I give you my class Logger to see > my implementation. > > Regards, > Benjamin > > > ------------------------------------------------------------------------ > > // destination_rolling_file.hpp > > // Boost Logging library > // > // Author: John Torjo, www.torjo.com > // > // Copyright (C) 2007 John Torjo (see www.torjo.com for email) > // > // Distributed under the Boost Software License, Version 1.0. > // (See accompanying file LICENSE_1_0.txt or copy at > // http://www.boost.org/LICENSE_1_0.txt) > // > // See http://www.boost.org for updates, documentation, and revision history. > // See http://www.torjo.com/log2/ for more details > > > #ifndef JT28092007_destination_rolling_file_HPP_DEFINED > #define JT28092007_destination_rolling_file_HPP_DEFINED > > #if defined(_MSC_VER) && (_MSC_VER >= 1020) > # pragma once > #endif > > #if defined(_MSC_VER) > #pragma warning ( disable : 4355) > #endif > > #include <boost/logging/detail/fwd.hpp> > #include <boost/logging/detail/manipulator.hpp> > #include <boost/logging/format/destination/convert_destination.hpp> > #include <fstream> > #include <string> > #include <sstream> > #include <boost/filesystem/path.hpp> > #include <boost/filesystem/operations.hpp> > > namespace boost { namespace logging { namespace destination { > > > /** > @brief Settings you can pass to the rolling file. To see how it's used, see @ref dealing_with_flags. > */ > struct rolling_file_settings { > typedef boost::logging::detail::flag<rolling_file_settings> flag; > > rolling_file_settings() > : max_size_bytes(this, 1024 * 1024) > , file_count(this, 10) > , initial_erase(this, false) > , start_where_size_not_exceeded(this, true) > {} > > /// maximum size in bytes, by default 1Mb > flag::t<int> max_size_bytes; > /// how many files has a rolling file, by default, 10 > flag::t<int> file_count; > /// if true, it initially erases all files from the rolling file (by default, false) > flag::t<bool> initial_erase; > /// if true, it starts with the first file that hasn't exceeded the max size; > /// otherwise, it starts with the first file (default = true) > flag::t<bool> start_where_size_not_exceeded; > }; > > namespace detail { > template<class convert_dest > > struct rolling_file_info { > > rolling_file_info (const std::string& name_prefix, rolling_file_settings flags ) > // many thanks to Martin Bauer > : m_name_prefix(name_prefix), m_flags(flags), m_cur_idx(0) { > namespace fs = boost::filesystem; > > if ( m_flags.initial_erase()) { > for ( int idx = 0; idx < m_flags.file_count(); ++idx) > if ( fs::exists( file_name(idx) )) > fs::remove( file_name(idx) ); > } > > // see what file to start from > if ( m_flags.start_where_size_not_exceeded() ) { > for ( m_cur_idx = 0; m_cur_idx < m_flags.file_count(); ++m_cur_idx ) > if ( fs::exists( file_name(m_cur_idx) )) { > if ( fs::file_size( file_name(m_cur_idx)) < m_flags.max_size_bytes() ) > // file hasn't reached max size > break; > } > else > // file not found, we'll create it now > break; > > } > > recreate_file(); > } > > std::string file_name(int idx) { > std::ostringstream out; > out << m_name_prefix << "." << (idx+1); > return out.str(); > } > > void recreate_file() { > m_out = boost::shared_ptr< std::basic_ofstream<char_type> >(new std::basic_ofstream<char_type>( file_name(m_cur_idx).c_str(), > std::ios_base::out | std::ios_base::app)); > m_cur_size = 0; > } > > template<class msg_type> void write( const msg_type& msg) { > convert_dest::write(msg, (*m_out) ); > > // bdd 2007-12-10 : flush each time > m_cur_size += static_cast<int>( msg.size() ); > m_out->flush(); > > // bdd > //if ( m_out->tellp() > m_flags.max_size_bytes()) { > if ( m_cur_size > m_flags.max_size_bytes()) { > m_cur_idx = (m_cur_idx + 1) % m_flags.file_count(); > recreate_file(); > } > } > > boost::shared_ptr< std::basic_ofstream<char_type> > m_out; > std::string m_name_prefix; > rolling_file_settings m_flags; > // the index of the current file > int m_cur_idx; > > // bdd 2007-12-10 : flush each time > //size_t m_cur_size; > int m_cur_size; > }; > } > > /** > @brief Writes to multiple files: name_prefix.1, name_prefix.2, ... name_prefix.N, and then restarts from 1. > > We first write to name_prefix.1. > > The log has a max_size. When max_size is reached, we start writing to name_prefix.2. When max_size is reached, we start writing to name_prefix.3. > And so on, until we reach name_prefix.N (N = file_count). When that gets fool, we start over, with name_prefix.1. > */ > template<class convert_dest = do_convert_destination > struct rolling_file_t : is_generic, non_const_context<detail::rolling_file_info<convert_dest> > { > typedef non_const_context<detail::rolling_file_info<convert_dest> > non_const_context_base; > > /** > Constructs a rolling file > > @param name_prefix the name to be used as prefix for the files > > @param flags [optional] extra settings to pass to the rolling file. See rolling_file_settings and @ref dealing_with_flags. > */ > rolling_file_t(const std::string & name_prefix, rolling_file_settings flags = rolling_file_settings() ) : non_const_context_base(name_prefix, flags) {} > > template<class msg_type> void operator()( const msg_type & msg) const { > non_const_context_base::context().write(msg); > } > > bool operator==(const rolling_file_t & other) const { > return non_const_context_base::context().m_name_prefix == other.context().m_name_prefix; > } > }; > > /** @brief rolling_file_t with default values. See rolling_file_t > > @copydoc rolling_file_t > */ > typedef rolling_file_t<> rolling_file; > > > > > }}} > > #endif > > > ------------------------------------------------------------------------ > > > > //============================================================================= > // Includes > //============================================================================= > #include "StdAfx.h" > #include "common/log/Logger.h" > > //----- MEDCommon ----- > #include "common/system/ApplicationHelper.h" > #include "common/io/Directory.h" > #include "common/system/Time.h" > > //----- boost ----- > #pragma warning(disable: 4541) > > #include "boost/logging/tags.hpp" > #include "boost/logging/defaults.hpp" > #include "boost/logging/format.hpp" > #include "boost/logging/format_all.hpp" > #include "boost/logging/format_fwd.hpp" > #include "boost/logging/format_ts.hpp" > #include "boost/logging/logging.hpp" > #include "boost/logging/detail/error.hpp" > #include "boost/logging/detail/filter.hpp" > #include "boost/logging/detail/find_gather.hpp" > #include "boost/logging/detail/format_msg_type.hpp" > #include "boost/logging/detail/format_write_detail.hpp" > #include "boost/logging/detail/forward_constructor.hpp" > #include "boost/logging/detail/fwd.hpp" > #include "boost/logging/detail/level.hpp" > #include "boost/logging/detail/log_keeper.hpp" > #include "boost/logging/detail/logger.hpp" > #include "boost/logging/detail/macros.hpp" > #include "boost/logging/detail/manipulator.hpp" > #include "boost/logging/detail/scenario.hpp" > #include "boost/logging/detail/template.hpp" > #include "boost/logging/detail/use_format_write.hpp" > // raw_doc ? > #include "boost/logging/detail/ts/ts.hpp" > #include "boost/logging/detail/ts/ts_boost.hpp" > #include "boost/logging/detail/ts/ts_none.hpp" > //#include "boost/logging/detail/ts/ts_posix.hpp" > #include "boost/logging/detail/ts/ts_resource.hpp" > #include "boost/logging/detail/ts/ts_win32.hpp" > #include "boost/logging/detail/tss/tss.hpp" > #include "boost/logging/detail/tss/tss_ensure_proper_delete.hpp" > #include "boost/logging/detail/tss/tss_impl.hpp" > //#include "boost/logging/detail/tss/tss_impl_pthread.hpp" > #include "boost/logging/detail/tss/tss_impl_win32.hpp" > #include "boost/logging/format/array.hpp" > #include "boost/logging/format/op_equal.hpp" > #include "boost/logging/format/optimize.hpp" > #include "boost/logging/format/destination/convert_destination.hpp" > #include "boost/logging/format/destination/defaults.hpp" > #include "boost/logging/format/destination/file.hpp" > #include "boost/logging/format/destination/rolling_file.hpp" > #include "boost/logging/format/destination/shared_memory.hpp" > #include "boost/logging/format/formatter/convert_format.hpp" > #include "boost/logging/format/formatter/defaults.hpp" > #include "boost/logging/format/formatter/tags.hpp" > #include "boost/logging/format/formatter/thread_id.hpp" > #include "boost/logging/format/formatter/time.hpp" > #include "boost/logging/gather/ostream_like.hpp" > #include "boost/logging/tag/defaults.hpp" > #include "boost/logging/writer/format_write.hpp" > #include "boost/logging/writer/on_dedicated_thread.hpp" > #include "boost/logging/writer/ts_write.hpp" > > using namespace boost::logging; > > //----- Step 3 : Specify your logging class(es) ----- > //typedef logger_format_write< > log_type; > // thread safe > typedef logger_format_write< default_, default_, writer::threading::ts_write > log_type; > //typedef logger_format_write< default_, default_, writer::threading::on_dedicated_thread > log_type; > > //----- Step 4: declare which filters and loggers you'll use (usually in a header file) ----- > // filter > BOOST_DECLARE_LOG_FILTER(g_log_level, level::holder ) > BOOST_DECLARE_LOG_FILTER(g_audit_filter, filter::ts ) > > // logger > BOOST_DECLARE_LOG(g_logger, log_type) > BOOST_DECLARE_LOG(g_audit, log_type) > BOOST_DECLARE_LOG(g_debug, log_type) > > //----- Step 5: define the macros through which you'll log ----- > > //----- Step 6: Define the filters and loggers you'll use (usually in a source file) ----- > // filter > BOOST_DEFINE_LOG_FILTER(g_log_level, level::holder ) // holds the application log level > BOOST_DEFINE_LOG_FILTER(g_audit_filter, filter::ts ) > BOOST_DEFINE_LOG_FILTER(g_debug_filter, filter::ts ) > //BOOST_DEFINE_LOG_FILTER(g_audit_filter, filter::no_ts ) > // logger > BOOST_DEFINE_LOG(g_logger, log_type) > BOOST_DEFINE_LOG(g_audit, log_type) > BOOST_DEFINE_LOG(g_debug, log_type) > > using namespace common::log; > > //============================================================================= > // Global functions > //============================================================================= > void > Audit( const std::ostringstream & msg ) > { > Info( msg ); > BOOST_LOG_USE_LOG_IF_FILTER(g_audit, g_audit_filter->is_enabled() ) << "\t[AUDIT]\t" << msg.str(); > } > > void > Debug( const std::ostringstream & msg ) > { > BOOST_LOG_USE_LOG_IF_FILTER(g_debug, g_debug_filter->is_enabled() ) << "\t[DEBUG]\t" << msg.str(); > } > > void > Trace2( const std::ostringstream & msg ) > { > Debug( msg ); > common::log::Logger::s_traces.Push( msg.str() ); > } > > void > Info( const std::ostringstream & msg ) > { > BOOST_LOG_USE_LOG_IF_LEVEL(g_logger, g_log_level, info ) << "\t[INFO]\t" << msg.str(); > BOOST_LOG_USE_LOG_IF_FILTER(g_debug, g_debug_filter->is_enabled() ) << "\t[INFO]\t" << msg.str(); > } > > void > Warning( const std::ostringstream & msg ) > { > BOOST_LOG_USE_LOG_IF_LEVEL(g_logger, g_log_level, warning ) << "\t[WARN]\t" << msg.str(); > BOOST_LOG_USE_LOG_IF_FILTER(g_debug, g_debug_filter->is_enabled() ) << "\t[WARN]\t" << msg.str(); > } > > void > Error( const std::ostringstream & msg ) > { > if ( ! common::log::Logger::IsInitialized() ) > { > common::log::Logger::Init( "INIT" ); > } > if ( ! common::log::Logger::s_traces.IsEmpty() ) > { > // > vector<string> traces = common::log::Logger::s_traces.ToArray(); > for ( size_t i=0; i < traces.size(); i++ ) > { > BOOST_LOG_USE_LOG_IF_LEVEL(g_logger, g_log_level, error ) << "\t[TRACE]\t" << traces[i]; > } > } > BOOST_LOG_USE_LOG_IF_LEVEL(g_logger, g_log_level, error ) << "\t[ERROR]\t" << msg.str(); > BOOST_LOG_USE_LOG_IF_FILTER(g_debug, g_debug_filter->is_enabled() ) << "\t[ERROR]\t" << msg.str(); > } > > void > Exception( const std::ostringstream & msg ) > { > if ( ! common::log::Logger::IsInitialized() ) > { > common::log::Logger::Init( "INIT" ); > } > if ( ! common::log::Logger::s_traces.IsEmpty() ) > { > // > vector<string> traces = common::log::Logger::s_traces.ToArray(); > for ( size_t i=0; i < traces.size(); i++ ) > { > BOOST_LOG_USE_LOG_IF_LEVEL(g_logger, g_log_level, fatal ) << "\t[TRACE]\t" << traces[i]; > } > } > BOOST_LOG_USE_LOG_IF_LEVEL(g_logger, g_log_level, fatal ) << "\t[FATAL]\t" << msg.str(); > BOOST_LOG_USE_LOG_IF_FILTER(g_debug, g_debug_filter->is_enabled() ) << "\t[FATAL]\t" << msg.str(); > } > > > > //============================================================================= > // Class attributs > //============================================================================= > bool Logger::s_isInitialized = false; > bool Logger::MODE_DEBUG = false; > common::container::RollingStack<string> Logger::s_traces( 15 ); > > //============================================================================= > // Class methods > //============================================================================= > void > Logger::SetLevel( LEVEL level ) > { > g_audit_filter->set_enabled(true); > g_debug_filter->set_enabled(false); > switch ( level ) > { > case LEVEL_DEBUG : > Logger::MODE_DEBUG = true; > g_debug_filter->set_enabled(true); > g_log_level->set_enabled(level::debug); // debug > break; > case LEVEL_INFO : > g_log_level->set_enabled(level::info); // info + warning + ... > break; > case LEVEL_ERROR : > g_log_level->set_enabled(level::error); // error + fatal + ... > break; > default: > g_log_level->set_enabled(level::info); > break; > } > > } > > bool > Logger::IsInitialized() > { > return s_isInitialized; > } > > void > Logger::Init( const string & product ) > { > if ( s_isInitialized ) > { > return; > } > > // check log dir > common::system::ApplicationHelper ah; > common::io::Directory dir( ah.GetPath() + "logfiles" ); > dir.CheckAndCreate(); > > // init file names > //string date = common::system::Time::GetTime( common::system::Time::FORMAT_AAAA_MM_JJ ); > //common::io::File logFile( dir.GetPath() + date + "_" + product + ".txt" ); > //common::io::File auditFile( dir.GetPath() + date + "_AUDIT_" + product + ".txt" ); > common::io::File logFile( dir.GetPath() + product + ".txt" ); > common::io::File auditFile( dir.GetPath() + "AUDIT_" + product + ".txt" ); > common::io::File debugFile( dir.GetPath() + "DEBUG_" + product + ".txt" ); > > // Step 7: add formatters and destinations > // That is, how the message is to be formatted... > g_logger->writer().add_formatter( formatter::time("$dd/$MM/$yyyy - $hh:$mm.$ss ") ); > g_logger->writer().add_formatter( formatter::idx() ); > g_logger->writer().add_formatter( formatter::append_newline() ); > //g_log_err->writer().add_formatter( formatter::tag::module() ); // tag::file_line() ); > //g_log_err->writer().add_formatter( formatter::tag::level() ); > > g_audit->writer().add_formatter( formatter::time("$dd/$MM/$yyyy - $hh:$mm.$ss ") ); > g_audit->writer().add_formatter( formatter::idx() ); > g_audit->writer().add_formatter( formatter::append_newline() ); > > g_debug->writer().add_formatter( formatter::time("$dd/$MM/$yyyy - $hh:$mm.$ss ") ); > g_debug->writer().add_formatter( formatter::idx() ); > g_debug->writer().add_formatter( formatter::append_newline() ); > > g_logger->writer().add_destination( destination::cout() ); > > // bdd : rolling file : pb de flush (garde les donnees en cache) > destination::rolling_file_settings settings; > settings.file_count( 10 ); > settings.max_size_bytes( 5242880 ); // bytes = 5M > //settings.flush_each_time(true); > destination::rolling_file loggerFile( logFile.GetPath(), settings ); > g_logger->writer().add_destination( loggerFile ); > > g_debug->writer().add_destination( destination::dbg_window() ); > > destination::rolling_file_settings settingsD; > settingsD.file_count( 30 ); > settingsD.max_size_bytes( 10000000 ); // ~10M > //settingsD.flush_each_time(true); > g_debug->writer().add_destination( destination::rolling_file( debugFile.GetPath(), settingsD ) ); > > // bdd xml : en attente > //g_log_err->writer().add_destination( as_xml("logerror.xml") ); > > g_audit->writer().add_destination( destination::file( auditFile.GetPath() ) ); > > #ifdef _DEBUG > SetLevel( Logger::LEVEL_DEBUG ); > #else > SetLevel( Logger::LEVEL_INFO ); > #endif > s_isInitialized = true; > // Step 9 : Enjoy! > } > > > //============================================================================= > // Constructor and destructor > //============================================================================= > Logger::Logger(void) > : common::app::Object("common::log::Logger") > { > } > > Logger::~Logger(void) > { > } > > //============================================================================= > // Public methods > //============================================================================= > > > ------------------------------------------------------------------------ > > //* Step 1: (optional) Specify your format message class and/or destination message class. By default, it's std::(w)string. You'll use this when you want a optimize string class. > //* Step 2: (optional) Specify your formatter & destination base classes > //* Step 3: Specify your logger class(es) > //* Step 4: Declare the filters and loggers you'll use (in a header file) > //* Step 5: Define the macros through which you'll do logging > //* Step 6: Define the loggers and the filters you'll use (in a source file). We need this separation (into declaring and defining the logs/filters), in order to make compilation times fast. > //* Step 7: Add formatters and destinations. That is, how the message is to be formatted... > //* Step 8: Use it > //* Step 9: Enjoy the results! > > //* debug (smallest level), > //* info, > //* warning , > //* error , > //* fatal (highest level) > > #ifndef _COMMON_LOG_LOGGER_H_ > #define _COMMON_LOG_LOGGER_H_ > #pragma once > > //============================================================================= > // Includes > //============================================================================= > //----- MEDCommon ----- > #include "../commonIncludes.h" > #include "../app/Object.h" > #include "StackLog.h" > #include "common/txt/StringHelper.h" > #include "common/container/RollingStack.h" > > void MEDCOMMON_API Audit( const std::ostringstream & msg ); > void MEDCOMMON_API Debug( const std::ostringstream & msg ); > void MEDCOMMON_API Trace2( const std::ostringstream & msg ); > void MEDCOMMON_API Info( const std::ostringstream & msg ); > void MEDCOMMON_API Warning( const std::ostringstream & msg ); > void MEDCOMMON_API Error( const std::ostringstream & msg ); > void MEDCOMMON_API Exception( const std::ostringstream & msg ); > > #define MED_FUNCTION \ > common::log::StackLog log( __FUNCTION__ ); > > #define MED_FUNCTION2( msg ) \ > ostringstream s; \ > s << msg; \ > common::log::StackLog log( __FUNCTION__, s ); > > #define MED_METHOD( object ) \ > common::log::StackLog log( object,__FUNCTION__ ); > > #define MED_METHOD2( object, params ) \ > ostringstream s; \ > s << params; \ > common::log::StackLog log( object,__FUNCTION__, s ); > > #define MED_AUDIT( module, msg ) \ > { \ > ostringstream s; \ > s << "[" << module << "]\t" \ > << msg; \ > Audit( s ); \ > } > > #define MED_DBG2( module, msg ) \ > { \ > if ( common::log::Logger::MODE_DEBUG ) \ > { \ > string file = __FILE__; \ > string fileName = common::txt::StringHelper::LastToken(file,"\\"); \ > ostringstream s; \ > s << "[" << module << "]\t" \ > << msg \ > << " (" \ > << fileName \ > << "#" \ > << __FUNCTION__ \ > << " L." \ > << __LINE__ \ > << ")"; \ > Debug( s ); \ > } \ > } > > #define MED_TRC2( module, msg ) \ > { \ > string file = __FILE__; \ > string fileName = common::txt::StringHelper::LastToken(file,"\\"); \ > ostringstream s; \ > s << "[" << module << "]\t" \ > << msg \ > << " (" \ > << fileName \ > << "#" \ > << __FUNCTION__ \ > << " L." \ > << __LINE__ \ > << ")"; \ > Trace2( s ); \ > } > > #define MED_INF2( module, msg ) \ > { \ > ostringstream s; \ > s << "[" << module << "]\t" \ > << msg; \ > Info( s ); \ > } > > #define MED_WARN2( module, msg ) \ > { \ > string file = __FILE__; \ > string fileName = common::txt::StringHelper::LastToken(file,"\\"); \ > ostringstream s; \ > s << "[" << module << "]\t" \ > << msg \ > << " (" \ > << fileName \ > << "#" \ > << __FUNCTION__ \ > << " L." \ > << __LINE__ \ > << ")"; \ > Warning( s ); \ > } > > #define MED_ERR2( module, msg ) \ > { \ > string file = __FILE__; \ > string fileName = common::txt::StringHelper::LastToken(file,"\\"); \ > ostringstream s; \ > s << "[" << module << "]\t" \ > << msg \ > << " (" \ > << fileName \ > << "#" \ > << __FUNCTION__ \ > << " L." \ > << __LINE__ \ > << ")"; \ > Error( s ); \ > } > > #define MED_EXC2( module, msg ) \ > { \ > string file = __FILE__; \ > string fileName = common::txt::StringHelper::LastToken(file,"\\"); \ > ostringstream s; \ > s << "[" << module << "]\t" \ > << msg \ > << " (" \ > << fileName \ > << "#" \ > << __FUNCTION__ \ > << " L." \ > << __LINE__ \ > << ")"; \ > Exception( s ); \ > } > > namespace common > { > namespace log > { > class MEDCOMMON_API Logger : public common::app::Object > { > > > > //============================================================================= > // Constants > //============================================================================= > public: > enum LEVEL { > LEVEL_DEBUG , > LEVEL_INFO , > LEVEL_ERROR }; > > //============================================================================= > // Class attributs > //============================================================================= > public: > static bool MODE_DEBUG; > // traces > static common::container::RollingStack<string> s_traces; > > private: > static bool s_isInitialized; > > //============================================================================= > // Class methods > //============================================================================= > public: > static void SetProduct( const string & product ); > static bool IsInitialized(); > static void Init( const string & product ); > static void SetLevel( LEVEL level ); > > //============================================================================= > // Attributs > //============================================================================= > private: > > > //============================================================================= > // Constructor and destructor > //============================================================================= > private: > Logger(); > virtual ~Logger(); > > //============================================================================= > // Public methods > //============================================================================= > public: > > //============================================================================= > // Other methods > //============================================================================= > protected: > > }; > } // namespace log > } // namespace common > > #endif // _COMMON_LOG_LOGGER_H_ > > -- http://John.Torjo.com -- C++ expert ... call me only if you want things done right

1 0

[Math] Feedback wanted on design issue.
by John Maddock 14 Jan '08

14 Jan '08

Hi folks I'd like some user feedback on an error-handling design issue if you're all willing :-) To the Sandbox "development" version of Boost.Math I've recently added equivalent functionality to the C99 round/trunc/modf functions: these convert floating point values to integers or to integer and fractional parts. However, there are two possible error conditions: 1) The input value is not a number (NaN). 2) The input value is outside the range of the integer type. We could handle these using the existing error handlers for domain_error's and overflow_error's respectively, but there's a problem: Users may legitimately turn off the throwing of exceptions from domain or overflow errors and prefer the functions to return NaN's and infinities instead. But this clearly wouldn't make as much sense for these particular conversion functions given that integers don't support either of these states.... So I'm tempted to add another error handler specific for integer conversion failures: the question then is whether this is starting down a slippery slope to too many error types making the library too hard to understand/use. Currently we already have: Pole Errors. Domain Errors. Overflow Errors. Underflow Errors. Denorm Errors. Internal Evaluation Errors. See http://svn.boost.org/svn/boost/trunk/libs/math/doc/sf_and_dist/html/math_to… for the details. So am I going overboard with error types, or worrying about nothing? Thanks for any thoughts/user experience you may have, Regards, John Maddock.

1 0

testing , please ignore
by John Torjo 14 Jan '08

14 Jan '08

-- http://John.Torjo.com -- C++ expert ... call me only if you want things done right

1 0

Question about link in VC7.1
by Michael Qi 14 Jan '08

14 Jan '08

Hi list users, I am using VC.net 2003 and use boost installer to install boost. I read the getting started guide and when link got an error. I configured VC to Multithreaded and the compilation succeeded, the link error is: LINK : fatal error LNK1104: could not open file "libboost_regex-vc71-mt-sgd-1_34_1.lib" and in boost lib directory the file libboost_regex-vc71-mt-1_34_1.lib existed, not the one with "sgd" Why VC　want sgd? Any suggestion is welcomed:) Regards HeQi

2 2

the review of the switch library ends today, January 13th
by Stjepan Rajko 14 Jan '08

14 Jan '08

The review of the Switch library submitted by Steven Watanabe ends today (Sunday, January 13th). I would like to thank Steven for submitting a very useful library, as well as all those who have submitted reviews and/or contributed to the discussion (especially Tobias Schwinger and Joel de Guzman who have put in quite a bit of effort towards enhancing the design of the library). I will send a more detailed summary of the review as well as a decision in the following days. I currently have only 3 reviews to base a decision on, so any additional votes that anyone would like to contribute in the very near future would be very welcome. Regards, Stjepan

1 0

Re: [Boost-users] Casting this pointer to a number
by sj＠sjcomp.com 13 Jan '08

13 Jan '08

On Sun, 13 Jan 2008 16:04:36 +0100, Zeljko Vrba, zvrba(a)ifi.uio.no wrote: > Why? What is it going to do with the ID? Why not make the ID a > void* pointer? > And what semantics does this "unique identification" have? Once an object is > deleted, another new'd object may get its address; I can hardly qualify that > as "unique ID". I have a set of objects and these objects have corresponding representations in the other part of my program (for debugging purposes [visualization]). Two parts of the program do not know about each other. One part calls a functions f and another part receives the call. I need to know what object initiated this call. It's given that objects are not destroyed, hence this is unique in that case. Making it void* is an option. Though I was looking for a more elegant solution. Thanks for the example. Thanks. -- Regards, Alexander. http://sjcomp.com

1 0

Casting this pointer to a number
by sj＠sjcomp.com 13 Jan '08

13 Jan '08

Hello, I'd like to provide a function with an unique identifier: void f(size_t UniqueId); This function is going to be called from within class member functions like that: class a { a() { f((size_t)this); } }; Right now the old style cast works. The question is how do I make conversion using numeric_cast? If I use: f(boost::numeric_cast<size_t>(this)); I get a compilation error: error C2665: 'ceil' : none of the 3 overloads could convert all the argument types I guess another question is: should I bother replacing this old-style cast, maybe there is a better way to approach this situation in general? Thanks.

4 3

FW: Export control classification number (ECC) for boost
by matthias.jaeschke＠nsn.com 13 Jan '08

13 Jan '08

> Hi, > > We are using boost in one of our products, and are now in the process of collecting the information needed to export it to other countries. > > Can you tell me what the U.S. Export Control Classification Number (ECCN) for boost is, and whether a license exception may be used for it? > > If you don't know the US ECCN, can you tell me whether any US citizens or people living in the U.S.A. have contributed code to boost? > > In addition to the U.S. ECCN, there is also a German "ECCN", which is called the AL Number. Can you tell me what the AL Number is for boost? > > To better understand the meaning of the U.S. ECCN, please check the following webpage: > http://www.bis.doc.gov/Licensing/Do_I_NeedAnECCN.html > > Many thanks, > Matthias Jäschke / Peter Niggemeier > Nokia Siemens Networks > > > Matthias Jäschke > Senior Quality Engineer > > Nokia Siemens Networks Deutschland GmbH > Heltorfer Str. 1 > D-40472 Düsseldorf > Phone: +49-151-55153859 > Fax +49-211-9412-3383 > E-mail: matthias.jaeschke(a)nsn.com > > Sitz der Gesellschaft: Bochum / Registered office: Bochum > Registergericht: Bochum / Commercial registry: Bochum, HRB 11180 > Geschäftsführung / Managing Directors: Dr. Ulrich Halka, Lydia Sommer > _________________________________________________ > Important Note: This e-mail and any attachment are confidential and may contain trade secrets and may well also be legally privileged or otherwise protected from disclosure. If you have received it in error, you are on notice of its status. Please notify us immediately by reply e-mail and then delete this e-mail and any attachment from your system. If you are not the intended recipient please understand that you must not copy this e-mail or any attachment or disclose the contents to any other person. Thank you for your cooperation. > > Wichtiger Hinweis: Dieses E-Mail und etwaige Anlagen können Betriebs- oder Geschäftsgeheimnisse, dem Anwaltsgeheimnis unterliegende oder sonstige vertrauliche Informationen enthalten. Sollten Sie dieses E-Mail irrtümlich erhalten haben, ist Ihnen der Status dieses E-Mails bekannt. Bitte benachrichtigen Sie uns in diesem Fall sofort durch Antwort-Mail und löschen Sie dieses E-Mail nebst etwaigen Anlagen von Ihrem System. Ebenso dürfen Sie dieses E-Mail oder seine Anlagen nicht kopieren oder an Dritte weitergeben. Vielen Dank. > >

2 1

ptime constructor
by Miguel Lopes 13 Jan '08

13 Jan '08

Hi all, I have a small question about ptime class usage. I am currently working on an old project that uses Boost library; unfortunately, when I build and run the project executable some exceptions are thrown. I found out that some parts of the project are trying to create ptime objects like this: *ptime(time_from_string(string(sz)))* That line throws an exception, when sz is empty. So my question is: Is there any version (Boost version) of ptime class that accepts an empty string as argument? The problem is that I need to investigate which version of Boost, is being really used in the project makefile and with all versions of Boost that line throws the exception. On the other hand I have a precompiled binary of the project, and under the same data input conditions, it works perfectly, that is, even with empty dates no exceptions are thrown. Kind Regards, Miguel Lopes

2 1

Re: [Boost-users] Review: Switch library
by legalize+jeeves＠mail.xmission.com 13 Jan '08

13 Jan '08

[Please do not mail me a copy of your followup] boost(a)lists.boost.org spake the secret code <fmblls$ees$1(a)ger.gmane.org> thusly: >I also urge Steven to pursue the dynamic_switch idea I posted >which employs perfect hashing at compile time whereby allowing >equivalent or faster than a switch dispatch at runtime where >the cases are dynamic (instead of compile time constants). I just want to say that I think this approach is so amazingly cool, my socks are not only blown off, but orbiting the planet :-). -- "The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download <http://www.xmission.com/~legalize/book/download/index.html> Legalize Adulthood! <http://blogs.xmission.com/legalize/>

4 4

Re: [Boost-users] [Boost String Algorithms library] ireplace_all bug with character arrays]
by Pavol Droba 13 Jan '08

13 Jan '08

Hi, Thorsten Ottosen wrote: > shunsuke skrev: >> Richard Turrin wrote: >>> Hi, >>> >>> I've encountered a bug with ireplace_all from the Boost String >>> Algorithms library for version 1.35. If I pass a character array for >>> the Format argument, the function ignores the null terminator and >>> instead uses the entire array minus the last character to replace the >>> occurrences of the Search string in the Input parameter. However, if >>> I provide a pointer to a character array, the string replacement is >>> done as expected. >>> >>> When I stepped into the code, I came across the following lines >>> (excerpt from /trunk/boost/range/as_literal.hpp): >>> >>> template< class Char, std::size_t sz > >>> inline iterator_range<const Char*> as_literal( const Char (&arr)[sz] ) >>> { >>> return boost::make_iterator_range( arr, arr + sz - 1 ); >>> } >>> >>> There is no check for a null terminator. Nor did I find one after >>> this function returned. I think the author here assumed that a >>> caller would always pass in a character array of the right size. >> >> Character array seems to have three views. >> >> 1. array: SIZE("ab\0c") == 5; >> 2. literal: SIZE("ab\0c") == 4; >> 3. null-terminated: SIZE("ab\0c") == 2; >> >> Both 2. and 3. is forced into boost::as_array. >> "One name, two facilities" usually makes trouble. >> IMO, `as_c_str` should have been added for 3. > > I agree we could add a new function. Can we come up with a better name > than as_c_str()? > > Or should we simply make as_literal() scan the array? > I think, that as_literal should behave the same way for character arrays and for c-string. Different behaviour is unexpexted here. The only difference that could be beneficial is that for arrays, the scanning for nulls can be bounded to protect agains the buffer overruns. Regards, Pavol.

1 0

/trunk/boost/range/is_literal.hpp: preprocessor bug
by Richard Turrin 13 Jan '08

13 Jan '08

Hi, Sorry for being a nitpicker here: There is a preprocessor bug in /trunk/boost/range/is_literal.hpp in the SVN repository. Line 18 has the following statement: #if BOOST_NO_FUNCTION_TEMPLATE_ORDERING It should really read: #ifdef BOOST_NO_FUNCTION_TEMPLATE_ORDERING This might manifest itself as compile errors in some of the older compilers (Metrowerks Code Warrior 5.3, SunPro 5.0, and Microsoft Visual C++ 7.0). Rich Turrin

2 1

Re: [Boost-users] [boost] Review: Switch library
by Stjepan Rajko 13 Jan '08

13 Jan '08

On Jan 12, 2008 5:22 PM, Joel de Guzman <joel(a)boost-consulting.com> wrote: > > For the record, I am changing my vote to "yes". I'm quite happy > with the response to my concerns. I am very confident Steven > will produce an amazing library from the very constructive > discussions so far. I'm obviously very adamant in my posts, > the reason being that I really need such a library now but I > have certain use-cases that I need to be handled by the library, > *now*, and not later in another lifetime. I can't wait for > another review or another library to come along that's closer > to my needs. I believe the switch_ library can, with additional > thought and design, handle my needs. > Thank you, Joel. Your contribution to this review is greatly appreciated. I do believe that without addressing your concerns the library would not be a true Boost.Switch. Regards, Stjepan

1 0

libXXX
by Lars Schouw 13 Jan '08

13 Jan '08

I am having a problems with the boost libs I have build the names does not start with lib When I build boost using bjam "-sTOOLS=vc9" install I got a bunch of .lib files in c:\boost\lib e.g. boost_thread-vc90-mt-1_35.lib but when I build my library against tghis if fails to link since it needs a file libboost_thread-vc90-mt-1_35.lib What am I doing wrong? I am using boost from subversion, Windows Vista and Visual Studio 2008 Thanks in advance Lars ____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ

3 2

boost.time_series
by Kim Kuen Tang 13 Jan '08

13 Jan '08

Hello everybody, i want to start using the time series library. But unfortunately i've got compiler errors while compiling the time_series\libs\time_series\example\main.cpp file with visual studio compiler 2005. ------ Erstellen gestartet: Projekt: example, Konfiguration: Debug Win32 ------ Kompilieren... main.cpp using native typeof c:\Boost\src\time_series\boost/sequence/size.hpp(26) : error C2143: Syntaxfehler: Es fehlt ';' vor '<' c:\Boost\src\time_series\boost/sequence/size.hpp(32): Siehe Verweis auf die Instanziierung der gerade kompilierten Klassen-template "boost::sequence::impl::size<S,T>". c:\Boost\src\time_series\boost/sequence/size.hpp(26) : error C4430: Fehlender Typspezifizierer - int wird angenommen. Hinweis: "default-int" wird von C++ nicht unterstützt. c:\Boost\src\time_series\boost/sequence/size.hpp(26) : error C2039: 'type': Ist kein Element von '`global namespace'' c:\Boost\src\time_series\boost/sequence/size.hpp(26) : error C2238: Unerwartete(s) Token vor ';' c:\Boost\src\time_series\boost/sequence/size.hpp(28) : error C2143: Syntaxfehler: Es fehlt ';' vor '(' c:\Boost\src\time_series\boost/sequence/size.hpp(28) : error C4430: Fehlender Typspezifizierer - int wird angenommen. Hinweis: "default-int" wird von C++ nicht unterstützt. c:\Boost\src\time_series\boost/sequence/size.hpp(29) : error C4430: Fehlender Typspezifizierer - int wird angenommen. Hinweis: "default-int" wird von C++ nicht unterstützt. Das Buildprotokoll wurde unter "file://c:\Boost\src\time_series\libs\time_series\example\Debug\BuildLog.htm" gespeichert. example - 7 Fehler, 0 Warnung(en) ========== Erstellen: 0 erfolgreich, Fehler bei 1, 0 aktuell, 0 übersprungen ========== The errors might come from clr-syntax in the quellcode since the compiler doesnt support the response file that contains the clr-syntax without the \clr option. Perhaps anybody can give me a hint how to solve this problem?

1 0

[iterator_facade] Help with const iterator for binary file
by nicola 12 Jan '08

12 Jan '08

Hi, I have a class modeling a record-based read-only binary file and I have written a random access iterator based on iterator_facade to iterate over the records. The class looks like this: class my_binary_file { public: typedef std::string key_type; typedef unsigned int value_type; typedef std::pair<key_type, value_type> record_type; private: class my_binary_file_iterator : public boost::iterator_facade< my_binary_file_iterator, my_binary_file::record_type const, boost::random_access_traversal_tag, my_binary_file::record_type&, int> { public: my_binary_file_iterator() : rec_num_(0), ff_ptr_(0) { } explicit my_binary_file_iterator(my_binary_file* ff, unsigned int n) : ff_ptr_(ff), rec_num_(n) { } private: friend class boost::iterator_core_access; unsigned int rec_num_; my_binary_file* ff_ptr_; mutable my_binary_file::record_type record; void increment() { ++rec_num_; } void decrement() { --rec_num_; } void advance(int n) { rec_num_ += n; } int distance_to(const my_binary_file_iterator z) const { return z.rec_num_ - this->rec_num_; } bool equal(my_binary_file_iterator const& other) const { return this->ff_ptr_ == other.ff_ptr_ && this->rec_num_ == other.rec_num_; } const my_binary_file::record_type dereference() const { ff_ptr_->seekg(rec_num_); my_binary_file::key_type key; my_binary_file::value_type val; ff_ptr_->get_record(key, val); record = std::make_pair(key, val); return record; } }; public: typedef my_binary_file_iterator iterator; iterator begin() const { return iterator(this, 0); } iterator end() const { return iterator(this, num_records_); } // Opens a binary file for reading explicit my_binary_file(const std::string& path); ~my_binary_file(); operator void*() const; bool operator!() const; // Reads the record at the current position bool get_record(key_type& k, value_type& v); std::ios::pos_type tellg() const { return fs_.tellg(); } void seekg(unsigned int n) { fs_.seekg(start_record_ + std::ios::off_type(n * record_size_), std::ios::beg); } private: boost::filesystem::path pathname_; mutable boost::filesystem::fstream fs_; std::streampos start_record_; key_type::size_type key_size_; unsigned int record_size_, num_records_; }; Unfortunately, when I try to compile my project, I get the following error: error: invalid conversion from 'const frequency_file* const' to 'frequency_file*' I have tried several variants of my code, but without success. I think I'm missing something pretty obvious in my definition of my_binary_file_iterator, but I can't get out of it. Anyone can help? Regards Nicola

2 4