Vitenskap

Prohibition of Imposing MISRA Compliance in Coding Standards

Kampanjer er ikke offentlig
Kampanje tas opp
Covent Garden; Place Charles Rogier/Charles Rogierplein 16; Belgique/België
7 Støttende 7 inn Den europeiske union

Ansvarlig har ikke sendt inn kampanjen

7 Støttende 7 inn Den europeiske union

Ansvarlig har ikke sendt inn kampanjen

  1. Startet 2016
  2. Innsamling ferdig
  3. Sendt inn
  4. Dialog
  5. Mislyktes

12.10.2018, 02:11

Liebe Unterstützende,
der Petent oder die Petentin hat innerhalb der letzten 12 Monate nach Ende der Unterschriftensammlung keine Neuigkeiten erstellt und den Status nicht geändert. openPetition geht davon aus, dass die Petition nicht eingereicht oder übergeben wurde.

Wir bedanken uns herzlich für Ihr Engagement und die Unterstützung,
Ihr openPetition-Team


21.07.2016, 11:04

Fixed typo.


Neue Begründung: The original goal of MISRA was to improve code quality by means of static code checking. That is, code is judged without any level of reflection. The fact is, that human written code can hardly be judged without reflection. Furthermore, the overwhelmingly strict standards tend to add a huge amount of visual noise into code that is otherwise safe and sound. Changes done to code due to MISRA tend to introduce new, hard to find errors.
On the other hand, MISRA compliance is often required by the uniformed uninformed management league that needs some type of quantifiable data. Requiring MISRA, though, causes a huge amount of extra work to be done with a value add that is at best zero.
Prohibiting the imposition of MISRA helps to avoid the negative impact of this standard on the European Software Industry. Today, there are much more sophisticated means to ensure code quality, such as Unit Tests and tools that reflect on code. There is no need for MISRA.





Bidra til å styrke innbyggermedvirkning. Vi ønsker å gjøre dine bekymringer hørt samtidig som vi forblir uavhengige.

Markedsfør nå