- Boost - lists.preview.boost.org

[svn]svn upgrade -> gnome keyring problem: SOLVED
by Larry Evans 30 Aug '10

30 Aug '10

When doing `svn commit`, I was asked for a gnome keyring password, but nothing I did worked. I *think* an upgrade of my OS (ubuntu 8.08 -> 10.04) lead to an upgraded subversion and that lead to the problem. Details are reported here: http://ubuntuforums.org/showthread.php?t=1561623 The solution which worked for me is found here: http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2… HTH anybody on this list experiencing similar problems. -Larry

1 0

Re: [boost] [Boost-users] Overloading boost::for_each()
by David Abrahams 30 Aug '10

30 Aug '10

At Mon, 30 Aug 2010 00:43:57 +0100, Mathias Gaunard wrote: > > Of course, for certain data structures, providing a step-generator, as I > call it, can still be too complicated, and they could only have a > 'global' generator, which, in the case or our deque, would be: > > template<typename T> > struct deque_generator > { > typedef T output_type; > > deque_generator(deque& deq_) : deq(deq_) {} > > template<typename Out> > Out operator()(Out out) > { > for(typename deque::const_iterator it = deq.begin(); it != > deq.end(); ++it) > out = copy(*it++, out); > return out; > } > > private: > typedef vector< array<T, whatever> > deque; > deque &deq; > }; > > In the case of a global generator, implementing algorithms such as > std::accumulate should be basically the same thing as the > string_appender example here: > <http://www.boost.org/doc/libs/1_44_0/libs/iterator/doc/function_output_iter…> > In the case of the step one, it's the same except you need to do it in a > loop. [Followup-To set to the developers' list, as this doesn't seem like a boost-users discussioin anymore.] Hi Mathias, Thanks, but you only answered the first part of my question. I don't understand how you'd use such a thing. Thanks again. -- Dave Abrahams BoostPro Computing http://www.boostpro.com

1 0

Attibutes and Qi
by Steffen.Roeber＠hella.com 30 Aug '10

30 Aug '10

Hi, I used the classic spirit in the past. Now I want to migrate to Spirit 2.4 but I don't get the things together.Reading the different docus in the web did not help. What I want to do at first is to parse a simple string into a QString: My pseudo code looks like: QString t; qi::rule<string::iterator, QString()> r1 = (+qi::char_)(qi::_val = qi::_1); qi::rule<string::iterator , void()> r = r1[ref(t) = _1]; std::string temp("Hallo"); phrase_parse(temp.begin(), temp.end(), r, qi::space); But the compiler does no like this. Can anybody help me? Hella Aglaia Mobile Vision GmbH Steffen Roeber Firmware & Tools Treskowstr. 14, D-13089 Berlin Amtsgericht Berlin-Charlottenburg HRB 66976 B Geschäftsführer: Kay Talmi Fon: +49 30 200 04 29? 412 Fax: +49 30 200 04 29? 109 Mail: Steffen.Roeber(a)hella.com URL: www.aglaia-gmbh.de URL: www.mobilevision.de Dieses Dokument ist vertraulich zu behandeln. Die Weitergabe sowie Vervielfältigung, Verwertung und Mitteilung seines Inhalts ist nur mit unserer ausdrücklichen Genehmigung gestattet. Alle Rechte vorbehalten, insbesondere für den Fall der Schutzrechtsanmeldung. This document has to be treated confidentially. Its contents are not to be passed on, duplicated, exploited or disclosed without our express permission. All rights reserved, especially the right to apply for protective rights.

3 4

[Smart Pointers] compilation error with ver 1.44 and VC 9
by Löw, Tobias (Evonik Energy Services GmbH) 29 Aug '10

29 Aug '10

Hi, after switching to version 1.44 my projects using make_shared won't compile anymore. I'm using the VC 9 compiler on a Windows 2003 Server. I'm confused that nobody else seems to have the same problem with make_shared, so here is a small example: /////////////////////////////////////////////////////////////////////////////// #define BOOST_NO_TYPEID #include <boost/smart_ptr.hpp> #include <boost/make_shared.hpp> struct test { test(){} int i; }; int main(int argc, char* argv[]) { boost::shared_ptr<test> spt = boost::make_shared<test>(); return 0; } ///////////////////////////////////////////////////////////////////////////////// this compiles fine with Boost 1.43, but with version 1.44 I get the following error: boost/detail/sp_typeinfo.hpp(77) : error C2440: 'Initialisierung': 'const char *' kann nicht in 'boost::detail::sp_typeinfo' konvertiert werden (in english: 'const char *' cannot be converted to 'boost::detail::sp_typeinfo') In version 1.43 the line in sp_typeinfo.hpp(77) was: template<class T> sp_typeinfo sp_typeid_≤ T >::ti_( sp_typeid_≤ T >::name() ); so, the explicit-marked ctor was called. In version 1.44 it changed to template<class T> sp_typeinfo sp_typeid_≤ T >::ti_ = sp_typeid_≤ T >::name(); and the explicit-marked ctor won't be called anymore. The change message (https://svn.boost.org/trac/boost/changeset/62245/trunk/boost/detail/sp_type…) refers to some fix for Sun C++. IMO the change should better be guarded by some compiler/platform-detection macro. Tobias PS: I already posted this message on 18 Aug but accidentially as a reply to another thread.

2 2

[Potentially OT] String Concatenation Operator
by Dean Michael Berris 29 Aug '10

29 Aug '10

Good day everyone, I am currently taking some time to implement some functionality into cpp-netlib [0] (shameless plug) and somehow I've stumbled into a sort of conundrum. First, some background: I'm trying to abstract away the string building routines of the network library to come up with the most efficient way of doing the following: 1. Efficiently allocate space to contain a string being built from literals and variable length strings. 2. Be able to build/traverse the string lazily (i.e., it doesn't matter that the string is contiguous in memory as in the case of C-strings, or whether they are built/backed by a stream as in Haskell ByteString). 3. As much as possible be "automagically" network-safe (i.e. can be dealt with by Boost.Asio without having to do much acrobatics with it). At the heart of the issue is the semantics of the '+' operator to signify string concatenation. Trying not to sound pedantic about it, the addition operator in traditional mathematical notions is both commutative and associative, while string concatenation is not commutative but right associative. Trying to remember my C++ operator precedence and associativity rules, it looks like operator% and/or operator^ might be good candidates for this, but only in expression templates where you fold from the right. Now I don't want to start beating on the STL's standard string implementation, but I'd like to know if anyone is already working on a string implementation that meets the above requirements? I'd be happy to wait on compile times with Proto, if it means I can save big at runtime. What I wanted to be able to do (and am reproducing at the moment) is a means of doing the following: string_handle f = /* some means of building a string */; string_handle s = str("Literal:") ^ f ^ str("\r\n\r\n"); std::string some_string = string_handle; // convert to string and build lazily If for instance f were also a literal, then s can efficiently already hold the string in some fixed sized byte array whose size is determined at compile time. Somehow the function str() would only be able to take a literal and look something like this: template <size_t N> inline bounded_fragment<N> str(char const s[N]) { return bounded_fragment<N>(s); } The evaluation of the assignment (or copy constructor) of the string_handle will then evaluate the expression template and already know at compile time: A. Whether the string is just a long literal and allocate enough space to effectively hold the whole string at compile time, or at least reserve enough space statically (a boost::array perhaps) so that a simple range copy can be done (and optimized by the compiler as well) B. Whether the string is a list of variable length strings, having a list of handles built C. Whether it is a mix and have all the adjacent literals joined effectively at compile time and those variable sized strings retrieved when required Pointers to ongoing work would be most appreciated -- I'm currently too preoccupied to chase this particular rabbit down the hole (I'm chasing a different rabbit in a different hole) but maybe this is an interesting enough problem for the template metaprogramming guru's to look into? Thanks in advance and I look forward to any thoughts/pointers. -- Dean Michael Berris deanberris.com

6 14

[Castor] FYI : Castor 1.1 & Boost
by Roshan 29 Aug '10

29 Aug '10

A quick update for the many who expressed interest in the Castor library at the "Logic Paradigm for C++" talk at this year's BoostCon and also folks on the dev mailing list when I polled for interest. Castor 1.1 that was recently released and it will form the basis for the version that will be proposed to Boost. http://www.mpprogramming.com/announce.aspx Among other things, version 1.1 enables support for Coroutines and Query Expressions in C++. There are a couple of videos describing 1.1 specific enhancements at http://www.mpprogramming.com/cpp/default.aspx#Videos Boost Porting: The initial Boost related work has begun (thanks to Zach Laine who has done pretty much all of the work so far). Besides incorporating user feedback and changes that make it conformant to Boost guidelines... my intention is to hopefully include a few significant enhancements. Volunteers welcome! Project sources are currently hosted at http://sourceforge.net/projects/castor-logic/ - Roshan Naik

4 8

[python] 32-bits target build errors with MSVC under Windows x64
by KTC 29 Aug '10

29 Aug '10

Hi, Attempts to build 32-bits target libraries/dll of Boost.Python with MSVC running under Windows 7 x64 ends with errors. The 6 *.lib & *.dll of the form boost_python-vc*-mt* are not built. No problems is experienced if MSVC is running under 32-bits version of Windows (XP Pro SP3 & 7 Ultimate tested), or the target is 64-bits libraries even when running under Win7 x64. The below (sample) errors was produced with Windows 7 Ultimate x64, Visual Studio (2008 Pro & 2010 Ultimate tested), and ActiveState ActivePython (2.6 & 2.7 tested). msvc.link.dll x86\boost\bin.v2\libs\python\build\msvc-10.0\debug\threading-multi\boost_python-vc100-mt-gd-1_44.dll Creating library x86\boost\bin.v2\libs\python\build\msvc-10.0\debug\threading-multi\boost_python-vc100-mt-gd-1_44.lib and object x86\boost\bin.v2\libs\python\build\msvc-10.0\debug\threading-multi\boost_python-vc100-mt-gd-1_44.exp function.obj : error LNK2001: unresolved external symbol __imp__PyErr_Format numeric.obj : error LNK2019: unresolved external symbol __imp__PyErr_Format referenced in function "void __cdecl boost::python::numeric::`anonymous namespace'::throw_load_failure(void)" (?throw_load_failure@?A0x9a30ad83@numeric@python@boost@@YAXXZ) from_python.obj : error LNK2001: unresolved external symbol __imp__PyErr_Format registry.obj : error LNK2001: unresolved external symbol __imp__PyErr_Format class.obj : error LNK2001: unresolved external symbol __imp__PyErr_Format numeric.obj : error LNK2001: unresolved external symbol __imp__PyExc_ImportError numeric.obj : error LNK2019: unresolved external symbol __imp__PyErr_Clear referenced in function "bool __cdecl boost::python::numeric::`anonymous namespace'::load(bool)" (?load@?A0x9a30ad83@numeric@python@boost@@YA_N_N@Z) class.obj : error LNK2001: unresolved external symbol __imp__PyErr_Clear <snip> (Full log can be view at <http://pastebin.com/b62UaEJV>.) Any ideas of a workaround or fix? Regards, KTC

1 0

Some modifications to the Boost random library
by Eric Hopper 28 Aug '10

28 Aug '10

I have written a new class for small random integers and made some slight modifications to the mersenne twister generator that allow me to generate random numbers approximately 2-4 times faster than the current small integer distribution. Would there be interest in these modifications? I have made some attempt to make the code conform to boost standards, but in reality the new class won't work on any compiler that doesn't have robust support for static constant integers. Thanks, -- A word is nothing more or less than the series of historical connotations given to it. That's HOW we derive meaning, and to claim that there is an arbitrary meaning of words above and beyond the way people use them is a blatant misunderstanding of the nature of language. -- Anonymous blogger -- Eric Hopper (hopper(a)omnifarious.org http://www.omnifarious.org/~hopper)--

2 1

[fusion] Problems with push_back/push_front/insert into map
by Alexander Fokin 28 Aug '10

28 Aug '10

Consider the following program: #include <iostream> #include <boost/fusion/algorithm.hpp> #include <boost/fusion/container.hpp> #include <boost/fusion/sequence.hpp> int main() { using namespace boost::fusion; map<> m; result_of::push_back<const map<>, pair<int, int> >::type m1 = push_back(m, pair<int, int>(0)); bool b1 = has_key<int>(m1); // b1 == false bool b2 = has_key<int>(as_map(m1)); // b2 == true int sz = size(m1); // sz == 1 return 0; } According to documentation [1], result of push_back is a model of Associative Sequence if its sequence parameter implements the Associative Sequence model. Therefore, I'd expect the variable b1 to be evaluated to true, not false. Is this the intended behavior? I get the same results with push_front and insert. Tested with boost 1.43 and 1.44. [1] http://www.boost.org/doc/libs/1_44_0/libs/fusion/doc/html/fusion/algorithm/… -- Best regards, Alexander Fokin, ru.elric(a)gmail.com.

2 2

Re: [boost] [msm] Async transition
by Christophe Henry 27 Aug '10

27 Aug '10

> Thanks for your answer. > > It was in fact a question from my employer that asked if msm allows to > do the same as the last example of the statechart doc : > http://www.boost.org/doc/libs/1_44_0/libs/statechart/doc/tutorial.html > (at the end of the page). It depends. As the event processing function of msm is reentrant thanks to the message queue, you have no risk in single threaded programs. In multithreaded programs, you will need to protect the access to process_event. > It's not a requirement, just a technical question because from my > understanding of UML, state regions should be managed separately and I > thought maybe they were threaded in some way. We wanted to be sure of > the whole behaviour before starting testing it. What UML writes about regions is that they are "logically" concurrent, meaning (IIUC) that they each get a chance to handle an event. MSM is implemented this way, each region being called in turn (in the order of the initial_state typedef). Of course, doing this concurrently would speed up event processing at the cost of predictability (if regions sent events to each other, you could not know which is processed first). > Anyway I see that I should treat the state machine like a STL > component in regards to thread-safety and asynchronous event > management. Yes, I also tend to see it that way. >As it's not a requirement, it's not a problem for me but I > was asking myself if there would be an interest in having the event > processing being thread-safe, allowing multiple threads to send > events? Maybe like haveing a msm2 like signals2? > I'm not experienced enough to see if it would be a good idea and I > don't need it so it's just a theorical question. As I don't see msm as a library closed for changes, there is no need for a msm2 yet ;-) I'm working on the next version so if there is a need, I will happily implement it. I've been thinking about thread safety for a while but failed to see a huge gain. I could replace: lock() // whatever you need for locking fsm.process_event(event()); unlock(); by: fsm.process_event(); where process_event would lock at the beginning and unlock at the end, but it seems pretty limited. This leaves us with the valid use case of concurrent region processing. I don't see any other yet, but I'd be interested if someone does as it's a subject I'll want to handle of at some point. Regards, Christophe

2 1

[serialization] register_type order dependent?
by Jeff Flinn 27 Aug '10

27 Aug '10

Is it expected that the calls to register_type need to be identical on both the save and load side of a serialization exchange? I thought I read that the registration facility sets up a map. But the following caused a archive_exception. struct C {}; struct B : C {}; struct A : B {}; --- save boost::archive::text_oarchive oa(some_ostream); oa.register_type(static_cast<A*>(0)); oa.register_type(static_cast<B*>(0)); oa.register_type(static_cast<C*>(0)); oa & aC_ptr; --- load boost::archive::text_iarchive ia(some_istream); ia.register_type(static_cast<B*>(0)); ia.register_type(static_cast<A*>(0)); ia.register_type(static_cast<C*>(0)); oa & aC_ptr; Thanks, Jeff

3 3

glog - google logging library
by Neal Becker 27 Aug '10

27 Aug '10

Just noticed this. Interesting design. http://google-glog.googlecode.com/svn/trunk/doc/glog.html

1 0

[python] boost 1.44 using python 3.1.2 build problem
by Christopher Lux 27 Aug '10

27 Aug '10

Hi, i am under the impression boost.python supported python 3 for a while now. But trying to compile it using python 3.1.2 gives me the old errors: .\boost/python/converter/builtin_converters.hpp(138) : error C2039: 'PyInt_FromLong' : is not a member of '`global namespace'' .\boost/python/converter/builtin_converters.hpp(138) : error C3861: 'PyInt_FromLong': identifier not found .\boost/python/converter/builtin_converters.hpp(138) : error C2065: 'PyInt_Type' : undeclared identifier .\boost/python/converter/builtin_converters.hpp(138) : error C2039: 'PyInt_FromLong' : is not a member of '`global namespace'' .\boost/python/converter/builtin_converters.hpp(138) : error C3861: 'PyInt_FromLong': identifier not found .\boost/python/converter/builtin_converters.hpp(138) : error C2065: 'PyInt_Type' : undeclared identifier .\boost/python/converter/builtin_converters.hpp(138) : error C2039: 'PyInt_FromLong' : is not a member of '`global namespace'' .\boost/python/converter/builtin_converters.hpp(138) : error C3861: 'PyInt_FromLong': identifier not found .\boost/python/converter/builtin_converters.hpp(144) : error C2039: 'PyInt_FromLong' : is not a member of '`global namespace'' .\boost/python/converter/builtin_converters.hpp(144) : error C3861: 'PyInt_FromLong': identifier not found .\boost/python/converter/builtin_converters.hpp(144) : error C2065: 'PyInt_Type' : undeclared identifier .\boost/python/converter/builtin_converters.hpp(144) : error C2039: 'PyInt_FromLong' : is not a member of '`global namespace'' .\boost/python/converter/builtin_converters.hpp(144) : error C3861: 'PyInt_FromLong': identifier not found .\boost/python/converter/builtin_converters.hpp(144) : error C2065: 'PyInt_Type' : undeclared identifier .\boost/python/converter/builtin_converters.hpp(144) : error C2039: 'PyInt_FromLong' : is not a member of '`global namespace'' .\boost/python/converter/builtin_converters.hpp(144) : error C3861: 'PyInt_FromLong': identifier not found my user-config.jam: using python : 3.1 : "C:\\Program Files\\python31\\python" : "C:\\Program Files\\python31\\include" : "C:\\Program Files\\python31\\libs" : #condition : #ext suffix ; Regards -chris

5 5

Re: [boost] Generic lazy loader library interest
by John Bellone 27 Aug '10

27 Aug '10

Hey Dave, It is not a code loader (or class loader) in the sense of Java. This is a design pattern which delays execution (allocation) until the object is first needed. Wikipedia would have a much better explanation than I could ( http://en.wikipedia.org/wiki/Lazy_loading) I currently have a example up on my Github repository, but there is still work to be done to make it better so I figured I'd put the feelers out to see if there is interest. I have a post regarding it on my blog (http://thoughtlessbanter.com/) and I'll include a snippet from the example. class Unique{public: Unique() : m_uuid(boost::uuids::random_generator()()) { } Unique(const boost::uuids::uuid& u) : m_uuid(u) { } const boost::uuids::uuid& uuid() { return m_uuid; }private: boost::uuids::uuid m_uuid;}; static void factory(boost::shared_ptr<Unique>& impl){ impl = boost::shared_ptr<Unique>( new Unique(boost::uuids::nil_uuid()) );} int main(int argc, char* argv[]){ thunk::lazy_loader<Unique> loader(&factory); const boost::uuids::uuid& u = loader->uuid(); std::cout<<"uuid: "<<boost::lexical_cast<std::string>(u)<<std::endl; return 0;} Thanks, jb

1 0

[Filesystem] problems with g++ -std=c++0x
by Roland Bock 26 Aug '10

26 Aug '10

Hi, getting my feet wet with variadic templates, I switched on c++0x support in gcc. Unfortunately, I am experiencing a linker error for the following minimal program: ------------------ #define BOOST_FILESYSTEM_VERSION 3 #define BOOST_FILESYSTEM_NO_DEPRECATED #include <boost/filesystem.hpp> int main() { boost::filesystem::copy_file("a", "b"); } ------------------ rbock@rbock:~/temp/test$ g++ File.cpp -std=c++0x -I boost/1.44/include -L boost/1.44/lib -l boost_filesystem -l boost_system /tmp/ccwkcQpq.o: In function `boost::filesystem3::copy_file(boost::filesystem3::path const&, boost::filesystem3::path const&)': File.cpp:(.text._ZN5boost11filesystem39copy_fileERKNS0_4pathES3_[boost::filesystem3::copy_file(boost::filesystem3::path const&, boost::filesystem3::path const&)]+0x2a): undefined reference to `boost::filesystem3::detail::copy_file(boost::filesystem3::path const&, boost::filesystem3::path const&, boost::filesystem3::copy_option, boost::system::error_code*)' collect2: ld returned 1 exit status Experienced on Ubuntu-10.4, 64bit, gcc (Ubuntu 4.4.3-4ubuntu5) 4.4.3 Other boost libraries seem to work fine, other functions within Boost.Filesystem work fine, too. When I rebuild boost with -std=c++0x, then the linking problem is gone, but I experience crashes in the boost::thread constructor :-( Any ideas? Thanks and regards, Roland

4 8

Re: [boost] [msm] Async transition
by Christophe Henry 26 Aug '10

26 Aug '10

Hi, > from what I understand of Meta-State-Machine library documentation, > the state transitions are performed immediately when events are > processed. - right? Right. > So my (maybe very dumb) question is : is there cases where the > state-machine will perform state transitions in an asynchronous way? No, transitions are performed when an event is fired. What are you trying to achieve? Regards, Christophe

2 1

ptr_container] 1.44 compile error in serialization
by Jan Boehme 26 Aug '10

26 Aug '10

Hi, a compile error (gcc used) occurs if a ptr_container should be serialized: boost/ptr_container/detail/serialize_reversible_cont.hpp:28: error: ‘make_nvp’ is not a member of ‘boost::serialization’ A patch to fix this is attached. Bye, Jan.

2 2

[msm] Async transition
by Klaim 26 Aug '10

26 Aug '10

Hi, from what I understand of Meta-State-Machine library documentation, the state transitions are performed immediately when events are processed. - right? So my (maybe very dumb) question is : is there cases where the state-machine will perform state transitions in an asynchronous way? Thanks, Joël Lamotte

1 0

[algorithm][string] gcc unused parameter warning
by Jürgen Hunold 25 Aug '10

25 Aug '10

Hi, compiling code using Boost.Unit results in an unused parameter in algorithm/string/detail/find_format_store.hp with gcc and -Wall -Wextra enabled. Okay to commit the attached patch ? Yours, Jürgen -- * Dipl.-Math. Jürgen Hunold ! Ingenieurgesellschaft für * voice: ++49 511 262926 57 ! Verkehrs- und Eisenbahnwesen mbH * fax : ++49 511 262926 99 ! Lister Straße 15 * juergen.hunold(a)ivembh.de ! www.ivembh.de * * Geschäftsführer: ! Sitz des Unternehmens: Hannover * Prof. Dr.-Ing. Thomas Siefer ! Amtsgericht Hannover, HRB 56965 * PD Dr.-Ing. Alfons Radtke !

2 2

[format] old-style cast warning
by Jürgen Hunold 25 Aug '10

25 Aug '10

Hi, I'm using Boost.Format with gcc "-Wold-style-cast" enabled. This issued a warning in format/feed_args.hpp. Okay to commit the attached patch ? Yours, Jürgen -- * Dipl.-Math. Jürgen Hunold ! Ingenieurgesellschaft für * voice: ++49 511 262926 57 ! Verkehrs- und Eisenbahnwesen mbH * fax : ++49 511 262926 99 ! Lister Straße 15 * juergen.hunold(a)ivembh.de ! www.ivembh.de * * Geschäftsführer: ! Sitz des Unternehmens: Hannover * Prof. Dr.-Ing. Thomas Siefer ! Amtsgericht Hannover, HRB 56965 * PD Dr.-Ing. Alfons Radtke !

1 0

Re: [boost] [1.44] [filesystem] operator +
by Jochen Wilhelmy 25 Aug '10

25 Aug '10

> > Sometimes I have file formats that have two parts, e.g. a description xml > > file > > and a data file. then I'd like to do name + ".xml" and name + ".dat" if name > > is > > a fs::path >path p1 = "foo/bar.xml"; >path p2 = path(p1).replace_extension(".dat"); path p = "foo/bar"; path p1 = p + ".xml";-) path p2 = path(p1).replace_extension(".dat");

2 1

[1.44] [filesystem] operator +
by Jochen Wilhelmy 25 Aug '10

25 Aug '10

> Note that Boost.Filesystem contains functions to retrieve and modify >file extensions. >In my opinion, introducing such a free + operator would be quite bad, as >it would encourage use of it to glue on path segments in ways that may >violate the format of paths for a platform, as in your example of an >unconditional +"/bar", which would be horribly wrong for any platform >that didn't use / as separator. I know that I can exchange the current extension, but how can I add one to a path that soes not have one? The current filename may already contain dots therefore the addition of an extension should not check if there is already one. (e.g. "foo/bar.xy" + ".zw" -> "foo/bar.xy.zw") I don't see any technical problem with + "/bar" since "/bar" is the platform independent notation and should therefore work on any platform. so far it is also allowed to do fs::path("foo/bar") where '/' is also the platform independent separator. therefore it should be equivalent to fs::path("foo") + "/bar". but it would be ok to prevent this e.g. by throwing an exception. something like path.add_extension(".bar") should be ok too. -Jochen

3 2

Boost Test Policy
by Edward Diener 25 Aug '10

25 Aug '10

I was looking at the Boost web page describing the Boost test policies, at http://www.boost.org/development/test.html. I was not sure what I needed to use to design tests for possible Boost software. I noticed that it was not required to use Boost Test in order to do so, but that there was an "Optional (but highly recommended)" section for using Boost Test. But neither of the links there are valid any longer, and while Boost Test still has a Unit Test Framework I did not find any Test Tools section for simple test programs, although perhaps the execution monitors or minimal test in Boost Test was originally meant. Anyway the page needs to be updated in regard to Boost Test links. I also found the lightweigt_test.hpp in Boost detail, so I was wondering whether or not that is now considered a viable enough choice for designing Boost component's tests.

6 5

Compilation error's while building boost 1_44_0 on Solaris (Sun Studio 10)
by Nakul Virmani 25 Aug '10

25 Aug '10

Hi All, I am trying to build boost version 1_44_0 on Solaris.The Solaris box has Sun Studio 10 installed. The compiler details are bash-2.05$ CC -V CC: Sun C++ 5.7 2005/01/07 I am using the following command to build boost libraries *bash-2.05$ bjam --build-dir=/export/home/dfdev/Boost_1_44_0/boost_1_44_0/tmp/build-boost toolset=sun stage* But i get the below compilation errors, not even one of the projects build sun.compile.c++ /export/home/dfdev/Boost_1_44_0/boost_1_44_0/tmp/build-boost/boo st/bin.v2/libs/iostreams/build/sun/release/stdlib-sun-stlport/threading-multi/fi le_descriptor.o Notice: The Early Access serial number will expire in -7 days. In order to purchase the product, visit http://www.sun.com/forte/buy.html or contact your Forte Tools reseller. "libs/iostreams/src/file_descriptor.cpp", line 352: Error: Could not find boost: :shared_ptr<boost::iostreams::detail::file_descriptor_impl>::shared_ptr(boost::i ostreams::detail::file_descriptor_impl*) to initialize pimpl_. "libs/iostreams/src/file_descriptor.cpp", line 355: Error: Could not find boost: :shared_ptr<boost::iostreams::detail::file_descriptor_impl>::shared_ptr(boost::i ostreams::detail::file_descriptor_impl*) to initialize pimpl_. "libs/iostreams/src/file_descriptor.cpp", line 360: Error: Could not find boost: :shared_ptr<boost::iostreams::detail::file_descriptor_impl>::shared_ptr(boost::i ostreams::detail::file_descriptor_impl*) to initialize pimpl_. "libs/iostreams/src/file_descriptor.cpp", line 380: Error: Could not find boost: :shared_ptr<boost::iostreams::detail::file_descriptor_impl>::shared_ptr(boost::i ostreams::detail::file_descriptor_impl*) to initialize pimpl_. "libs/iostreams/src/file_descriptor.cpp", line 385: Error: Could not find boost: :shared_ptr<boost::iostreams::detail::file_descriptor_impl>::shared_ptr(boost::i ostreams::detail::file_descriptor_impl*) to initialize pimpl_. "libs/iostreams/src/file_descriptor.cpp", line 393: Error: Using static_cast to convert from boost::iostreams::file_descriptor_flags to boost::iostreams::detail ::file_descriptor_impl::flags not allowed. 6 Error(s) detected. "CC" -library=stlport4 -xO4 -mt -erroff=%none -KPIC -DBOOST_ALL_NO_LIB=1 -DB OOST_IOSTREAMS_DYN_LINK=1 -DBOOST_IOSTREAMS_USE_DEPRECATED -DNDEBUG -I"." -c -o "/export/home/dfdev/Boost_1_44_0/boost_1_44_0/tmp/build-boost/boost/bin.v2/libs/ iostreams/build/sun/release/stdlib-sun-stlport/threading-multi/file_descriptor.o " "libs/iostreams/src/file_descriptor.cpp" ...failed sun.compile.c++ /export/home/dfdev/Boost_1_44_0/boost_1_44_0/tmp/build -boost/boost/bin.v2/libs/iostreams/build/sun/release/stdlib-sun-stlport/threadin g-multi/file_descriptor.o... sun.compile.c++ /export/home/dfdev/Boost_1_44_0/boost_1_44_0/tmp/build-boost/boo st/bin.v2/libs/iostreams/build/sun/release/stdlib-sun-stlport/threading-multi/ma pped_file.o Notice: The Early Access serial number will expire in -7 days. In order to purchase the product, visit http://www.sun.com/forte/buy.html or contact your Forte Tools reseller. "./boost/type_traits/is_array.hpp", line 41: Error: Multiple declaration for boo st::is_array. "./boost/type_traits/is_array.hpp", line 42: Error: Multiple declaration for boo st::is_array. "./boost/type_traits/is_array.hpp", line 43: Error: Multiple declaration for boo st::is_array. "./boost/type_traits/is_array.hpp", line 44: Error: Multiple declaration for boo st::is_array. "./boost/mpl/aux_/preprocessed/plain/full_lambda.hpp", line 95: Error: The type of specialized argument boost::mpl::aux::F<boost::mpl::aux::P1> is dependent on another argument. "./boost/mpl/aux_/preprocessed/plain/full_lambda.hpp", line 95: Error: Partial s pecialization parameter Tag is not used in the arguments. "./boost/mpl/aux_/preprocessed/plain/full_lambda.hpp", line 112: Error: Partial specialization parameter F is not used in the arguments. "./boost/mpl/aux_/preprocessed/plain/full_lambda.hpp", line 172: Error: The type of specialized argument boost::mpl::aux::F<boost::mpl::aux::P1, boost::mpl::aux ::P2> is dependent on another argument. "./boost/mpl/aux_/preprocessed/plain/full_lambda.hpp", line 172: Error: Partial specialization parameter Tag is not used in the arguments. "./boost/mpl/aux_/preprocessed/plain/full_lambda.hpp", line 189: Error: Partial specialization parameter F is not used in the arguments. "./boost/mpl/aux_/preprocessed/plain/full_lambda.hpp", line 254: Error: The type of specialized argument boost::mpl::aux::F<boost::mpl::aux::P1, boost::mpl::aux ::P2, boost::mpl::aux::P3> is dependent on another argument. "./boost/mpl/aux_/preprocessed/plain/full_lambda.hpp", line 254: Error: Partial specialization parameter Tag is not used in the arguments. "./boost/mpl/aux_/preprocessed/plain/full_lambda.hpp", line 271: Error: Partial specialization parameter F is not used in the arguments. "./boost/mpl/aux_/preprocessed/plain/full_lambda.hpp", line 339: Error: The type of specialized argument boost::mpl::aux::F<boost::mpl::aux::P1, boost::mpl::aux ::P2, boost::mpl::aux::P3, boost::mpl::aux::P4> is dependent on another argument . "./boost/mpl/aux_/preprocessed/plain/full_lambda.hpp", line 339: Error: Partial specialization parameter Tag is not used in the arguments. "./boost/mpl/aux_/preprocessed/plain/full_lambda.hpp", line 357: Error: Partial specialization parameter F is not used in the arguments. "./boost/mpl/aux_/preprocessed/plain/full_lambda.hpp", line 427: Error: The type of specialized argument boost::mpl::aux::F<boost::mpl::aux::P1, boost::mpl::aux ::P2, boost::mpl::aux::P3, boost::mpl::aux::P4, boost::mpl::aux::P5> is dependen t on another argument. "./boost/mpl/aux_/preprocessed/plain/full_lambda.hpp", line 427: Error: Partial specialization parameter Tag is not used in the arguments. "./boost/mpl/aux_/preprocessed/plain/full_lambda.hpp", line 445: Error: Partial specialization parameter F is not used in the arguments. "libs/iostreams/src/mapped_file.cpp", line 441: Error: Could not find boost::sha red_ptr<boost::iostreams::detail::mapped_file_impl>::shared_ptr(boost::iostreams ::detail::mapped_file_impl*) to initialize pimpl_. 20 Error(s) detected. Am i missing something? Do i need to do any configuration changes? I will appreciate your input's. Regards, Nakul

1 0

Generic lazy loader library interest
by John Bellone 24 Aug '10

24 Aug '10

Hey guys, Would there be any interest in a generic lazy loader implementation? Thanks, jb

2 1