6 ms·
The JSF (joint strike fighter) C++ coding standards are also a good starting point http://www.jsf.mil/downloads/down_documentation.htm http://www.jsf.mil/downl
by excuse-me 14y ago
The JSF (joint strike fighter) C++ coding standards are also a good starting point
http://www.jsf.mil/downloads/down_documentation.htm http://www.jsf.mil/downloads/down_documentation.htm
They are a bit heavy handed on "thou shalt not" - but if you use them as guide - and really think if breaking a rule is worth it in a specific case - they are good conservative practice.
- deleted 14y ago[deleted]
- excuse-me 14y agoConservative can also mean use #define, macros and casts rather than those new fangled templates ;-) IIRC the guidelines are a reasonable compromise between recommending new 'safe' but relatively unfamiliar and tricky constructs - and sensible advice to avoid #define and macros. There are often other constraints in real time and safety critical systems - like avoiding allocations and exceptions. But these docs aren't specific avionics rules, there is an awful lot of code in a project like this that never gets onboard the airframe.