July 2013 - Boost-users - lists.boost.org

Is MultiIndex right for me?
by Sensei 23 Jul '13

23 Jul '13

Hello everyone, I was playing with std::unordered_multimap trying to achieve the following. I need to store values in no particular order. I need to find, however, all values (let's assume they are integers) that satisfy some given criteria that is NOT the simple equality. For example, I'd like to store integers, and find all integers that are equal modulo p, for instance given two integers u, v, I may write the equality predicate as return (u % p) == (v % p). This requirement might change (at compile time, of course), for example, in another map I'd like to find all integers that have a particular bit set to 1. I tried, as I said, with std::unordered_multimap, but I was told (correctly, AFAIK) that the ISO requires that items matching values MUST match also with hash values. Of course, in my case matching integers do not possess matching hashes. I was wondering if boost might be handy here. Thanks & Cheers!

2 3

[multiprecision] Compiler Warnings
by Michael Olea 23 Jul '13

23 Jul '13

Hi. I'm getting compiler warnings for narrowing conversions when I write a cpp_int to a stream. This is with boost 1_53_0 on OS X 10.8.3 using Xcode version 4.6.2 with clang: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang --version Apple LLVM version 4.2 (clang-425.0.28) (based on LLVM 3.2svn) Target: x86_64-apple-darwin12.3.0 Thread model: posix Here's a short example causing the problem: // // main.cpp // #include <boost/multiprecision/cpp_int.hpp> #include <iostream> int main(int argc, const char * argv[]) { using namespace boost::multiprecision; cpp_int u = 1; for(unsigned i = 1; i <= 100; ++i) u *= i; std::cout << "100! using arbitrary precision cpp_int:\n"; std::cout << u << std::endl; // prints 100! return 0; } The short compiler messages: In file included from /Users/olea/code/mjaal/learn/boost/build/xcode/mp_warner/mp_warner/main.cpp:5: /usr/local/include/boost/multiprecision/cpp_int.hpp:1573:34: warning: implicit conversion loses integer precision: 'unsigned long' to 'int' [-Wshorten-64-to-32] int pos = result.size() - 1; ~~~ ~~~~~~~~~~~~~~^~~ /usr/local/include/boost/multiprecision/cpp_int.hpp:1653:14: note: in instantiation of member function 'boost::multiprecision::backends::cpp_int_backend<0, 0, 1, 0, std::__1::allocator<unsigned int> >::do_get_string' requested here return do_get_string(f, trivial_tag()); ^ /usr/local/include/boost/multiprecision/number.hpp:576:24: note: in instantiation of member function 'boost::multiprecision::backends::cpp_int_backend<0, 0, 1, 0, std::__1::allocator<unsigned int> >::str' requested here return m_backend.str(digits, f); ^ /usr/local/include/boost/multiprecision/number.hpp:1650:22: note: in instantiation of member function 'boost::multiprecision::number<boost::multiprecision::backends::cpp_int_backend<0, 0, 1, 0, std::__1::allocator<unsigned int> >, 1>::str' requested here std::string s = r.str(d, os.flags()); ^ /Users/olea/code/mjaal/learn/boost/build/xcode/mp_warner/mp_warner/main.cpp:16:12: note: in instantiation of function template specialization 'boost::multiprecision::operator<<<boost::multiprecision::backends::cpp_int_backend<0, 0, 1, 0, std::__1::allocator<unsigned int> >, 1>' requested here std::cout << u << std::endl; // prints 100! ^ In file included from /Users/olea/code/mjaal/learn/boost/build/xcode/mp_warner/mp_warner/main.cpp:5: /usr/local/include/boost/multiprecision/cpp_int.hpp:1606:34: warning: implicit conversion loses integer precision: 'unsigned long' to 'int' [-Wshorten-64-to-32] int pos = result.size() - 1; ~~~ ~~~~~~~~~~~~~~^~~ /usr/local/include/boost/multiprecision/cpp_int.hpp:1639:23: warning: implicit conversion loses integer precision: 'size_type' (aka 'unsigned long') to 'unsigned int' [-Wshorten-64-to-32] unsigned n = result.find_first_not_of('0'); ~ ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3 warnings generated. The compile command: CompileC /Users/olea/Library/Developer/Xcode/DerivedData/mp_warner-fvjhjlwtkmsewtfsdqsuzhczhlxd/Build/Intermediates/mp_warner.build/Debug/mp_warner.build/Objects-normal/x86_64/main.o mp_warner/main.cpp normal x86_64 c++ com.apple.compilers.llvm.clang.1_0.compiler cd /Users/olea/code/mjaal/learn/boost/build/xcode/mp_warner setenv LANG en_US.US-ASCII /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -x c++ -arch x86_64 -fmessage-length=0 -std=gnu++11 -stdlib=libc++ -Wno-trigraphs -fpascal-strings -O0 -Wno-missing-field-initializers -Wno-missing-prototypes -Wreturn-type -Wno-non-virtual-dtor -Wno-overloaded-virtual -Wno-exit-time-destructors -Wformat -Wno-missing-braces -Wparentheses -Wswitch -Wno-unused-function -Wno-unused-label -Wno-unused-parameter -Wunused-variable -Wunused-value -Wempty-body -Wuninitialized -Wno-unknown-pragmas -Wno-shadow -Wno-four-char-constants -Wno-conversion -Wconstant-conversion -Wint-conversion -Wenum-conversion -Wshorten-64-to-32 -Wno-newline-eof -Wno-c++11-extensions -DDEBUG=1 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.8.sdk -fasm-blocks -fstrict-aliasing -Wdeprecated-declarations -Winvalid-offsetof -mmacosx-version-min=10.8 -g -fvisibility-inlines-hidden -Wno-sign-conversion -iquote /Users/olea/Library/Developer/Xcode/DerivedData/mp_warner-fvjhjlwtkmsewtfsdqsuzhczhlxd/Build/Intermediates/mp_warner.build/Debug/mp_warner.build/mp_warner-generated-files.hmap -I/Users/olea/Library/Developer/Xcode/DerivedData/mp_warner-fvjhjlwtkmsewtfsdqsuzhczhlxd/Build/Intermediates/mp_warner.build/Debug/mp_warner.build/mp_warner-own-target-headers.hmap -I/Users/olea/Library/Developer/Xcode/DerivedData/mp_warner-fvjhjlwtkmsewtfsdqsuzhczhlxd/Build/Intermediates/mp_warner.build/Debug/mp_warner.build/mp_warner-all-target-headers.hmap -iquote /Users/olea/Library/Developer/Xcode/DerivedData/mp_warner-fvjhjlwtkmsewtfsdqsuzhczhlxd/Build/Intermediates/mp_warner.build/Debug/mp_warner.build/mp_warner-project-headers.hmap -I/Users/olea/Library/Developer/Xcode/DerivedData/mp_warner-fvjhjlwtkmsewtfsdqsuzhczhlxd/Build/Products/Debug/include -I/usr/local/include -I/Users/olea/Library/Developer/Xcode/DerivedData/mp_warner-fvjhjlwtkmsewtfsdqsuzhczhlxd/Build/Intermediates/mp_warner.build/Debug/mp_warner.build/DerivedSources/x86_64 -I/Users/olea/Library/Developer/Xcode/DerivedData/mp_warner-fvjhjlwtkmsewtfsdqsuzhczhlxd/Build/Intermediates/mp_warner.build/Debug/mp_warner.build/DerivedSources -F/Users/olea/Library/Developer/Xcode/DerivedData/mp_warner-fvjhjlwtkmsewtfsdqsuzhczhlxd/Build/Products/Debug -MMD -MT dependencies -MF /Users/olea/Library/Developer/Xcode/DerivedData/mp_warner-fvjhjlwtkmsewtfsdqsuzhczhlxd/Build/Intermediates/mp_warner.build/Debug/mp_warner.build/Objects-normal/x86_64/main.d --serialize-diagnostics /Users/olea/Library/Developer/Xcode/DerivedData/mp_warner-fvjhjlwtkmsewtfsdqsuzhczhlxd/Build/Intermediates/mp_warner.build/Debug/mp_warner.build/Objects-normal/x86_64/main.dia -c /Users/olea/code/mjaal/learn/boost/build/xcode/mp_warner/mp_warner/main.cpp -o /Users/olea/Library/Developer/Xcode/DerivedData/mp_warner-fvjhjlwtkmsewtfsdqsuzhczhlxd/Build/Intermediates/mp_warner.build/Debug/mp_warner.build/Objects-normal/x86_64/main.o

2 3

Re: [Boost-users] [graph] in-depth parsing and modifications of the graph
by Orianne Siret 23 Jul '13

23 Jul '13

Thanks a lot, it worked ! Le 12/07/2013 20:54, boost-users-request(a)lists.boost.org a écrit : > Send Boost-users mailing list submissions to > boost-users(a)lists.boost.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.boost.org/mailman/listinfo.cgi/boost-users > or, via email, send a message with subject or body 'help' to > boost-users-request(a)lists.boost.org > > You can reach the person managing the list at > boost-users-owner(a)lists.boost.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Boost-users digest..." > > > Today's Topics: > > 1. [msm] access to root fsm (Alexander Mingalev) > 2. Re: issues compiling Boost 1.54 thread on AIX5.2 > (Vicente J. Botet Escriba) > 3. [boost format] Not getting expected errors (Rob Conde) > 4. Re: [graph] in-depth parsing and modifications of the graph > (Jeremiah Willcock) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 12 Jul 2013 20:29:36 +0400 > From: Alexander Mingalev <infest21h(a)gmail.com> > To: boost-users(a)lists.boost.org > Subject: [Boost-users] [msm] access to root fsm > Message-ID: <51E02EF0.4010202(a)gmail.com> > Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" > > I have main fsm with two sub-levels. > The problem is, the sub-fsms need data which is held in root fsm, like: > > struct SomeAction > { > template <typename EVT, typename FSM, typename > SourceState, typename TargetState> > void operator()(EVT&, FSM& fsm, SourceState&, > TargetState&) const > { > // ... > } > }; > > Instance of fsm here might be root fsm as well as sub-fsm. > I see two possible solutions: > > 1. use sm_ptr policy and store parent pointer in each sub-fsm > In this case access might look like this: > > fsm.parent_->data; (access from 1-level fsm) > fsm.parent_->parent_->data; (access from 2-level fsm) > > doesn't look so nice, besides, documentation states that using sm_ptr is > deprecated. > > 2. recursively traverse all states, detect fsm's and store root pointer > > typedef RootFSM::stt stt; > typedef boost::msm::back::generate_state_set<stt>::type all_states; > > boost::mpl::for_each<all_states, boost::msm::wrap<mpl::placeholders::_1> > > (find_sub_fsm<stt>()); > > template <typename stt> > struct find_sub_fsm > { > template <class StateType> > void operator()(boost::msm::wrap<StateType>& state) const > { > // ??? > // state.root_ = &g_root; > // do the recurs > } > }; > > How to detect that StateType is sub-fsm? > > 3. Maybe, there is a easier way to communicate between sub-fsm's? > >

1 0

Announcing boost dependency analyzer
by Jens Weller 23 Jul '13

23 Jul '13

Hello to the boost community, I'd like to announce the release of a small tool, that allows you analyze the dependencies in boost. It is based on bcp, requirement is that you have bcp build and well a version of boost to analyze installed. Simply select the boost directory (the tool also might find BOOST_ROOT) and the location of bcp, and the tool will start. This will take a little time, depending on your machine, on my multicore intel ist 90 seconds - 2 minute. The tool will store this information into a database, so that with the next start, this will be a lot shorter. The tool allows to analyze the dependcies of a single boost library, but also of all of boost. Its build with Qt for the UI and processing part, and uses boost graph for the layout. Full information + download you'll find at my blogpost: http://www.meetingcpp.com/index.php/br/items/boost-dependency-analyzer.html Current Issues: What libraries might be missing? I'm reading the libs from maintainers.txt, which isn't all the boost libs. For example, lexical_cast is missing, and function_types is twice in there. (C&P error or missing library?) So far Windows is supported, linux support planned and improving, currently ownly the (beta) binaries for linux available. kind regards, Jens Weller

1 0

[icl] joining two simple intervals
by Olaf Krzikalla 23 Jul '13

23 Jul '13

Hi, I just tried and failed to find a simple way to compute the upper and lower bounds of some interval_sets: typedef boost::icl::interval_set<int> list_type; typedef list_type::value_type interval; void add_region(interval& av, const list_type& reg) { av += reg; // didn't work if (!reg.empty()) { // didn't work either: av += tAddressInterval( reg.begin()->lower(), (--reg.end())->upper())); // this one works: av = tAddressInterval(std::min(av.lower(), reg.begin()->lower()), std::max(av.lower(), (--reg.end())->upper())); } } My workaround doesn't even respect the boundary types. I wonder if there is not a simpler way for such a fundamental tasks. Best regards Olaf

2 2

[msm] access to root fsm
by Alexander Mingalev 23 Jul '13

23 Jul '13

I have main fsm with two sub-levels. The problem is, the sub-fsms need data which is held in root fsm, like: struct SomeAction { template <typename EVT, typename FSM, typename SourceState, typename TargetState> void operator()(EVT&, FSM& fsm, SourceState&, TargetState&) const { // ... } }; Instance of fsm here might be root fsm as well as sub-fsm. I see two possible solutions: 1. use sm_ptr policy and store parent pointer in each sub-fsm In this case access might look like this: fsm.parent_->data; (access from 1-level fsm) fsm.parent_->parent_->data; (access from 2-level fsm) doesn't look so nice, besides, documentation states that using sm_ptr is deprecated. 2. recursively traverse all states, detect fsm's and store root pointer typedef RootFSM::stt stt; typedef boost::msm::back::generate_state_set<stt>::type all_states; boost::mpl::for_each<all_states, boost::msm::wrap<mpl::placeholders::_1> > (find_sub_fsm<stt>()); template <typename stt> struct find_sub_fsm { template <class StateType> void operator()(boost::msm::wrap<StateType>& state) const { // ??? // state.root_ = &g_root; // do the recurs } }; How to detect that StateType is sub-fsm? 3. Maybe, there is a easier way to communicate between sub-fsm's?

3 3

packaged_task returning boost::any with BOOST_THREAD_VERSION>=3
by Nicolas P 22 Jul '13

22 Jul '13

Hello, I'm trying to enable boost (1.54) thread version >=3 with my code and i run into a package_task compilation issue I reduced my issue to a minimal test program that compiles fine on windows 7, but fails to compile on osx and linux (compilers info bellow) with BOOST_THREAD_VERSION = 3 or 4 (fine with boost thread version 2) test succeded on - Windows 7 with Visual 2010 Express sp1 with SDK 7.1 ok test failed on - Mac os x 10.6 Xcode 4.2 : gcc 4.2.1 and clang 3.0 - Mac os x 10.7 Xcode 4.4 : gcc and clang 4.0 - Ubuntu 13.04 gcc 4.7.4 The minimal test program : #define BOOST_THREAD_PROVIDES_SIGNATURE_PACKAGED_TASK #define BOOST_THREAD_VERSION 4 #include <boost/any.hpp> #include <boost/thread.hpp> #include <boost/function.hpp> boost::any process() { return 1; } int main() { boost::function< boost::any () > f = &process ; //boost::packaged_task< boost::any () > task(&process); // Works fine boost::packaged_task< boost::any () > task(f); return 0; } // Replacing 'boost::any' with 'int' make it compile. Error log with clang on os x 10.6 : In file included from /tmp/packaged_task_test/main.cpp:5: In file included from boost/thread.hpp:24: boost/thread/future.hpp:2298:27: error: no matching member function for call to 'set_value_at_thread_exit' this->set_value_at_thread_exit(f()); ~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~ boost/thread/future.hpp:2857:33: note: in instantiation of member function 'boost::detail::task_object<boost::function<boost::any ()>, boost::any ()>::do_apply' requested here task = task_ptr(new task_object_type(f)); ^ /tmp/packaged_task_test/main.cpp:17:43: note: in instantiation of function template specialization 'boost::packaged_task<boost::any ()>::packaged_task<boost::function<boost::any ()> >' requested here boost::packaged_task< boost::any () > task(f); ^ boost/thread/future.hpp:673:18: note: candidate function not viable: no known conversion from 'result_type' (aka 'boost::any') to 'source_reference_type' (aka 'boost::any &') for 1st argument void set_value_at_thread_exit(source_reference_type result_) ^ boost/thread/future.hpp:687:18: note: candidate function not viable: no known conversion from 'result_type' (aka 'boost::any') to 'rvalue_source_type' (aka 'rv<boost::any> &') for 1st argument void set_value_at_thread_exit(rvalue_source_type result_) ^ boost/thread/future.hpp:2329:25: error: no matching member function for call to 'mark_finished_with_result' this->mark_finished_with_result(f()); ~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~ boost/thread/future.hpp:2857:33: note: in instantiation of member function 'boost::detail::task_object<boost::function<boost::any ()>, boost::any ()>::do_run' requested here task = task_ptr(new task_object_type(f)); ^ /tmp/packaged_task_test/main.cpp:17:43: note: in instantiation of function template specialization 'boost::packaged_task<boost::any ()>::packaged_task<boost::function<boost::any ()> >' requested here boost::packaged_task< boost::any () > task(f); ^ boost/thread/future.hpp:627:18: note: candidate function not viable: no known conversion from 'result_type' (aka 'boost::any') to 'source_reference_type' (aka 'boost::any &') for 1st argument void mark_finished_with_result(source_reference_type result_) ^ boost/thread/future.hpp:633:18: note: candidate function not viable: no known conversion from 'result_type' (aka 'boost::any') to 'rvalue_source_type' (aka 'rv<boost::any> &') for 1st argument void mark_finished_with_result(rvalue_source_type result_) ^ 2 errors generated. Am i missing something ? Regards, Nicolas

1 0

[property_tree] Parsing vectors of objects
by Michael Powell 21 Jul '13

21 Jul '13

Hello, I want to parse to and from Xml (or possibly Json) using the property tree. I've got a simple POCO parsing, but now I need to include vectors of objects. Furthermore, I understand the property tree paths are pretty cumbersome. Not so much through a thin vernier, template function, something like that, but anywho... Here's the desired output I want in Xml, something like this: <output> <apples> <apple grower="red" /> <apple grower="green" /> <apple grower="golden" /> </apples> <oranges> <orange freshness="picked" /> <orange freshness="market" /> <orange freshness="store" /> </oranges> <items> <item name="" id="">1234</item> <item name="" id="">1234</item> <item name="" id="">1234</item> </items> </output> I understand the tree path might look something like this "output.apples.apple.<xmlattr>.grower", but what about the vector? Probably want to be trimming white spaces, indenting, as well. Regards, Michael Powell

2 2

Boost integration in Visual Studio 2010
by Georg.Kellerer＠lfu.bayern.de 20 Jul '13

20 Jul '13

Hi, we're using boost inour projects and all works fine. Our projects are standing under version control in a subversion repository. Our problem is that every developper had installed boost in a diferent place. Is their a way to get the reference to boost in a user speciffic configuration place? At the moment we have a fix path c:\dev\boost... but that does not fit for every developpers machine. Thanks for help, Georg ---------------------------------------------- Bayerisches Landesamt für Umwelt Referat Z6: IuK-Steuerung, Aufbau von Informationssystemen Hans-Högn-Str. 12 95030 Hof/Saale Tel.: 09281/1800-4572

6 7

[boost-users][Container] Compilation error using new "static_vector".
by Jupp Tscheak 20 Jul '13

20 Jul '13

Hello boost users, Please consider the following example: [code] #include "CGAL/Cartesian.h" #include "CGAL/Polygon_2.h" #include "boost/container/static_vector.hpp" typedef CGAL::Cartesian<double> Kernel; typedef Kernel::Point_2 Point2d; typedef CGAL::Polygon_2<Kernel, boost::container::static_vector<Point2d, 100> > Polygon2d; Polygon2d p; p = Polygon2d(); [/code] Compiling this code snippet with GCC results in following error message: [error] error: no match for 'operator=' in 'p = CGAL::Polygon_2<CGAL::Cartesian<double>, boost::container::static_vector<CGAL::Point_2<CGAL::Cartesian<double> >, 100u> >((*(const Traits*)(& CGAL::Polygon_2<CGAL::Cartesian<double>, boost::container::static_vector<CGAL::Point_2<CGAL::Cartesian<double> >, 100u> >::Traits())))' note: candidate is: CGAL-4.2/include/CGAL/Polygon_2.h:68:7: note: CGAL::Polygon_2<CGAL::Cartesian<double>, boost::container::static_vector<CGAL::Point_2<CGAL::Cartesian<double> >, 100u> >& CGAL::Polygon_2<CGAL::Cartesian<double>, boost::container::static_vector<CGAL::Point_2<CGAL::Cartesian<double> >, 100u> >::operator=(CGAL::Polygon_2<CGAL::Cartesian<double>, boost::container::static_vector<CGAL::Point_2<CGAL::Cartesian<double> >, 100u> >&) CGAL-4.2/include/CGAL/Polygon_2.h:68:7: note: no known conversion for argument 1 from 'sensor::Polygon2d {aka CGAL::Polygon_2<CGAL::Cartesian<double>, boost::container::static_vector<CGAL::Point_2<CGAL::Cartesian<double> >, 100u> >}' to 'CGAL::Polygon_2<CGAL::Cartesian<double>, boost::container::static_vector<CGAL::Point_2<CGAL::Cartesian<double> >, 100u> >&' [/error] I apologize for this concrete example using CGAL, but maybe someone has advice for me? Thanks in advance! Jupp Tscheak

2 2

Boost::thread instantiation and clean up
by Riskybiz 19 Jul '13

19 Jul '13

I have a C++ DLL written in Visual Studio for use on Windows 7 using Boost 1_53_0. The following two functions, CREATE & DESTROY, are called to launch and shutdown a simple ZeroMQ server (code below). The thread is launched and the server on that thread goes into a continuous listening loop (as intended). When it comes time to shut down the server then the thread is interrupted to cause thread termination (though I cannot tell if the interrupt is actually working as I get no output from the catch block). The boost::thread object is then deleted. Problem is that the 3rd party application which this DLL is designed for is prone to crashing after DESTROY is called and I think it's because either the boost::thread resources are not being freed/cleared up properly or the boost::thread is not interrupting. Have I properly handled thread instantiation, interruption and object destruction here? With thanks, Riskybiz. static bool createCalled = false;//initialise static variable static bool destroyCalled = false;//initialise static variable static boost::thread *serverThread = nullptr; int __stdcall CREATE() { if(createCalled == false) { createCalled = true; OutputDebugStringA("TestDataAccess: CREATE"); serverThread = new boost::thread(ListenOnReplySocket);//create instance of boost::thread object return 0; } return 1; } int __stdcall DESTROY() { if(createCalled == true && destroyCalled == false) { destroyCalled = true; OutputDebugStringA("TestDataAccess: DESTROY"); serverThread->interrupt();//set flag for interruption delete serverThread; return 0; } return 1; } Simple ZeroMQ server: #ifndef ZMQ_COMMUNICATIONS_H//if not defined already #define ZMQ_COMMUNICATIONS_H//then define it #define _WINSOCK2API_ //stops windows.h including winsock2.h #include <zmq.hpp> #include "boost\thread.hpp" int ListenOnReplySocket() { // Prepare our context and socket zmq::context_t context (1); zmq::socket_t socket (context, ZMQ_REP); socket.bind ("tcp://*:5555"); boost::this_thread::interruption_enabled(); try { while (true) { zmq::message_t request; // Wait for next request from client socket.recv (&request); char buffer[50]; int j; j = sprintf_s(buffer, 50, "TestDataAccess: ZMQComms: Hello"); OutputDebugStringA(buffer); // Do some 'work' Sleep (1000); // Send reply back to client zmq::message_t reply (5); memcpy ((void *) reply.data (), "World", 5); socket.send (reply); boost::this_thread::interruption_point();//check iterruption flag } } catch(boost::thread_interrupted) { char buffer[100]; int j; j = sprintf_s(buffer, 100, "TestDataAccess: ZMQComms: Server Thread Interrupted"); OutputDebugStringA(buffer); return 0; } } #endif

3 2

[fusion] how to get the tuple of min values of 2 tuples whatever their length?
by Frédéric Bron 18 Jul '13

18 Jul '13

I have two tuples: typedef boost::tuple<double, int, std::string> Key; Key k1, k2; I would like to get the tuple of the min values for each corresponding value between k1 and k2: Key min=Key(std::min(k1.get<0>(), k2.get<0>()), std::min(k1.get<1>(), k2.get<1>()), std::min(k1.get<2>(), k2.get<2>())); but I do not know the length of the tuple so I am looking for a generic algorithm... Is this possible with boost::fusion or boost::mpl? I have tried with boost::fusion::accumulate but I need to now in the functor the index of the value that is currently accessed to compare to the right one in k1. Frédéric

5 7

Named condition not behaving as expected
by rudasi 18 Jul '13

18 Jul '13

I have 2 processes (producer and consumer) sharing an int deque in shared memory, I have the producer process put 2 numbers in the deque and then it gets in a wait state losing its mutex lock. I then have the consumer process removing the numbers and printing them. It then does a notify on the condition which the producer is waiting on. The consumer then goes on its own wait on a second condition. After this case the producer does not wake up. I am using the same mutex between the processes. I have removed some of the code where i set up the shared memory and create the mutex and conditions. Producer process: int main() { scoped_lock<named_mutex> lock(mutex); while(1) { while (MyDeque->size() == 2) { full.wait(lock); std::cout << "unlocked producer" << std::endl; } if (MyDeque->size() == 0) { *a = 2; MyDeque->push_back(a); } if (MyDeque->size() == 1) { *b = 4; MyDeque->push_back(b); empty.notify_one(); } } } Consumer process: int main() { scoped_lock<named_mutex> lock(mutex); while(1) { //volatile int size = MyDeque->size(); while (MyDeque->size() == 0) { empty.wait(lock); } if (MyDeque->size() == 2) { std::cout << "Consumer: " << *MyDeque->front() << std::endl; MyDeque->pop_front(); } if (MyDeque->size() == 1) { std::cout << "Consumer: " << *MyDeque->front() << std::endl; MyDeque->pop_front(); full.notify_one(); } } } While debugging things seem to go ok for the first iteration, the producer puts numbers 2 and 4 on the deque then waits on the full condition. The Consumer then gets the lock, prints these numbers, does a notify_one on the full condition and then goes into a wait. After this the producer does not wake up. -- View this message in context: http://boost.2283326.n4.nabble.com/Named-condition-not-behaving-as-expected… Sent from the Boost - Users mailing list archive at Nabble.com.

1 0

[serialization] platform independence (32 & 64bit windows)
by आशीष वर्मन् 18 Jul '13

18 Jul '13

Hi We are using boost serialization our product which was 32bit only till now. Now we have started building it on 64bit as well. On finding that boost::binary_archive is not platform independent, we seem to have 2 options: 1. Use text_archive - (but are worried about performance since the serialized data is approx 500MB even after gzip compression) 2. Use the eos portable archive - (but it is updated only till boost 1.49. We are using 1.53) So my questions are: 1. One (and only one) of our archives created by our 32 bit executable is successfully read in by the 64 bit executable while the rest throw exception on reading the archive signature. If the platform is encoded in the signature, why is that one archive being read in successfully. 2. Which of the above two approaches would be better and why. Thanks in advance. Yours Sincerely Ashish Varman

3 3

Boost::Interprocess mutex with condition variable
by Riskybiz 17 Jul '13

17 Jul '13

I'm trying to get a working implementation of a boost::interprocess named_mutex with a named_condition_variable. I have created the following toy console applications to try and understand what's necessary. The console application 'Sleeper' is run first; it simply creates some resources and then goes to sleep. Then 'Waker' is run with the intention that it would cause the 'Sleeper' instance to resume execution and print out a further message. Ultimately the intention is to have one Waker process and several Sleeper processes. When each application is run in a separate terminal window then the Sleeper process sleeps and the Waker process tries to wake; but it is ineffective. Can anyone advise what is wrong here and how to get the notify_all() to take effect? Thanks Riskybiz. // Sleeper.cpp : Defines the entry point for the console application. // #include "stdafx.h" #include <boost/interprocess/managed_shared_memory.hpp> #include <boost/interprocess/sync/named_mutex.hpp> #include <boost/interprocess/sync/named_condition.hpp> #include <iostream> int _tmain(int argc, _TCHAR* argv[]) { using namespace boost::interprocess; //Clean up resources from any prior instances named_condition::remove("msm_named_condition"); named_mutex::remove("msm_named_mutex"); //shared_memory_object::remove("msm"); //Setup shared memory resources managed_shared_memory *msm = new managed_shared_memory(create_only, "msm", 10000); named_mutex *nm = new named_mutex(create_only, "msm_named_mutex"); named_condition *nc = new named_condition(create_only, "msm_named_condition"); try { scoped_lock<named_mutex> lock(*nm);//acquire scoped lock for mutex std::cout << "Going to sleep now...." << std::endl; nc->wait(lock);//induce wait std::cout << "Wide awake and back in the room" << std::endl;//print this out on waking up } catch(interprocess_exception &ipe) { std::cout << "Error in Sleeper process: interprocess_exception: "<< ipe.what() << std::endl; } //Clean up delete msm; delete nm; delete nc; return 0; } // Waker.cpp : Defines the entry point for the console application. // #include "stdafx.h" #include <boost/interprocess/managed_shared_memory.hpp> #include <boost/interprocess/sync/named_mutex.hpp> #include <boost/interprocess/sync/named_condition.hpp> #include <iostream> int _tmain(int argc, _TCHAR* argv[]) { using namespace boost::interprocess; //Setup shared memory resources managed_shared_memory *msm = new managed_shared_memory(open_only, "msm"); named_mutex *nm = new named_mutex(open_only, "msm_named_mutex"); named_condition *nc = new named_condition(open_only, "msm_named_condition"); try { scoped_lock<named_mutex> lock(*nm);//acquire scoped lock for mutex std::cout << "Going to Notify...." << std::endl; nc->notify_all();//notify to release the wait condition std::cout << "Wakey Wakey....Notified...." << std::endl; } catch(interprocess_exception &ipe) { std::cout << "Error in Waker process: interprocess_exception: "<< ipe.what() << std::endl; } //Clean up delete msm; delete nm; delete nc; return 0; }

2 1

multi_index_container with protected constructor
by Horváth Imre 17 Jul '13

17 Jul '13

Hi, I want to use boost::multi_index_container with a class that have protected constructors, but the compile fails. I think I should make multi_index_container a friend of my class, but I don't know how. #include <iostream> #include <boost/shared_ptr.hpp> #include <boost/multi_index_container.hpp> #include <boost/multi_index/ordered_index.hpp> #include <boost/multi_index/composite_key.hpp> #include <boost/multi_index/mem_fun.hpp> class Item { public: typedef boost::shared_ptr<Item> P; static P create() { return P(new Item()); } static P create(P item) { return P(new Item(item)); } protected: Item() { } Item(P item) : source(item->get_source()) , target(item->get_target()) { } public: std::string source; std::string target; std::string get_source() const {return source;} std::string get_target() const {return target;} struct key : boost::multi_index::composite_key< P, boost::multi_index::const_mem_fun<Item, std::string, &Item::get_source>, boost::multi_index::const_mem_fun<Item, std::string, &Item::get_target> >{}; typedef boost::multi_index_container< P, boost::multi_index::indexed_by< boost::multi_index::ordered_non_unique< key, boost::multi_index::composite_key_result_less<key::result_type> > > > index_t; }; int main() { Item::index_t index; Item::P t1 = Item::create(); index.insert(t1); return 0; } Thanks in advance: Imre Horvath

2 2

[Boost.Log] Example tutorial_fmt_stream.cpp does not compile
by Mario Knezović 17 Jul '13

17 Jul '13

I am trying to change date formatting exactly in the way as described in the tutorial, sub-section "Specialized formatters": http://www.boost.org/doc/libs/1_54_0/libs/log/doc/html/log/tutorial/formatt… What I want to achieve is pretty simple, change month output from the default "Abbreviated month name" (%b): [2013-Jul-08 10:51:00.989235] to "Month name as a decimal 01 to 12" (%m): [2013-07-08 10:51:00.989235] Unfortunately this does not compile, nor does the example from which the snipped is taken: "tutorial_fmt_stream.cpp". The interesting part in the example source is commented out by default. (But this was the case with other examples too.) The part I'm interested in is in line 60 (from current Boost 1.54.0): expr::format_date_time< boost::posix_time::ptime >("TimeStamp", "%Y-%m-%d %H:%M:%S") The errors I get (Win7, 64-bit, MS VC++ 2010): error C2027: use of undefined type "boost::log::v2s_mt_nt5::expressions::aux::date_time_formatter_generator_traits<T,CharT>" d:\boost\boost_1_54_0\boost\log\expressions\formatters\date_time.hpp 94 error C3861: "parse": Identifier not found. d:\boost\boost_1_54_0\boost\log\expressions\formatters\date_time.hpp 94 I hope somebody can help or point me in the right direction. Thank you! Mario Knezović

1 1

[log, spirit] phoenix version conflict
by Yi Ding 17 Jul '13

17 Jul '13

It looks like Boost.Log conflicts with Boost.Spirit because they're using different version of Boost Phoenix? Take this example file: #include <boost/log/common.hpp> #include <boost/log/sinks.hpp> #include <boost/spirit/include/karma.hpp> int main() { } We get this warning: In file included from /opt/boost_1_54_0/include/boost/log/detail/custom_terminal_spec.hpp:21, /opt/boost_1_54_0/include/boost/spirit/include/phoenix_core.hpp:13:1: warning: "BOOST_PHOENIX_DEFINE_CUSTOM_TERMINAL" redefined /opt/boost_1_54_0/include/boost/phoenix/core/terminal.hpp:22:1: warning: this is the location of the previous definition There are a bunch of errors that result as well.

2 2

How to build libboost_filesystem-vc110-mt-sgd-1_54.lib with VS2012 x64?
by Amann, Julian 17 Jul '13

17 Jul '13

I have some trouble building the boost filesystem lib using VS2012 x64. I use the following instructions to build it: 1. Download boost 1.54.0 from http://www.boost.org/ 2. Extract files (e.g. "C:\thirdparty\vs2013\x64\boost_1_54_0") 3. Start Visual Studio 2012 x64 command prompt 4. Change to boost directory (e.g. "cd C:\thirdparty\vs2010\x64\boost_1_54_0") 5. Execute .\bootstrap.bat 6. Execute b2 address-model=64 toolset=msvc-11.0 --build-type=complete stage --with-filesystem --with-signals --with-system Unfortunately the file "libboost_filesystem-vc110-mt-sgd-1_54.lib" is not build Previously I used boost 1.51.0, 1.52.0 and 1.53.0. In this releases the libboost_filesystem-vc110-mt-sgd-1_5x.lib was always build without any problems. Did anybody mange to build this lib using VS2012? Which instructions do you use to build it? Best regards, Julian

1 0

[log] operator<< best practices
by Yi Ding 16 Jul '13

16 Jul '13

I noticed boost log has a helper function for operator<< template< typename CharT, typename TraitsT, typename AllocatorT, typename T > inline basic_formatting_ostream< CharT, TraitsT, AllocatorT >& operator<< (basic_formatting_ostream< CharT, TraitsT, AllocatorT >& strm, T const& value) { strm.stream() << value; return strm; } which is useful because a lot of code has operator<< overloads specifically for std::ostream. Recently we've moved our code to use a generic template <class stream, int N> inline stream& operator<<(stream& os, const BlahClass& value) which conflicts with the boost log helper function, but is useful for our own ostream-like classes. What's the best practice here? Can we make the two mesh by using traits of some sort? Should we do all of our type to string conversions ahead of time using something like folly::to? Cheers, Yi

1 0

[Boost.Log] An update on severity level issue
by Leo Carreon 16 Jul '13

16 Jul '13

Hi all, I am still having the issue with the missing severity level string in the logs and have decided to give you my latest code. Here is my current code: #include <iostream> #include <iomanip> #include <cstdlib> #include <fstream> #include <boost/log/core.hpp> #include <boost/log/sources/global_logger_storage.hpp> #include <boost/log/sources/severity_logger.hpp> #include <boost/log/sources/record_ostream.hpp> #include <boost/log/attributes/clock.hpp> #include <boost/log/attributes/current_process_name.hpp> #include <boost/log/attributes/current_process_id.hpp> #include <boost/log/attributes/current_thread_id.hpp> #include <boost/log/utility/setup/file.hpp> #include <boost/log/utility/setup/from_stream.hpp> #include <boost/log/utility/manipulators/to_log.hpp> #include <boost/log/utility/formatting_ostream.hpp> using namespace std; namespace logging = boost::log; namespace keywords = boost::log::keywords; namespace expr = boost::log::expressions; namespace attr = boost::log::attributes; namespace src = boost::log::sources; #define LFC1_LOG_TRACE(logger) BOOST_LOG_SEV(logger, trace) << "(" << __FILE__ << ", " << __LINE__ << ") " #define LFC1_LOG_DEBUG(logger) BOOST_LOG_SEV(logger, debug) << "(" << __FILE__ << ", " << __LINE__ << ") " #define LFC1_LOG_INFO(logger) BOOST_LOG_SEV(logger, info) << "(" << __FILE__ << ", " << __LINE__ << ") " #define LFC1_LOG_WARNING(logger) BOOST_LOG_SEV(logger, warning) << "(" << __FILE__ << ", " << __LINE__ << ") " #define LFC1_LOG_ERROR(logger) BOOST_LOG_SEV(logger, error) << "(" << __FILE__ << ", " << __LINE__ << ") " static const auto RET_SUCCESS = 0; static const auto RET_FAIL = 1; static const auto LOGGING_ENVIRONMENT_NAME = "LOGGING_CONFIG_FILE_NAME"; static const auto DEFAULT_LOGGING_CONFIG_FILE_NAME = "config/LogSettings.txt"; enum ESeverityLevel { trace, debug, info, warning, error }; BOOST_LOG_ATTRIBUTE_KEYWORD(severity, "Severity", ESeverityLevel) ostream& operator<<(ostream& arStream, ESeverityLevel avLevel) { static const char* pStrings[] = { "trace", "debug", "info", "warning", "error" }; if (static_cast<size_t>(avLevel) < sizeof(pStrings) / sizeof(*pStrings)) { arStream << pStrings[avLevel]; } else { arStream << static_cast<int>(avLevel); } return arStream; } logging::formatting_ostream& operator<< ( logging::formatting_ostream& arStream, logging::to_log_manip<ESeverityLevel, tag::severity> const& arManip ) { static const char* pStrings[] = { "TRACE", "DEBUG", "INFO", "WARNING", "ERROR" }; ESeverityLevel vLevel = arManip.get(); if (static_cast<size_t>(vLevel) < sizeof(pStrings) / sizeof(*pStrings)) { arStream << pStrings[vLevel]; } else { arStream << static_cast<int>(vLevel); } return arStream; } BOOST_LOG_INLINE_GLOBAL_LOGGER_DEFAULT(SLogger, src::severity_logger<ESeverityLevel>) static void gvLoggingInit(const char* apConfigFileName = nullptr) { // Obtain the name of the logging configuration file. if (apConfigFileName == nullptr || apConfigFileName[0] == 0) { if ((apConfigFileName = getenv(LOGGING_ENVIRONMENT_NAME)) == 0 || apConfigFileName[0] == 0) { apConfigFileName = DEFAULT_LOGGING_CONFIG_FILE_NAME; } } // Open the logging configuration file. ifstream vConfigFile(apConfigFileName); if (!vConfigFile.is_open()) { // TODO: throw an exception } // Read the contents of the logging configuration file. logging::init_from_stream(vConfigFile); // Add the logging attributes that we require. auto pCore = logging::core::get(); pCore->add_global_attribute("TimeStamp", attr::local_clock()); pCore->add_global_attribute("Process", attr::current_process_name()); pCore->add_global_attribute("ProcessID", attr::current_process_id()); pCore->add_global_attribute("ThreadID", attr::current_thread_id()); pCore->set_filter(severity >= info); } int main() { auto vRetVal = RET_SUCCESS; try { gvLoggingInit(); auto& vLogger = SLogger::get(); LFC1_LOG_TRACE(vLogger) << "A trace severity message"; LFC1_LOG_DEBUG(vLogger) << "A debug severity message"; LFC1_LOG_INFO(vLogger) << "An informational severity message"; LFC1_LOG_WARNING(vLogger) << "A warning severity message"; LFC1_LOG_ERROR(vLogger) << "An error severity message"; } catch (exception& crException) { cerr << crException.what() << endl; vRetVal = RET_FAIL; } catch (...) { cerr << "Unknown exception" << endl; vRetVal = RET_FAIL; } return vRetVal; } Here is what’s in the settings file: [Core] Filter="%Severity% >= 2" DisableLogging=false [Sinks.File] Destination=TextFile FileName=log/test_logging_%N.log RotationSize=1048576 Target=logs MaxSize=10485760 ScanForFiles=All Format="%TimeStamp% [%Severity%] %Process%:%ProcessID%:%ThreadID% %Message%" As mentioned in a previous post, the issue I’m having is this is how the resulting log records look like: 2013-Jul-16 11:24:59.758177 [] test_logging:000000x9f3:0x403cc6c0 (src/test_logging.cpp, 240) An informational severity message 2013-Jul-16 11:24:59.758812 [] test_logging:000000x9f3:0x403cc6c0 (src/test_logging.cpp, 241) A warning severity message 2013-Jul-16 11:24:59.758851 [] test_logging:000000x9f3:0x403cc6c0 (src/test_logging.cpp, 242) An error severity message Note that the severity string is missing from the above log records. Does anyone know I can fix the code to make the severity string show up in the log records? Another question I have is how do I change the format of the date in the timestamp from YYY-MMM-DD to YYYY-MM-DD. I am sticking to using logging settings from a file because I want an application user to be able to control where log records go. However, I am open to the idea of setting the format within the code but at the moment there is no option of setting the format when a settings file is used. It would be nice to have a function within the logging core which allows us to obtain a pointer/reference to the existing sinks. Kind regards, Leo

1 0

Problems include the RANDOM LIBRARIES, in a console project, in Windows.
by Alberto Aliberti 16 Jul '13

16 Jul '13

I used the Random libraries of Boost collection. I have implemented it in my program. A program for the chess analysis . Now, at compile time I have no problem. Everything ok, the console project is compiled without errors. During run time, the functions of Boost Random libraries, correctly generate a random number. But after a few repetitions of the loop (from 2/3 to a few tens of loops), the program crashes. The strange thing that the crash does not occur in the functions where I use the random functions, but occurs in the chess engine that does not use these functions, and thus in theory should not be influenced by it. But if I do not use the functions of Boost library and use the basic function of C + + (rand ();) I have no problems. I work in Windows. My project is a console project compiled with VC + +2010. Also I have wrote a test program with VC + +2010, which generates a sequence of random numbers, using Boost libraries. In this case I have no problems. Only when I implement the libraries in the chess program I have problems. So it seems that your libraries are in conflict with the chess engine. What do you recommend for the search for the cause of the problem? The headers and the function use by me in my program: #include <boost/random/mersenne_twister.hpp> #include <boost/random/uniform_smallint.hpp> // initializes boost random generator seed boost::random::mt19937 gen; // random function int ransel(int minr,int maxr) { boost::random::uniform_smallint <> dist(minr, maxr); return dist(gen); } ________ Then I call the ransel() function in the loop of my program to select the chess moves.

2 2

quick threading query
by Sean Farrow 15 Jul '13

15 Jul '13

Hi all, I have a quick threading query. I'm in the process of rewriting an application to take advantage of concurrency. This application is cross-platform so I'm looking at the boost threading library to solve the issue. When the window is created I'm creating a thread, then when the user chooses to quit I need to notify the created thread to stop running. Would a future do the job, if this is the case where should this be stored in the class that represents the window or in the class that represents the thread, I'm really not wanting to store this globally. Any help appreciated. Cheers Sean.

2 1

1.54.0 breaks bcp-produced partial builds?
by Bruce Stephens 15 Jul '13

15 Jul '13

Back in 1.53.0, I could do the following: ./bootstrap.sh (cd tools/bcp; ../../b2) bin.v2/.../bcp build filesystem .../temp Then in .../temp run ./bootstrap.sh and ./b2 to build just filesystem (or whatever else I copied). In 1.54.0, the copy doesn't build: brs% ./b2 Building the Boost C++ Libraries. /auto/tmpfs/temp/tools/build/v2/build/targets.jam:397: in find-really *** argument error * rule project.is-registered-id ( id ) * called with: ( ) * missing argument id /auto/tmpfs/temp/tools/build/v2/build/project.jam:600:see definition of rule 'project.is-registered-id' being called /auto/tmpfs/temp/tools/build/v2/build/targets.jam:457: in class(a)project-target.find /auto/tmpfs/temp/tools/build/v2/build/targets.jam:841: in resolve-reference /auto/tmpfs/temp/tools/build/v2/build/targets.jam:858: in targets.generate-from-reference /auto/tmpfs/temp/tools/build/v2/build/targets.jam:1245: in generate-dependencies /auto/tmpfs/temp/tools/build/v2/build/targets.jam:1302: in class(a)basic-target.generate /auto/tmpfs/temp/tools/build/v2/build/targets.jam:757: in generate-really /auto/tmpfs/temp/tools/build/v2/build/targets.jam:729: in class(a)main-target.generate /auto/tmpfs/temp/tools/build/v2/build/targets.jam:272: in class(a)project-target.generate /auto/tmpfs/temp/tools/build/v2/build/targets.jam:874: in targets.generate-from-reference /auto/tmpfs/temp/tools/build/v2/build/targets.jam:1245: in generate-dependencies /auto/tmpfs/temp/tools/build/v2/build/targets.jam:1302: in class(a)basic-target.generate /auto/tmpfs/temp/tools/build/v2/build/targets.jam:757: in generate-really /auto/tmpfs/temp/tools/build/v2/build/targets.jam:729: in class(a)main-target.generate /auto/tmpfs/temp/tools/build/v2/build/targets.jam:874: in targets.generate-from-reference /auto/tmpfs/temp/tools/build/v2/build/targets.jam:1245: in generate-dependencies /auto/tmpfs/temp/tools/build/v2/build/targets.jam:1302: in alias-target-class.generate /auto/tmpfs/temp/boostcpp.jam:391: in build-multiple /auto/tmpfs/temp/boostcpp.jam:353: in class(a)top-level-target.generate /auto/tmpfs/temp/tools/build/v2/build/targets.jam:757: in generate-really /auto/tmpfs/temp/tools/build/v2/build/targets.jam:729: in class(a)main-target.generate /auto/tmpfs/temp/tools/build/v2/build/targets.jam:874: in targets.generate-from-reference /auto/tmpfs/temp/tools/build/v2/build/targets.jam:1245: in generate-dependencies /auto/tmpfs/temp/tools/build/v2/build/targets.jam:1302: in alias-target-class.generate /auto/tmpfs/temp/boostcpp.jam:391: in build-multiple /auto/tmpfs/temp/boostcpp.jam:353: in class(a)top-level-target.generate /auto/tmpfs/temp/tools/build/v2/build/targets.jam:757: in generate-really /auto/tmpfs/temp/tools/build/v2/build/targets.jam:729: in class(a)main-target.generate /auto/tmpfs/temp/tools/build/v2/build/targets.jam:272: in class(a)project-target.generate /auto/tmpfs/temp/tools/build/v2/build-system.jam:707: in load /auto/tmpfs/temp/tools/build/v2/kernel/modules.jam:289: in import /auto/tmpfs/temp/tools/build/v2/kernel/bootstrap.jam:139: in boost-build /auto/tmpfs/temp/boost-build.jam:17: in module scope

1 1

Re: [Boost-users] [Boost.Log] More queries
by Leo Carreon 15 Jul '13

15 Jul '13

From: Leo Carreon Sent: Saturday, July 13, 2013 3:51 PM To: Boost Users Mailing List Subject: [Boost.Log] More queries Hi everyone, As I have mentioned in a previous post, I have been trying to learn how to use Boost.Log. I have been experimenting with logging to a file with filtering and specifying the log formatting in three different ways, namely: 1. Specifying the log formatting using a lambda type expression. 2. Specifying the log formatting using a plain text string with placeholders for the attributes that I have defined. 3. Specifying the log formatting in a settings file. (However, the formatting string is exactly the same as in 2 above.) I have attached a copy of my source code and settings file. Note that I comment out parts of the source code file depending on which option I use above. The problem I’m encountering is when I use options 2 & 3 above, the severity level string does not appear in the log. But if I use option 1, the severity level string appears as expected. It is my understanding that severity level is a pre-defined attribute when using a severity_logger. Am I missing something when using options 2 & 3? If I decide to use my own severity level enumeration, what do I need to do? Kind regards, Leo Hi again everyone, I have managed to use my own severity level enumeration but the severity level string is still not appearing in the log. Regards again, Leo

2 4