Re:The memory safety problem isn't bad coders
by jschwartzi on Tuesday February 12, 2019 @02:03PM
(#19146411)
I try to avoid using STL because it A) throws exceptions, B) has really convoluted type names, and C) dynamically allocates memory. These are all things you avoid in the embedded space.
Re:The memory safety problem isn't bad coders
by maxxxxx on Tuesday February 12, 2019 @02:22PM
(#19146586)
Makes sense for embedded.
Re:The memory safety problem isn't bad coders
by gowld on Tuesday February 12, 2019 @02:51PM
(#19146870)
Any use of templates has the same problem, including templates that are used to generate highly efficient static constants and non-branching-at-runtime code.
for (auto it = s.begin(); it != s.end(); it++) {
is much easier to write than
for (vector<int>::iterator it = s.begin(); it!=s.end(); it++) {