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

Compile errors in pointer_traits.hpp after upgrade to 1_58_0
by James Walker 20 Apr '15

20 Apr '15

After switching from Boost 1_57_0 to 1_58_0, I get various compile errors in pointer_traits.hpp, where it uses the macro BOOST_INTRUSIVE_HAS_STATIC_MEMBER_FUNC_SIGNATURE: warning: declaration does not declare anything error: use of undeclared identifier 'check' error: 'U' does not refer to a value This is with Xcode 4.6.3 and the Apple LLVM 4.2 compiler.

2 2

Boost Spirit Karma - convert character to hex representation
by Ernest Zaslavsky 20 Apr '15

20 Apr '15

There is karma::hex formatter and I need somehow to add zero padding to get “0a” instead of just “a”. in addition it would be lovely to have some king of control over hex letter case. It sounds like a policies for real or Boolean formatters but I didn’t find one for hex. Is it possible to achieve the above without policy? [Read More]<http://feeds.feedburner.com/~r/sizmek-blog/~6/1> [http://www.sizmek.com/Sizmek.png]<http://www.sizmek.com/>

2 4

Re: [Boost-users] Boost 1.58.0 has been released
by Florent Guiliani 20 Apr '15

20 Apr '15

On 4/18/15 6:00 PM, boost-users-request(a)lists.boost.org wrote: > On Fri, Apr 17, 2015 at 8:59 PM, Tom Kent<lists(a)teeks99.com> wrote: >> > >> >On Fri, Apr 17, 2015 at 3:58 PM, Marshall Clow<mclow.lists(a)gmail.com> >> >wrote: >>> >> >>> >>Release 1.58.0 of the Boost C++ Libraries is now available. > You sure about that? > Did you forget to push the release tag on Github? https://github.com/boostorg/boost/releases The release tag boost-1.58.0 is missing on Github. -- Florent

1 0

Compile error with boost::factory after upgrade to 1.58.0
by Bitar Fadi 18 Apr '15

18 Apr '15

Hi, I installed Boost 1.58.0 today, having been using 1.57.0 previously, and noticed that a part of my code that uses boost::factory doesn't compile anymore. Here's briefly what I'm doing, followed by the error message I'm getting: typedef boost::function<Apollo::ReportGenerator*(Apollo::ApolloBaseModel*)> reportFactory; struct reportListing { std::string displayName; reportFactory factory; reportListing(std::string name, reportFactory f) : displayName(name), factory(f) { } }; std::vector<reportListing> reportFactories; reportFactories.push_back(reportListing("Scenario Analyzer", boost::factory<Apollo::ScenarioAnalyzer*>())); // Apollo::ReportGenerator being the base class from which Apollo::ScenarioAnalyzer is derived ... The constructor for ScenarioAnalyzer is: ScenarioAnalyzer(Apollo::ApolloBaseModel* model) This fails to compile with the following error (on Windows 7 using Visual C++ 12): error C2664: 'Apollo::ScenarioAnalyzer *boost::factory<Pointer,void,factory_alloc_for_pointee_and_deleter>::operator ()(void) const' : cannot convert argument 1 from 'Apollo::ApolloBaseModel *' to 'Apollo::ApolloBaseModel *&' I'm just wondering if that is caused by an intentional change or not, because according to the change log to boost::factory no significant changes with implications to backward compatibility have been made. Also, I'm not sure I know how to get rid of this error. Thanks for the help! /Fadi ________________________________ Fadi Bitar Modeling and simulation specialist Energy Markets Telephone direct +46 (0)8 695 64 05 Mobile +46 725 40 64 05 fadi.bitar(a)sweco.se<mailto:fadi.bitar@sweco.se> Sweco Energuide AB Gjörwellsgatan 22 P.O. Box 34044 SE-100 26 Stockholm Telephone +46 8 695 60 00 www.sweco.se<http://www.sweco.se/> [cid:image001.jpg@01CECF3E.855DC4C0] Please consider the environment before printing this e-mail.

1 0

Boost 1.58.0 has been released
by Marshall Clow 18 Apr '15

18 Apr '15

Release 1.58.0 of the Boost C++ Libraries is now available. These open-source libraries work well with the C++ Standard Library, and are usable across a broad spectrum of applications. The Boost license encourages both commercial and non-commercial use. This release contains two new libraries and numerous enhancements and bug fixes for existing libraries. New Libraries * Endian: Types and conversion functions for correct byte ordering and more regardless of processor endianness. * Sort: Includes spreadsort, a general-case hybrid radix sort that is faster than O(n*log(n)) For details, including download links, see http://www.boost.org/users/news/version_1.58.0 You can also download directly from SourceForge: http://sourceforge.net/projects/boost/files/boost/1.58.0/ To install this release on your system, see http://www.boost.org/doc/libs/release/more/getting_started/index.html Thanks, --The Boost release team Vladimir Prus Rene Rivera Marshall Clow Eric Niebler Daniel James Beman Dawes

3 2

How to suppress warnings from boost headers
by avib369 . 17 Apr '15

17 Apr '15

Is there any way using boost to suppress warning messages issued from the boost headers ? Is there a way to replace -I with -isystem ? Ta, Avi

1 0

multiprecision -- eigen matrices using dynamically allocated variable-precision mpfr_float
by Daniel Brake 17 Apr '15

17 Apr '15

I'd like to use the variable-precision mpfr_float type offered by the Boost.Multiprecision library, with the templated Eigen linear algebra library. I observe that if I make an identity matrix created with dynamically-allocated variable-precision mpfr_floats, and multiply it against itself, every other row is populated with nan's. Here is some code: int main(){ int size = 9; typedef boost::multiprecision::mpfr_float_backend<0, boost::multiprecision::allocate_dynamic> mybackend; typedef boost::multiprecision::number<mybackend, boost::multiprecision::et_on> mynumtype; typedef Eigen::Matrix<mynumtype, Eigen::Dynamic, Eigen::Dynamic> mp_matrix; mp_matrix A = mp_matrix::Identity(size, size); mp_matrix B = A*A; std::cout << B << std::endl; return 0; } output: 1 0 0 0 0 0 0 0 0 nan nan nan nan nan nan nan nan nan 0 0 1 0 0 0 0 0 0 nan nan nan nan nan nan nan nan nan 0 0 0 0 1 0 0 0 0 nan nan nan nan nan nan nan nan nan 0 0 0 0 0 0 1 0 0 nan nan nan nan nan nan nan nan nan nan nan nan nan nan nan nan nan nan I have been able to pin it down to the allocate_dynamic switch; if I select allocate_stack, the product computes correctly; allocate_dynamic reliably generates nans. Fixed-precision numbers work just fine, and expression templates on/off make no difference. I'd like to use the dynamic allocation, as I expect to use thousands of digits at times. I am using clang++, with c++11, on OSX, Boost 1.57.0, Eigen 3.2.4. Same behaviour in 1.56 / 3.2.3. It seems like maybe an offset issue, but I just can't get there by myself. I've also played with defining the NumTraits in Eigen various ways, but nothing affects the nan behaviour. Does anyone have any ideas? Daniel Brake Postdoctoral Research Scholar University of Notre Dame

2 5

[boost][thread] thread_local vs boost::thread_specific vs ::pthread_key_t
by chilabot＠gmail.com 16 Apr '15

16 Apr '15

I have a program that dlopens some libraries (all C++), that use TLS for a variable (which passed to all libraries). With the keyword 'thread_local' and with 'boost::thread_specific', the storage of the variable is different for every thread AND for every shared library. With 'pthread_key_t' it's only different for every thread, it behaves as expected. I guess 'boost::thread_specific' uses 'thread_local' and that's why it behaves like it. Why does 'thread_local' behave like this? $ clang --version Ubuntu clang version 3.5.0-4ubuntu2~trusty2 (tags/RELEASE_350/final) (based on LLVM 3.5.0) Target: x86_64-pc-linux-gnu Thread model: posix $ uname -a Linux robert-y510p 3.13.0-49-generic #81-Ubuntu SMP Tue Mar 24 19:29:48 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux ref http://stackoverflow.com/questions/29656089/ thread-local-vs-boostthread-specific-vs-pthread-key-t

1 0

[IPC Named Mutex]
by Lorenzo Trivelli 16 Apr '15

16 Apr '15

Hi to everyone, I'm experiencing a strange behaviour of named mutex on a windows 2008 machine. symptoms: when the system event log is empty, creation of named mutex fails with a boost::interprocess::interprocess:exception with msg boost::interprocess_exception::library_error. Now some data: 1) Boost 1.57.0 + stlport 5.2 2) VS 2005 3) Target Environment: Win 2008/32 3) after a night of code digging I managed to crete a small sample which raises the exception: #include <boost/shared_ptr.hpp> #include <boost/interprocess/sync/named_mutex.hpp> #include <boost/interprocess/sync/scoped_lock.hpp> #include <iostream> typedef boost::shared_ptr<boost::interprocess::named_mutex> safe_ipc_mx; static safe_ipc_mx __mx; int main(void) { system("pause"); try { __mx = safe_ipc_mx(new boost::interprocess::named_mutex(boost::interprocess::open_or_create_t(),"JAEGER")); std::cout << std::endl << "Mutex created !" << std::endl; } catch(boost::interprocess::interprocess_exception const& e) { std::cout << std::endl << "Mutex creation error " << e.what() << " /" << e.get_error_code() << " /" << e.get_native_error(); } system("pause"); return 0; } as far as I digged, it seems that the trouble is in the winapi::get_last_bootup_time(stamp) call in shared_dir_helpers.hpp, but up to now I had not been able to reproduce it on a machine with all the debugging tools installed does anyone have a clue on what I am doing wrong ? thanks in advance Lorenzo

2 1

Re: [Boost-users] Project linking problem with boost
by Max 16 Apr '15

16 Apr '15

----- Original Message ----- From: <Mark.Bartosik(a)thomsonreuters.com> To: <boost-users(a)lists.boost.org> Subject: Re: [Boost-users] Project linking problem with boost Date: 2015-04-15 22:59 Try one of the /VERBOSE options on the linker’s command line will get you this information, I cannot remember which is the most painless one though. From the command line: /VERBOSE[:{CLR|ICF|INCR|LIB|REF|SAFESEH|UNUSEDLIBS}] /VERBOSE:LIB You can find this under Properties, Linker, General, Show Progress You can also set directly Properties, Linker, Command Line As I recall just /VERBOSE:LIB should generate a lot of output about which library is pulled in (and hopefully by which other library). Just the /VERBOSE output generate a huge amount of output (minimize the window and open with text editor later or it will be a long wait). - Mark - ------------------------------------------------------ Dear Mark, Thank you very much for your information - I didn't know this technique before. The problem is, though the problem seemed to be related to the linking process, the message as in my previous email was emitted by VS2008 before the linking process begins. So for the time being, I cannot benefit from adding extra switches to the link command. Best regards,Max --------------------------------------------------- From: Boost-users [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Max Sent: Wednesday, April 15, 2015 5:49 AM To: boost-users Subject: [Boost-users] Project linking problem with boost Sent: Wednesday, April 15, 2015 5:49 AM To: boost-users Subject: [Boost-users] Project linking problem with boost Hello, The problem here relates to boost, but I'm aware it may of more general nature rather than boost specific. I had a weird problem with my project. It has a bunch of dependencies including many of the boost libraries. My platform is: Win7SP1 + VS2008SP1 + boost1.39.0. I have properly set the VC++ directories for both include and lib files pointing to the boost folder (1.39.0) and of course those for other dependencies. But I got the following message when I built the project: 1>Linking to GSL lib 1>Linking to lib file: CGAL-vc90-mt.lib 1>Linking to lib file: libboost_date_time-vc80-mt-1_34.lib 1>Linking to lib file: libboost_regex-vc80-mt-1_34.lib I don't know why VS was attempting to link to libs of boost 1.34.0 built with VC80 (I'm using VC 90 - VS2008) Could anybody please give me some hints about this problem or where the message like "Linking to lib file: ..." came from? Thanks. Best regards, Max _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

1 0