Timeline for MISRA C 2012 violation of rule 9.1 even with an initialized variable
Current License: CC BY-SA 3.0
Post Revisions
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 18, 2017 at 11:44 | vote | accept | Salim | ||
| Dec 14, 2017 at 15:47 | comment | added | chux |
Detail: "I am initializing var2 in ... function "func" ". C describes this as assigning the elements of var2. To initialize var2, use uint64_t var4[10] = { something }; Anything after that is assignment.
|
|
| Dec 14, 2017 at 11:58 | comment | added | Lundin | Specifically, the return type of main() is nowadays explicitly excluded from the MISRA-C directive that requires that types like those of stdint.h should be used. | |
| Dec 14, 2017 at 11:34 | comment | added | user3629249 | read rule sets to learn about 'rule sets' and how to manipulate them. | |
| Dec 14, 2017 at 11:23 | comment | added | user3629249 |
the function: main() is special in C, do not prototype it. use a return type of int,
|
|
| Dec 14, 2017 at 10:49 | comment | added | Lundin | Out of curiousity, which tool gave the warning? I think I have yet to find one which doesn't have this bug. | |
| Dec 14, 2017 at 10:43 | answer | added | Lundin | timeline score: 5 | |
| Dec 14, 2017 at 10:43 | comment | added | Stargateur |
Is var3 or var5 initialized ? Is var5[i] initialized ? Obviously no, so this doesn't violate the rule.
|
|
| Dec 14, 2017 at 10:38 | history | edited | Salim | CC BY-SA 3.0 |
added 111 characters in body
|
| Dec 14, 2017 at 10:31 | history | asked | Salim | CC BY-SA 3.0 |