RE: C++ moving and returning objects part 1: object as return value (embedded friendly C++)

kmikemoo — Sat, 19 Jul 2025 22:20:01 GMT

Good information. [emoticon:1435ff2429184e17bc948e4f19178e1e]

RE: C++ moving and returning objects part 1: object as return value (embedded friendly C++)

DAB — Sat, 19 Jul 2025 18:39:13 GMT

Nice post Jan.

RE: C++ moving and returning objects part 1: object as return value (embedded friendly C++)

Jan Cumps — Sat, 19 Jul 2025 14:15:18 GMT

I'm using this technique sparsely in a GPS parser lib I wrote. Several developers that wanted to use it, challenged performance because I sometimes return an object. This post can help put some context to that question.

What I learned while writing C++ libraries, is that not a lot of people challenge the functionality. Virtual any comment is about the use of C++, STL, ... As if we were in 1998.
While there is a lot to gain for embedded designs. Embedded firmware is close to hardware. It's an excellent candidate for object based designs.
And OO designs come cheap this days. For memory and clock ticks. A lot of times the execution cost is 0 bytes, 0 ticks. But it's expensive for the designer community brain flex ...