Software Hardware Architecture — Feasible Speculations
Value Handle to Avoid Implicit Conversions in standard C++
“… C++ is not a bad language per se. It’s just, well kinda suffers from bloat. In the words of Richard E. Gooch, “It seduces the programmer, making it much easier to write bloatware“…”
The source
The Introduction“…There are issues such as dynamic memory allocation in C/C++, which is forbidden, under the DO-178B standard, in safety-critical embedded avionics code…”
The source
Before knowing the above, the other day I have developed a handy little template to hold and provide, a plain 2d array, completely on the stack (aka the “matrix”).
It is also fully “compile time capable” with the full static internal presentation.
It is very handy to gently enforce company-wide C++ policies and to give some useful functionality in return. I am calling this approach “almost a pod”. Continue reading “Simple matrix for the rest of us”
Interface inheritance is good.
Just stumbled upon this excellent and succinct short text on how not to use inheritance. In C++ in particular, and I am adding: in general.
That text is precisely about differences v.s. the Objective-C, but it is priceless if and when you spot the growth of the weed of inheritance. Continue reading “C++ Inheritance easily grows out of control”
As I am also claiming since ages ago, inheritance as (class or component) 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.
In case you need it, here is one very relevant use case, for proving the dynamic dll loading usability. Windows dll’s versions. Continue reading “C++ Why loading Windows DLL at runtime?”
