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

My last message
by Osman Zakir 02 Jan '19

02 Jan '19

Hi, everyone. Did you guys see my last message? I really need to get a reply ASAP.

4 9

function template with a universal reference to a specific type
by Ireneusz Szcześniak 01 Jan '19

01 Jan '19

Hi, I'm writing to ask a C++ question, not specifically Boost-related, but this list is the best place I know. How can I write a function template, which has a parameter of the universal reference to a specific type? I can write a function template like this: template <typename T> void foo(T &&t) { // The primary template implementation. cout << "Primary: " << __PRETTY_FUNCTION__ << endl; } And so I can call this function with an expression of any value category, and any type, cv-qualified or not, like this: int main() { foo(1); int i = 1; foo(i); const int ci = 1; foo(ci); } In my code I need to provide different implementations of foo for different types (and these types are templated). How can I accomplish that? Best, Irek

5 11

Error: no member named 'GetModuleFileNameA' in namespace 'boost::winapi'; did you mean simply 'GetModuleFileNameA'?
by Osman Zakir 31 Dec '18

31 Dec '18

Hi again, everyone. When trying to build Boost 1.69.0 after having placed my installation of Python 3.7.1 above the one of Python 2.7.15, I got the error mentioned in the title of this email. It says at the end, " ...failed updating 4 targets... ...skipped 8 targets... ...updated 2381 targets... " The project-config.jam file I used is attached to this message.

1 0

Errors with 1.69 when compiling with /clr on MSVC
by Stian Zeljko Vrba 30 Dec '18

30 Dec '18

I get the following warning and error when compiling a C++/CLI file that includes boost 1.69. 1>c:\quinesoftwarebase\include\boost\type_traits\detail\is_member_function_pointer_cxx_11.hpp(114): error C2764: 'C': template parameter not used or deducible in partial specialization 'boost::is_member_function_pointer<Ret(Args...)>' 1>c:\quinesoftwarebase\include\boost\type_traits\detail\is_member_function_pointer_cxx_11.hpp(125): warning C4575: '__vectorcall' incompatible with the '/clr' option: converting to '__stdcall' Is there a workaround for this? -- Stian

3 3

Re: [Boost-users] [cfe-dev] [llvm-dev] Error: ISO C++17 does not allow 'register' storage class specifier [-Wregister], when building Boost 1.69.0
by Osman Zakir 25 Dec '18

25 Dec '18

I'll build using C++14 mode, then. I wonder if Python 3.7.1 has this issue as well? If it doesn't, then maybe Boost should switch over to that version of Python. ________________________________ From: Matthieu Brucher <matthieu.brucher(a)gmail.com> Sent: Tuesday, December 25, 2018 2:56 PM To: Oleg Smolsky Cc: Craig Topper; Osman Zakir; clang developer list; cfe-users(a)lists.llvm.org; llvm-dev(a)lists.llvm.org Subject: Re: [cfe-dev] [llvm-dev] Error: ISO C++17 does not allow 'register' storage class specifier [-Wregister], when building Boost 1.69.0 The issue comes in part form the Python headers that have the keyword. Unfortunately, this also means that there is an issue while building user code. But it's not a Boost code issue for this library, but a Python one. Regards, Matthieu Le mar. 25 déc. 2018 à 02:08, Oleg Smolsky via cfe-dev <cfe-dev(a)lists.llvm.org<mailto:cfe-dev@lists.llvm.org>> a écrit : Yes, this keyword is no longer valid starting from C++17: https://en.cppreference.com/w/cpp/keyword/register I realize that the "why" probably doesn't help you move forth with your problem, so here are a couple suggestions how to get over it: * Build Boost in C++14 mode with -std=c++14 * Cut out "register" from the Boost source and rebuild * Try a newer Boost version, it may have been fixed Oleg. On 2018-12-23 09:26, Craig Topper via cfe-dev wrote: This seems a better question for cfe-dev or cfe-users ~Craig On Sat, Dec 22, 2018 at 12:23 PM Osman Zakir via llvm-dev <llvm-dev(a)lists.llvm.org<mailto:llvm-dev@lists.llvm.org>> wrote: When trying to build Boost using LLVM, I had this error: " error: ISO C++17 does not allow 'register' storage class specifier [-Wregister] " I attached the project-config.jam file I used to this message. Someone please help me out (if there's someone on here who can). _______________________________________________ LLVM Developers mailing list llvm-dev(a)lists.llvm.org<mailto:llvm-dev@lists.llvm.org> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev _______________________________________________ cfe-dev mailing list cfe-dev(a)lists.llvm.org<mailto:cfe-dev@lists.llvm.org> http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev _______________________________________________ cfe-dev mailing list cfe-dev(a)lists.llvm.org<mailto:cfe-dev@lists.llvm.org> http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev -- Quantitative analyst, Ph.D. Blog: http://blog.audio-tk.com/ LinkedIn: http://www.linkedin.com/in/matthieubrucher

2 1

Problem downloading 1.69.0 for Windows
by tim＠raisedbar.net 24 Dec '18

24 Dec '18

Hi, Windows Defender is blocking my download from https://www.boost.org/users/history/version_1_69_0.html as it is identified as being unsafe. Can anybody advise, please? Best wishes. Tim Burgess Raised Bar Ltd. E: <mailto:tim@raisedbar.net> tim(a)raisedbar.net M: +44 (0)7989 486976

2 2

[Asio/Beast] Any non-obvious reasons for no bind_executor_and_allocator?
by Sorin Fetche 23 Dec '18

23 Dec '18

Hi, As I'm looking to modernize an older C++03 project based on Boost.Asio to use C++17 and the net TS api, I am not ready yet to give up on using lambdas for completion handlers. Boost.Asio and Boost.Beast have some utilities for correctly implementing asynchronous composed operations but from them only asio::bind_executor seems to be applicable to lambdas. And the problem is that it only associates an executor with a (lambda) object; I didn't find any utility for associating an allocator too. Could there be any reason for a utility that associates both an executor and an allocator with an object to not work correctly when implementing asynchronous operations? Or is it just that this utility has not been implemented yet? I did come across the paper "Networking TS Associations for Call Wrappers"[1], but I didn't see any mention there about bind_executor or something similar for allocators or why this kind of approach wouldn't work. I would be very happy if I could write something like: asio::post( socket_.get_executor(), bind_executor_and_allocator_from( handler_, [...] { self_.handler_(...); })); and, unless I'm missing something, such a utility could be implemented similarly to the existing asio::bind_executor. Thank you, Sorin [1] http://open-std.org/JTC1/SC22/WG21/docs/papers/2018/p1133r0.html

2 7

Update for C++17 register keyword error question
by Osman Zakir 23 Dec '18

23 Dec '18

This is the error I get when trying to build Boost 1.69.0 with LLVM: "error: ISO C++17 does not allow 'register' storage class specifier [-Wregister]". I've also sent an email about this to the LLVM developer mailing list. I've attached the project-config.jam file to this message. Please let me know how to fix this. Thanks in advance.

2 2

[uuid] constexpr uuid from string and ""_uuid literal
by Tobias Loew 23 Dec '18

23 Dec '18

Hi, while searching for constexpr GUID from string generators, I found https://gist.github.com/AlexBAV/b58e92d7632bae5d6f5947be455f796f . Since I still work with VS 2015, I wrote a C++11 constexpr version incl. boost-uuid generators. If there's interest adding this to boost uuid, please have a look at https://github.com/tobias-loew/constexpr-GUID-cpp-11 Tobias -- Sent from: http://boost.2283326.n4.nabble.com/Boost-Users-f2553780.html

2 1

Patch for using boost-1_69_0 and clang-cl
by JR Cary 23 Dec '18

23 Dec '18

I found that I had to apply the attached patch to build another project that uses boost with clang-cl, or else I got an error that complained about the non-existence of std::snprintf. John Cary

2 1