Re:Guide to Implementing Communication Protocols in C++ for ...
by ranit on Tuesday June 12, 2018 @06:26AM
(#17292054)
So, which language or tool would you recommend?
[ Parent
| on HN ]
Re:Guide to Implementing Communication Protocols in C++ for ...
by v_lisivka on Tuesday June 12, 2018 @08:28AM
(#17292596)
Rust looks promising, but it is not ready yet. I use it on iMX6, which is relatively powerful system, but on NRF52 we still use C. Maybe I will use it on NRF52 when support for bare hardware metal will be in stable (working group[1] is working on that).
Re:Guide to Implementing Communication Protocols in C++ for ...
by vardump on Tuesday June 12, 2018 @07:13AM
(#17292238)
Rust looks quite promising.
Currently limited microcontroller architecture support is one of the biggest issues with it.
Rust based RTOS would also be helpful for medium size devices. Of course small devices are fine on bare metal.
Re:Guide to Implementing Communication Protocols in C++ for ...
by v_lisivka on Tuesday June 12, 2018 @08:48AM
(#17292715)
There are some projects, for example [1],[2], but they require nightly compiler, i.e. they cannot be used in production yet.
[1]: https://github.com/tock/tock/blob/master/doc/Getting_Started... [2]: https://github.com/hashmismatch/freertos.rs
Re:Guide to Implementing Communication Protocols in C++ for ...
by iainmerrick on Tuesday June 12, 2018 @09:02AM
(#17292786)
If you don't use Rust yet, what do you use right now?
I would have guessed C or C++. Maybe they're not great for the purpose but they're also just about the only game in town, no?
Re:Guide to Implementing Communication Protocols in C++ for ...
by vardump on Tuesday June 12, 2018 @10:54AM
(#17293784)
Mostly C.
While C++ is easier to write, for very low level code, it is harder to maintain when you need to understand all of the side effects to maintain code safety.
C++ compiler support is also sometimes not available. (And of course it's very like there'll be no Rust compiler available either in this case.)