Should #17-0-2 include any non-function identifier? - Printable Version +- MISRA Discussion Forums (https://forum.misra.org.uk) +-- Forum: MISRA C++ (https://forum.misra.org.uk/forumdisplay.php?fid=18) +--- Forum: MISRA C++:2008 rules (https://forum.misra.org.uk/forumdisplay.php?fid=19) +---- Forum: 6.17 Library introduction (C++) (https://forum.misra.org.uk/forumdisplay.php?fid=145) +---- Thread: Should #17-0-2 include any non-function identifier? (/showthread.php?tid=717) |
Should #17-0-2 include any non-function identifier? - gs - 16-03-2010 A discussion of a similar rule for MISRA C concluded the rule was meant to encompass any reserved identifier. While MISRA C++ has excluded functions from this rule and placed their consideration under rule #17-0-3, no mention of standard types (e.g, clock_t) or any other non-function identifier is made as far as I can tell. Should the rule include these also? Re: Should #17-0-2 include any non-function identifier? - misra cpp - 07-10-2015 The changes to the wording in MISRA C will be reviewed for inclusion in a future version of MISRA C++. |