Re:Mbeddr – engineering the future of embedded software
by ArkyBeagle on Saturday September 13, 2014 @04:29PM
(#8313462)
'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.
*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.