2 ms·
It's all C. It is all syntactic sugar on top of C so if at the end of the day you want to go back to C then just compile it down and take it from there. Your c
by dkarapetyan 12y ago
It's all C. It is all syntactic sugar on top of C so if at the end of the day you want to go back to C then just compile it down and take it from there.
Your comment reminds me what people were saying when assemblers were first developed. Real programmers did not use assemblers because it was too high level or too far removed from the hardware or any number of other excuses. The fact is that plain C is inadequate for delivering correct software in high assurance environments. This tool addresses that problem and then some.
- ArkyBeagle 12y ago'C' is perfectly adequate for delivering safe and correct* code. Just because it's possible to have 'C' code that is unsafe is not a blanket indictment of the language. Micheal Barr, the MISRA team, Valgrind all exist to aid and abet delivery of safe and correct systems. *whatever that means in context... As we say - "doctor, doctor it hurts when I do that!" "Well, don't do that!" Tools like this simply automate or add leverage to that process. And unless there's considerable community support for the use of something like this, it'll remain a smaller thing than raw 'C'. But many embedded projects are small enough that there's little pain in reinventing the wheel.
- errordeveloper 12y agoI'm sure one can use any libraries/SDKs from Mbeddr, right? And my other impression is that the aim is not to support boards or chips at all, it's just a tool, in my understanding. Are there plans to support C++?