Welcome to the MISRA discussion forum

Dear,

I have to design our new familly product SW platform.

To do this, we have introduce in our design the \"components set\" concept, that gathers components that have the same functionnal behaviour and that are interchangeable.
Let's take the example of a driver: we can have driver1 and driver2 that
are interchangeable, do the same job, and part of the same library. They
present the same interface.
During project instanciation from the SW platform, we choose one of them. To manage this, we plan to have a definition of the include file to avoid modifying a generic component that would call these drivers.

Following the publication of MISRA-C:2004, the subtopics in this forum are now open.

If you have any questions or want to discuss a point about any of the rules in MISRA-C:2004, please post it to the appropriate topic according to the section in the document (e.g. for a question about rule 1.1, post it to forum \"6.1 Environment\").

MISRA-C:2004 \"Guidelines for the use of the C language in critical systems\" has been published.

You can purchase it using a credit or debit card at our new on-line store. Choose \"Buy\" on the MISRA C website, or go directly to http://www.misra.org.uk/buy_now.php

The organisation I work for is about to start a series of new products.

Within the organsiation ( 2 sites) of the 8 embedded software engineers, none has any experience of working to any formal standards etc.

Currently we looking at using PC lint from gimpel ( using the MISRA options lnt file) to help test and verify the code is MISRA compliant.

I must admit is was quite educational to try lint just on its own, on the exsisting products code and has generated quite a bit of reworking of code.

Can anyone suggest a better tool or perhaps a training course etc that may ease the introduction of the MISRA standard into our newer products.

Hi,

I heard that some one was developing a sub/superset of MISRA-C for use in autocode generation tools.

Does anyone know anything about this?
Who is doing it?


Regards
Chris

Hi

I run an unoffical MISRA-C web site at http://www.misra-c.org

As it has no connection with MISRA/MIRA I get to post mosr commercial information and other bits and pices.

Hi

Please note theat MISRA-C2 contains an appendix showing all the mapping from C1 to C2 rules.

Regards

First, good idea to set up the forum, hope it will be frequently visited by engineers working with Misra C. Nice to be one of the first users of the forum :-)

As there is no section specifically dedicated to Misra C:1998 I place my question in the general question section.

What is the intended interpretation of Misra C:1998 rules 104 and 105?

Misra C:1998 rule 104 reads \"Non-constant pointers to functions shall not be used\"
One may interpret this rule as that the only allowed use and declaration of a function pointer is as in the example below

Example:

Hi,

there is an appendix in MISRA-C2 that maps all the C1 rules to theC2 rules. This will enable speedy remapping of development processes.

Can anyone identify the place in the cover of MISRA-C2?

We it was better than \"this is a test \" :-)