Disclosure: On this site you won’t find specific advice on “how to call function xyz()”. Interpreting C++ ARM and #pragma dwim is also out of scope.
We’re treating our readers as intelligent beings who can use Google and/or StackOverflow, where all such specific questions were answered more than once.
What you will find is opinions, more opinions, and even more opinions on all the aspects of software development - and with a large chunk of them based on real-world experience too.
Your mileage may vary. Batteries not included.
App-level Developer on std::error Exceptions Proposal for C++. Part I. The Good
May 23, 2018 by • “No Bugs” Bunny
Quote:
No single error handling method is good enough for ALL the projects – which in turn leads to segmentation, with some of the projects using exceptions, and some others using error codes
Another Quote:
Right above I said that I like the std::error exception proposal a.k.a.[P0709R0]. However, as soon as I look at competing proposals, I begin to love it.
Filed under: On.ProgrammingProgramming Languages
C++: On Using int*_t as Overload and Template Parameters
May 14, 2018 by • “No Bugs” Bunny
Quote:
We decide which set of types we’re using (fundamental or int*_t), and use it consistently
Another Quote:
The only thing we’re doing here, is changing the name of the type, NOT its behavior
Filed under: On.ProgrammingTips and TricksProgramming Languages
Quick Update on C++ Compiler Bug Hunt (overall, 15 bugs reported, 8 already fixed)
May 8, 2018 by • “No Bugs” Bunny
Some time ago, I wrote a post about kscope – mini-project on finding and reporting bugs in modern C++ compilers. The point was that there is a way to use C++ facilities to make C++ code self-mutating (more strictly – pseudo-randomized using externally supplied ITHARE_KSCOPE_SEED macro), which allows finding certain classes of bugs during randomized […]
‘Speedy Gonzales’ Serializing (Re)Actors via Allocators
May 1, 2018 by • “No Bugs” Bunny
Quote:
Allocator-based serialization for (Re)Actors is extremely fast (for x64 – around tens of ms per 100MB of state)
Another Quote:
Per-(Re)Actor allocators can be implemented without any changes within (Re)Actor itself (i.e. all the necessary changes can be confined to Infrastructure Code).
Filed under: On.ProgrammingProgramming LanguagesOptimizations
Read more
