Context

Previously, comparing C++Builder classic and Clang compilers I regreted than CodeGuard tool doesn't work with Clang. Fortunately, there are other tools which can help you to profile program code and detect memory leaks. The Dataleaker is the one of these tools.

According to specification, "...constructor is a special non-static member function of a class that is used to initialize objects of its class type". In addition to basic concepts, C++11 introduces move constructors, initializer list type and brace-enclosed lists of comma-separated initializers.

Motivation

C++11 has introduced the move semantic which can also be used in containers instead of "old-school" pointers. The specific containers owning objects has been proposed earlier by third-party libraries like Boost (for example, ptr_map or ptr_vector).

The small test program shows how I/O operations (memory and file) can be accelerated using multiple threads.

Pro et contra

I use C++Builder 10.1 (Berlin) that proposes both 'classic' bcc32 compiler and new clang bcc32c. Whether do you rather to use classic compiler or to switch to clang? The answer is not quite simple.

The advantages of new clang compiler: