3 ms·

I think you missed exceptions often being a problem in low level and embedded targets. That knocks out most of STL anyway. I also think you are a bit harsh on

by ska 3y ago

I think you missed exceptions often being a problem in low level and embedded targets. That knocks out most of STL anyway. I also think you are a bit harsh on virtual functions - it introduces a single indirection, yes, but sometimes that is fully justified. RTTI on the other hand... of course depends a bit on target characteristics. Perhaps controversial, I've also found (especially bare) lambdas and even std::function objects useful, although may evolve into something purely static when the dust settled. Highly dependent on target of course. It will be interesting to see the final form of the new MISRA std, since the active one predates all of this.

corysama 3y ago
If you can't use the STL because of exceptions: https://www.etlcpp.com/ https://www.etlcpp.com/
- ska 3y ago
  Sure, there are more embedded friendly libraries, but that wasn't the topic.
  - cjaybo 3y ago
    It’s almost as if this is some sort of discussion board where people can expand on the topic as they see fit :D
vodou 3y ago
You can use quite a lot of STL even with -fno-exceptions. Things that you probably need to ditch are: std::vector std::list std::map std::unordered_map std::set std::unordered_set std::sort std::transform std::merge std::string std::regex std::swap std::function std::stable_partition But there are much more than that in STL.
- ska 3y ago
  True: "most" was a stretch.
- synergy20 3y ago
  most (useful) containers are out, what else are left in STL for embedded systems, algorithms?
deleted 3y ago
[deleted]
synergy20 3y ago
newest MISRA for c++ just came out, though it's based on c++17