although you should put the variable into a managed pointer on it’s creation to do it from an existing pointer. int *a=new int; boost::shared_ptr<int> a_ptr(a); That said you most definitely do not want to be putting stack variables into shared_ptr BAD THINGS WILL HAPPEN If for some reason a function takes shared_ptr and you only … Read more
Basically your question boils down to “is it reasonable to have [free library xyz] as a dependency for a C++ open source project.” Now consider the following quote from Stroustrup and the answer is really a no-brainer: Without a good library, most interesting tasks are hard to do in C++; but given a good library, … Read more
In general, I don’t find the documentation is that bad. In general again, the information is “somewhere” in there. The main problem I see is a lack of uniformity, making it difficult to find that “somewhere”. As you write in your question, the docs were written by different people, and a different times, and that’s … Read more
boost::variant will heap allocate in order to have part of itself be recursively defined as itself. (It will also heap allocate in a number of other situations, uncertain how many) std::variant will not. std::variant refuses to heap allocate. There is no way to actually have a structure containing a possible variant of itself without a … Read more
Because when I wrote that code, the compiler (clang) had not yet implemented C++11 atomics. And I never got back to it to clean it up. Nothing subtle here. 🙂
You need to install the packages beforehand (using vcpkg install ). (Then you could specify the toolchain as a CMake option: -DCMAKE_TOOLCHAIN_FILE=C:\path\to\vcpkg\scripts\buildsystems\vcpkg.cmake but this won’t work if you already specify a toolchain, such as when cross-compiling.) “include” it, instead, to avoid this problem: Add this line to the project CMakeLists.txt before find_package(): include(/path/to/vcpkg/scripts/buildsystems/vcpkg.cmake)
Nope. But I here is how to clean it up. First, rewrite iterator based functions as ranged based functions. This halves your boilerplate. Second, have them return container builders rather than take insert iterators: this gives you efficient assignment syntax. Third, and probably too far, write them as named operators. The final result is you … Read more
JSON support, is spotty with boost property tree. The property tree dataset is not typed, and does not support arrays as such. Thus, the following JSON / property tree mapping is used: JSON objects are mapped to nodes. Each property is a child node. JSON arrays are mapped to nodes. Each element is a child … Read more
a_class is responsible for creating and destroying b_class instances … a_class instance “survives” b_class instances. Given these two facts, there should be no danger that a b_class instance can attempt to access an a_class instance after the a_class instance has been destroyed as the a_class instance is responsible for destroying the b_class instances. b_class can … Read more
This is the method I followed to install Boost.Log in my Linux box. One important note before you build and install Boost libraries: Make sure you have installed a threading library like pthreads. Most package managers should have them. Here are the build steps: If you have installed Boost already from source, then its fine … Read more