27-04-2006, 01:29 PM
You must avoid undefined behaviour, you must not rely on unspecified behaviour, and you must document implementation defined behaviour.
Many library functions contain instances of such behaviour. Where possible, additional measures should be used to avoid the risk of reliance on such behaviour. Deviations should document such use.
fopen() could be used with an appropriate deviation to rule 20.9.
open() could be used with an appropriate deviation to rule 3.6.
Many library functions contain instances of such behaviour. Where possible, additional measures should be used to avoid the risk of reliance on such behaviour. Deviations should document such use.
fopen() could be used with an appropriate deviation to rule 20.9.
open() could be used with an appropriate deviation to rule 3.6.
Posted by and on behalf of the MISRA C Working Group