writing a MISRA-C:2004 tutorial

[phaedsys]

What means \"TC\"?

Technical Corrigendum

This is something like an errata or additional techical comments. It will contain clarifications from both questions asked here and anything else the team find whilst doing the example suite.

The document I want to write is for a diploma thesis, which I work on in a company in germany. It should be a help for the software engineers here, who work with MISRA-C.

You may write anything you like for a diploma or internal company documentation.

I write it down in german, for very easy understanding.

Only in Germany :-) I think there is a German version of MISRA C somwhere.

I can't wait for any new documents of MISRA, like TC or the example suite, because I want to complete my diploma thesis. So I think, I must do it by myself.

Then anything you write may be out of date before you finish it. We expect to have the first version of the TC in a few months.

However this is the same with ANY book or guide on any programming language. C, C++, C# etc are all developing and changing for C and C++ thare are lots of defect reports and small changes all the time. There have been major updates to both C and C++ inthe last couple of years. Yet there are many books on C , C++ etc

I think there is no way for a student to get access to the work of the helping documents the MISRA team is working on? Perhaps I could be of help with ideas and making examples, because I do the same things and do it together with the software engineers in my company

The MISRA team is a closed, stable and mature team and has developed a good way of working. It has a wide range of expertise. It can work faster by limiting the size of the team. Larger teams tend to work a lot slower.

It is unlikely that any documents would be released early to anyone except at review points. These reviews are controled and you could not publish information in them . Also things change due to the feed back.

The problem is that things change during development. Even if you did have access I do not think you would not be able to publish anything before the MISRA team does. Also the MISRA teams (and reviewers) are bound by contract to stop early release of thigs that might change or be taken out of context.

Now I am a little bit disappointed. I wanted to write gladly a diploma thesis, which will be practically used when it is done. But if a few months later MISRAs own helping documents appear, my work perhaps is in vain. If it is possibile to help at the development of the documents, I would be grateful for your information.
best regards,Manni

You can still write a diploma thesis on MISRA C. A thesis is, of course, a snapshot at a single point in time. You can also ask questions here and get answers.

You can also write a company document based on MISRA C. Many people do write company guidelines based on MISRA C. That is the whole idea. For company guidelines you have to take a view on how often you want to update them.

There are companies still using MISRA C:1998 this is because they do not want to change mid project and often the tools they have only support MISRA C:1998.


These views are entirley my own and not those of the MISRA C team, MISRA or MIRA. I wil probably be told I have got it all wrong at the mext meeting!

Remember I was the one who said no MISRA C++ in my life time :-)