Rule 2-5-1 - 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.2 Lexical conventions (C++) (https://forum.misra.org.uk/forumdisplay.php?fid=131) +---- Thread: Rule 2-5-1 (/showthread.php?tid=1374) |
Rule 2-5-1 - ogawa.kiyoshi - 01-10-2017 I feel, the sentence "The use of digraphs may not meet developer expectations." is not clear. The usage of digraphs are only system constraints. Digraph are just an alternative method for a systems that can not input '{','}','[',']'. Therefore, there is no point in leaving a digraph in the final source file. Even if anyone use a system that requires digraphs, it is better to replace in the final source file from digraph(alternative token) to primary token. Re: Rule 2-5-1 - misra cpp - 05-10-2017 We take your point that if you are developing with diagraphs, you probably know what to expect. It may be more accurate to say '… may not meet maintainers' expectations'. We will review for the next release |