- Boost-users - lists.boost.org

Applying Boost license to non boost projects
by Roshan Naik 16 Jan '08

16 Jan '08

I am interested in adopting the Boost Software license for an open source C++ library (Castor: http://www.mpprogramming.com/2.html) The Boost FAQ describes how to apply the license to Boost header files. It basically states that the foll. lines should be included: // Copyright Joe Coder 2004 - 2006. // 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) - Does this same guideline apply to non boost projects ? The need for stating Boost.org there might confuse some users of non boost prj to think that the library is supplied by Boost. - Do all header files in my prj (which is a pure header library) need to include this text at the top/somewhere in order to adopt the license. -Roshan

2 1

[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