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

[quickbook] Understanding xsl:param(s) for TOC generation
by legalize+jeeves＠mail.xmission.com 01 Aug '13

01 Aug '13

[Please do not mail me a copy of your followup] I have this magic recipe in my jam file: import quickbook ; boostbook foo : src/foo.qbk : <xsl:param>chunk.section.depth=4 <xsl:param>chunk.first.sections=1 <xsl:param>toc.section.depth=4 <xsl:param>toc.max.depth=4 <xsl:param>generate.section.toc.level=4 and to be honest I copy/pasted it from somewhere else and I really don't understand this recipe. I looked in the quickbook documentation and I couldn't find anything discussing these parameters like toc.max.depth, etc. Where can I find documentation on these paramters? -- "The Direct3D Graphics Pipeline" free book <http://tinyurl.com/d3d-pipeline> The Computer Graphics Museum <http://computergraphicsmuseum.org> The Terminals Wiki <http://terminals.classiccmp.org> Legalize Adulthood! (my blog) <http://legalizeadulthood.wordpress.com>

3 2

Storing path from A*, using operator::new with boost::multi_array
by Sladey 01 Aug '13

01 Aug '13

I'm trying to use dynamic memory allocation for the first time. I want to allocate memory for a 2 dim dynamic array, to store paths from an A* function. I think the array for the job is boost::multi_array. Problem I have is seem to be able to allocate the memory but i can't change or access any of the elements. #include <iostream> #include "boost/multi_array.hpp" typedef boost::multi_array<int, 2> array_type; int main() { array_type *A = new array_type; A->resize( boost::extents[2][2] ); A[1][1] = 2; std::cout << A[1][1] << std::endl; delete A; return 0; } -- View this message in context: http://boost.2283326.n4.nabble.com/Storing-path-from-A-using-operator-new-w… Sent from the Boost - Users mailing list archive at Nabble.com.

3 2

Boost 1.52 with Cygwin and STLPort 5.2.1
by Akanksh Vashisth 31 Jul '13

31 Jul '13

Hello, I am trying to compile the following source file using gcc on cygwin and stlport: //-------------------------------------- //cygwin_stl.cpp #include <boost/graph/graphviz.hpp> int main() { return 0; } //-------------------------------------- with the following commandline: //-------------------------------------- $ gcc cygwin_stl.cpp -I /cygdrive/y/STLPORT/STLport-5.2.1/stlport/ -I /cygdrive/y/BOOST/boost_1_52_0/ //-------------------------------------- and this is resulting in an assertion inside boost/xpressive/traits/cpp_regex_tratis.hpp at line 74 as: //-------------------------------------- /cygdrive/y/BOOST/boost_1_52_0/boost/xpressive/traits/cpp_regex_traits.hpp:74:9: error: no matching function for call to ‘assertion_failed(mpl_::failed************ mpl_::assert_relation<(mpl_::assert_::relations)1u, -0x000000069l, 2l>::************)’ //-------------------------------------- Complete error message attached. It appears that the boost header has a conditional compilation for __CYGWIN__ where it asserts a property of the STL std::ctype_base headers that come with cygwin. But as I am using STLport, the assertion does not hold true any longer, but I do have the preprocessor macro __CYGWIN__defined. The code in cpp_regex_traits.hpp is as follows: //-------------------------------------- #ifdef __CYGWIN__ // Work around a gcc warning on cygwin template<> struct mask_cast<std::ctype_base::print> { BOOST_MPL_ASSERT_RELATION('\227', ==, std::ctype_base::print); BOOST_STATIC_CONSTANT(umaskex_t, value = 0227); }; #endif //-------------------------------------- I do have __CYGWIN__ as I am on cygwin, but the STL header is coming from STLport, thus the assertion fails. Is there anyway I can work around this issue? or is it a bug in the boost header where it the test for __CYGWIN__ is insufficient? as a third party STL can be used with cygwin, in which case the assertion is invalid. Thanks

1 0

[FileSystem] detect whether a path has a termi9nating separator
by Sean Farrow 31 Jul '13

31 Jul '13

Hi all, Firstly I apologise for the lameness of the question-or if I'm missing something really obvious but, is there a function in boost filesystem or on the path object to terminate the path with a separator if one doesn't exist? Help/pointers appreciated. Regards Sean.

1 0

compiling with -std=c++0x option
by Norman Lo 31 Jul '13

31 Jul '13

Hello, I am trying to compile a source file that utilizes boost::multi_array. When I try to compile the file with the option -std=c++0x, I get the following error: /apps/boost_1_48/include/boost/multi_array/extent_gen.hpp(62): error: class "boost::detail::multi_array::extent_gen<2UL>" has no suitable copy constructor return extent_gen<NumRanges+1>(*this,range(0,idx)); ^ detected during instantiation of "boost::detail::multi_array::extent_gen<<expression>> boost::detail::multi_array::extent_gen<NumRanges>::operator[](boost::detail::multi_array::index={ptrdiff_t={long}}) [with NumRanges=1UL]" at line 48 of When I compile the same source file without -std=c++0x option, it compiles fine. The compiler I am using: icpc 12.1.0 gcc version: 4.5.0 boost version 1_48 Any help is greatly appreciated. Thanks! Norman

1 0

Deserializing Boost archives using C#
by Robert Fairlie 30 Jul '13

30 Jul '13

Hi, I'm currently writing a component in C++ which creates a hierarchy of objects, and serializes them using the Boost serialization library. The serialized archive consists of a root "Document" object, which consists of an STL vector of "Pages". Each page consists of an STL vector of other object types, which themselves have sub-objects. The platform is Microsoft Windows. At some time in the future I want to port the component to C#. One option would be to call the Boost library from C# using interop, but I'd rather try to code it completely in C#, as that would bring a lot of portability benefits. What I'd ideally like to do therefore is in the future to deserialize with C# any files currently being saved with C++. Since Boost provides XML archives I thought I'd look at changing from my current text archives to XML archives. That was straightforward and I'm now saving to XML archives. I'm now starting to look at whether it possible to deserialize an XML archive using C#, possibly by writing a skeleton test component in C#. I'm pretty familiar with C#, but not XML serialization in C#, so I'm not sure yet how to map the XML elements (and class ids ?) to C# objects. In the meantime I was wondering if any one has done anything like this or had any thoughts on whether this approach is feasible? Thanks for any advice, Robert Fairlie -- View this message in context: http://boost.2283326.n4.nabble.com/Deserializing-Boost-archives-using-C-tp4… Sent from the Boost - Users mailing list archive at Nabble.com.

1 0

[Boost.Log] compiling issue of trivial example under boost version 1.5.4
by Steven Sun 30 Jul '13

30 Jul '13

Hi All - I was trying to compile the boost log example code under boost_1_54_0/libs/log/example/trivial/. I basically want to have a simple logger with filter function. So the example code serves the purpose. I got the attached error message while trying to compile. I think my compile command is fine because if I comment out the section of " core::get()->set_filter ( trivial::severity >= trivial::info ); " it compiles and runs fine. Can someone please provide some insight of how to make the severity filter work? Best, -- Steven Sun ********************************************************* Eco-Tips: Please consider the environment before printing this email!

1 0

[datetime] to/from ISO
by Michael Powell 30 Jul '13

30 Jul '13

Hello, I have a cross platform date/time quirk I want to work out. I am using Boost DateTime Posix to_iso_string and from_iso_string to pass date/time fields over the wire. What I am finding is that C# .NET DateTime and/or Boost DateTime Posix ISO do not agree, at least where ISO format is concerned. So... Is it a Boost issue? Or a .NET issue? I'm not positive, but the ISO format goes something like this: "YYYY-mm-DDTHH:MM:SS" Whereas Boost interpretation of that is something like: "YYYYmmDDT..." Something else after 'T', not sure, is that seconds since the epoch? Something like that. Anyway. Parsing the tree is falling over on that interpretation. A workaround is to leave the field out (for now), but longer term I would like to preserve the time field in whatever date/time format will work and parse ubiquitously over the wire. Any recommendations? Thank you... Regards, Michael Powell

1 1

[Spirit][Math] karma: regression in 1.54 due to argument promotion in math?
by Igor R 30 Jul '13

30 Jul '13

Hello, The following code compiles with 1.53, but fails with 1.54 (FreeBSD 9.1, gcc4.2.1): #include <boost/spirit/include/karma.hpp> #include <string> #include <iterator> int main() { using namespace boost::spirit::karma; std::string result; std::back_insert_iterator sink(result); unsigned short a; generate(sink, auto_, a); } The error is: boost/boost/math/tools/promotion.hpp: In instantiation of 'boost::math::tools::promote_args<long double, float, float, float, float, float>': boost/boost/math/special_functions/sign.hpp:114: instantiated from 'int boost::math::signbit(T) [with T = long double]' boost/boost/spirit/home/support/detail/sign.hpp:47: instantiated from 'bool boost::spirit::detail::signbit(T) [with T = long double]' boost/boost/spirit/home/karma/numeric/detail/numeric_utils.hpp:130: instantiated from here boost/boost/math/tools/promotion.hpp:141: error: invalid application of 'sizeof' to incomplete type 'boost::STATIC_ASSERTION_FAILURE<false>' I.e., the compilation fails because FreeBSD doesn't supprt "long double" type. This happens now due to the following changes in boost/math/special_functions/sign.hpp : 123 template<class T> int (signbit)(T x) 124 { 125 typedef typename detail::fp_traits<T>::type traits; 126 typedef typename traits::method method; 127 - typedef typename boost::is_floating_point<T>::type fp_tag; 128 - return detail::signbit_impl(x, method()); 127 + // typedef typename boost::is_floating_point<T>::type fp_tag; 128 + typedef typename tools::promote_args<T>::type result_type; 129 + return detail::signbit_impl(static_cast<result_type>(x), method()); 130 } So, what would be the right way to reconcile karma and math? Thanks, Igor'.

2 2

interprocess file_lock timed_lock not returning false after timeout
by Claudio Bantaloukas 30 Jul '13

30 Jul '13

Hi all! I think there are two issues, one is a documentation issue, the other might be a bug with boost::interprocess file_lock. The documentation issue is that it was not clear to me by reading the documentation on file_lock that it is a RAII-style class. By reading that it has process lifetime, I assumed that once acquired, the lock would be held even after the file_lock object is destroyed. Once I figured this out, I changed the file_lock to a static method variable and ran into the following issue. I have two processes that use the following class method that I wrote. They both try to acquire a lock on the same file and the lock must be held until the process exits. When I start the first process, it acquires the lock correctly. When I start up the second process, I would expect the following code to return false after 10 seconds //// static boost::interprocess::file_lock process_flock(processLockFile.string().c_str()); if (!process_flock.timed_lock(wait_until)){ //// However, when I read through the logs, I see that the process reaches the timed_lock call and gets stuck there. Can you please help me diagnose this? I'm attaching the entire method with log lines treated for brevity. Boost version is 1.53, running on Centos 6. Thanks! ------------------------8<-------------- ReturnStatus ProcessLocker::lockViaFile() { L_CONTEXT("ProcessLocker::lockViaFile()"); path lockDirectory(lockFileDirectoryName); if (!exists(lockDirectory)){ L_ERROR("missing lock directory"); return r_error; } if (!is_directory(lockDirectory)){ L_ERROR("lock path is not a directory"); return r_error; } path globalLockFile = lockDirectory / "general-locking.lock"; // make sure file exists boost::filesystem::ofstream globalfile(globalLockFile, std::ios::out); // we do nothing with it... globalfile.close(); std::string filename; // class member, this is the process identifier, and is the same between invocations filename.append(identifier); filename.append(".lock"); path processLockFile = lockDirectory / filename; // make sure file exists boost::filesystem::ofstream processfile(processLockFile, std::ios::out); // we do nothing with it... processfile.close(); try { ptime now(second_clock::local_time()); ptime wait_until = now +seconds(10); L_DEBUG("Waiting for global lock until " << wait_until); boost::interprocess::file_lock global_flock(globalLockFile.string().c_str()); if (!global_flock.timed_lock(wait_until)){ L_ERROR("Cannot create global lock"); return r_error; } try { L_DEBUG("Waiting for process lock until " << wait_until); static boost::interprocess::file_lock process_flock(processLockFile.string().c_str()); if (!process_flock.timed_lock(wait_until)){ global_flock.unlock(); // this point is never reached!? L_ERROR("Cannot create process lock"); return r_error; } global_flock.unlock(); L_DEBUG("Obtained process lock, freeing global lock"); return r_ok; } catch (std::exception& e){ global_flock.unlock(); L_ERROR("Cannot create process lock, freeing global lock"); return r_error; } } catch (std::exception& e){ L_ERROR("Cannot create global lock"); return r_error; } } -- Claudio Bantaloukas

1 1