2 ms·
Anything POSIX should do, no? Anyway, I still think the point stands: many lower level targets do not have C++ or Rust compilers, but do have okay-ish C compi
by throwawayEmb 3y ago
Anything POSIX should do, no?
Anyway, I still think the point stands: many lower level targets do not have C++ or Rust compilers, but do have okay-ish C compilers.
You replied to
> I can think of several embedded platforms where Rust or C++ is not even an option.
… asking “Go on, name a few”. I understood this as “name a few targets for which C++ and/or Rust is unavailable”.
These targets do exist and are perhaps more common than you assume. In my own experience, it is mostly seen with small micros though.
But perhaps I misunderstood you?
- glonq 3y agoyour point does stand. ignore the trolls.
- omeid2 3y agoContext is everything. Bringing up STM8 in the context of libwebsockets is as relevant as bringing up PLCs, not at all. Of course there will always platforms where C remains the only option because honestly, C is just quasi-portable glorified asm; but the point is that if you have the luxury of a platform that can run Libwebsockets, you're most likely in a position to use C++ or Rust, or some other safe language. That is the point.
- throwawayEmb 3y agoI was replying to this > Genuine question. With Rust and C++, even for embedded systems, what is the use case for starting a new project that does binary encoding and network with such an unsafe language like C? And I gave a genuine answer :) If you want to restrict the context to libwebsockets, I suggest you edit your question to clarify that. Network code != libwebsockets. I have written Ethernet-connected firmware without OS/RTOS on 8-32 bit MCUs that definitely would not be able to run libwebsocket. There is a big world in embedded between PLCs and e.g. RasPi. That is often where you use C (in my experience).