3 ms·
Yes that's basically what I found too. To practice OOP, its approach is every class should be a "library". Procedural code that doesn't have a class context i
by letstrynvm 8y ago
Yes that's basically what I found too.
To practice OOP, its approach is every class should be a "library". Procedural code that doesn't have a class context is felt to be a shameful throwback to an earlier era degenerate C practices. From before some people feel they starting writing "good C++" apparently.
- Gibbon1 8y agoI think having done hardware first gives me a slightly different perspective. Hardware designs get reused a lot, but usually not as a drop in, it gets reworked at each reiteration. Either that are it's something you buy off the shelf in which case the design interface is absolutely stable. Think a uP chip or core. They'll fix bugs and shrink the die, but they never ever change the abstract design. You can still by 8051 cores and IC's and that design has not changed at all in 40 years. Compare with business logic. The problem is the spec and use case keeps moving. Moving way too fast to be a good library or a framework.