Welcome to the MISRA discussion forum

Does Rule 7.1, \"No octal constants (other than zero) and octal escape sequences shall not be used,\" permit the use of the null character, '\\0'? The normative and rule text exempt 0, per se, but make no mention about '\\0'. Prohibitting '\\0' runs, IMHO, contrary to the Principle of Least Surprise. Perhaps someone would show such kindness as to provide me with some clarity?

I appreciate your time in advance.

I was looking through the MISRA 2 Standard and was wondering what the underlying type of an expression is involving mixed types. For example suppose we are given the following variables:
int i1, i2, *ip;
unsigned char uc;
float f;
What is the underlying type of:
i1 | uc;
i2 ? i1 : uc;
&i1;
ip;
( i1 == i2 );
f;
Since the Standard goes into such detail regarding the concept of \"underlying type\", I feel this is an important issue which, to me, requires clarification.

Hi,

I have a few queries with respect to \"dynamic memory allocation\". As per the rule we are not supposed to use functions like \"malloc()\", \"free()\", \"calloc()\" etc. But malloc() is a very common requirement. Most of the embedded system applications use their own application level memory managers so as to make the allocation and de-allocation fast. Do you have any suggestions to get around this problem ( if we can't use malloc, any other way )?

One possible solution I can think of right now it to do a static allocation of a big chunk of memory and redirecting all the dynamic memory requirements to that chunk ( basically a kind of memory manager ). But here also we are stuck with one problem. If we write an application level memory manager, it has to cater to all data types. This will require conversion from any data type to \"void*\" and from \"void*\" to any data type ( say \"char*\" ). But Rule No: 45 of MISRA C ( Typecasting from any type to or from pointers shall not be used ) prohibits me doing that also.

The third problem is with writing portable code. Its quite common to use codes like (X*)0->data1 to get the offset to data1 , where X is a structure ( struct X { }; ) and data1 is a member within that structure. Are we not supposed to use these types of casts too [ (X*)0 ] ???

It would be great if someone could give some possible solutions to these kind of issues.

- Thanks
- Raveendran V.

Hi,

I'd like to know how the corporate PDF Version of the Misra Rules can be used.
How many people can use it at all and at the same time, does it work like a \"floating license\" ?

Thanks,

Erik

Copies of the presentation material from the recent MISRA C technical forum, held on 14 October 2004, are now available.

Visit the \"Resources\" section of the MISRA C website to find them.

Will these be made available?

If so where and when?

Best Regards

Andrzej

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.