Throwing an exception out of a destructor is dangerous. If another exception is already propagating the application will terminate. #include <iostream> class Bad { public: // Added the noexcept(false) so the code keeps its original meaning. // Post C++11 destructors are by default `noexcept(true)` and // this will (by default) call terminate if an exception … Read more
In C++ operators (for POD types) always act on objects of the same type. Thus if they are not the same one will be promoted to match the other. The type of the result of the operation is the same as operands (after conversion). if: either is long double other is promoted > long double … Read more
The general consensus is that you do not (should not) need to dispose of HttpClient. Many people who are intimately involved in the way it works have stated this. See Darrel Miller’s blog post and a related SO post: HttpClient crawling results in memory leak for reference. I’d also strongly suggest that you read the … Read more
A simple (and perhaps overused) example of RAII is a File class. Without RAII, the code might look something like this: File file(“/path/to/file”); // Do stuff with file file.close(); In other words, we must make sure that we close the file once we’ve finished with it. This has two drawbacks – firstly, wherever we use … Read more
Given a choice between the solution advocated by IServiceOriented.com and the solution advocated by David Barret’s blog, I prefer the simplicity offered by overriding the client’s Dispose() method. This allows me to continue to use the using() statement as one would expect with a disposable object. However, as @Brian pointed out, this solution contains a … Read more
This cheat sheet provides a pretty good summary of the different containers. See the flowchart at the bottom as a guide on which to use in different usage scenarios: Created by David Moore and licensed CC BY-SA 3.0
When you want to treat lambda expressions as expression trees and look inside them instead of executing them. For example, LINQ to SQL gets the expression and converts it to the equivalent SQL statement and submits it to server (rather than executing the lambda). Conceptually, Expression<Func<T>> is completely different from Func<T>. Func<T> denotes a delegate … Read more
A dangling pointer is a pointer that points to invalid data or to data which is not valid anymore, for example: Class *object = new Class(); Class *object2 = object; delete object; object = nullptr; // now object2 points to something which is not valid anymore This can occur even in stack allocated objects: Object … Read more
You can use this-> to make clear that you are referring to a member of the class: void Bar<T>::BarFunc () { std::cout << this->_foo_arg << std::endl; } Alternatively you can also use “using” in the method: void Bar<T>::BarFunc () { using Bar<T>::_foo_arg; // Might not work in g++, IIRC std::cout << _foo_arg << std::endl; } … Read more
I saw Veer’s answer. I think it’s right, but it did not I work for me. Maybe I am using .NET 4 and am using 64x OS so kindly check this. You may put in setup or check it in start-up of your application: private void Form1_Load(object sender, EventArgs e) { var appName = Process.GetCurrentProcess().ProcessName … Read more