13-12-2012, 11:49 AM
Hi,
I missed discussion about new Misra C to be released.
Anyway now and then I have several questions and comments about dynamic memory allocation.
In Misra C 2004 there is only one rule (20.4) addressing dynamic memory allocation.
In my opinion it's too little. There are questions not answered by this single rule.
So the questions are:
1. Is this rule only forbiding use of malloc, calloc, realloc and free functions while leaving a room for implementation and use of prorpietary functions?
2. Is proprietary dynamic memory management allowed in any way?
3. I would like to implement my own "heap" (pool) which would allow for memory allocation on startup only and no deallocation anytime. Is this possible without violation of this rule?
In my opinion these questions should be answered in new Misra in some clearer way.
Best regards,
Szymon
I missed discussion about new Misra C to be released.
Anyway now and then I have several questions and comments about dynamic memory allocation.
In Misra C 2004 there is only one rule (20.4) addressing dynamic memory allocation.
In my opinion it's too little. There are questions not answered by this single rule.
So the questions are:
1. Is this rule only forbiding use of malloc, calloc, realloc and free functions while leaving a room for implementation and use of prorpietary functions?
2. Is proprietary dynamic memory management allowed in any way?
3. I would like to implement my own "heap" (pool) which would allow for memory allocation on startup only and no deallocation anytime. Is this possible without violation of this rule?
In my opinion these questions should be answered in new Misra in some clearer way.
Best regards,
Szymon
<t></t>