In case you want to know why is Universally unique identifier incredibly useful for you click on that link. UUID and GUID mean the same “thing”.
In case you need little resilient modern C++ compile-time GUID read on.
Continue readingIn case you want to know why is Universally unique identifier incredibly useful for you click on that link. UUID and GUID mean the same “thing”.
In case you need little resilient modern C++ compile-time GUID read on.
Continue readingSimple things are simply the most useful things. But one has to be careful not to make them simpler than that. Continue reading
In case you might be wondering why don’t we “just” use char32_t and get over it once and for all, please see this GODBOLT.
It shows C and/or C++ console output simply does not deal with char32_t and char16_t. When on Linux you use char * which is codead as UTF8 and when on windows you use wchar_t which is coded as UTF16. Thus you have to transform your char32_t / char16_t strings to them frist, depending on which platform you happen to be, then you can use the console subsystem.
The other day, a C++ student approached me on-line, while he researched some tiny framework of mine. In his own words he”bumped into this problem”. For some reason, he still uses Visual Studio 2017 IDE. Annoyingly he had an image, not a source code, to prove the problem. Sigh.
One of those snippets you just copy-paste from SO? Can I please explain to you a few basics before your copy-paste this one? Let’s suppose you have developed for C++17.
As I am also claiming since ages ago, inheritance as a program composition method is evil. There is no reason to use class inheritance. And I am not the inventor of this advice.
What more can we say? Ah yes, please read this little text first. Immediately. Then come back here.