4 ms·
To be fair, there is often some sort of limited version of the std lib available even for those (for example by the MCU manufacturer).
by duozerk 10y ago
To be fair, there is often some sort of limited version of the std lib available even for those (for example by the MCU manufacturer).
- LionessLover 10y ago"Availability" doesn't mean much. There are plenty of all kinds of libs available on all platforms (who wants to program WiFi access for the embedded sensor from scratch, for example?). Doesn't mean it makes sense to put any of them into the current project. The stdlib is one of many and not that often the one that is put in. The libs I use on my embedded system are much more likely to be for some specific piece of sensor or I/O device (like the mentioned WiFi module), I rarely have need for what's in the stdlib. Of course, embedded systems vary far more than the PC and server stuff so you can easily find people who will say the exact opposite.
- jotux 10y ago>I rarely have need for what's in the stdlib It has been my experience that people who don't know or use the C stdlib end up unknowingly re-implementing stdlib functions over and over again.
- marssaxman 10y agoA freestanding C implementation doesn't have to include anything but a handful of headers with some macro and type definitions. It's not uncommon to get a manufacturer-specific library whose features are specific to the particular controller architecture, not related to those defined in the full C library. And it's not uncommon for embedded software developers to ignore those libraries, which are frequently terrible, and write everything from scratch.