rspec/rules/S881/comments-and-links.adoc

=== deprecates: S1454

=== on 7 Jan 2014, 11:36:12 Freddy Mallet wrote:
Implemented by \http://jira.codehaus.org/browse/SONARPLUGINS-3374 for JavaScript

=== on 23 Feb 2014, 22:52:53 Freddy Mallet wrote:
Is implemented by \http://jira.codehaus.org/browse/SONARPLUGINS-3506 for PHP

=== on 22 Apr 2015, 13:29:07 Evgeny Mandrikov wrote:
\[~ann.campbell.2] how this relates to MISRA C:2004, 13.3 - "Floating-point expressions shall not be tested for equality or inequality" ? is it a typo and some other reference should be placed instead?

=== on 23 Apr 2015, 10:07:22 Ann Campbell wrote:
It looks like the original reference was to 2012:13.3, & 2004:13.3 introduced in error during edits

=== on 26 Feb 2018, 16:11:36 Alban Auzeill wrote:
Irrelevant for "go" because the increment and decrement operators are statements and not expressions (to prevent issues related to this rule).


See \https://golang.org/ref/spec#IncDec_statements 

=== on 3 Oct 2019, 11:14:22 Lex Mourek wrote:
I think it is irrelevant in JavaScript (and Typescript) too. ECMAScript clearly states that expressions are evaluated let-to-right one at a time (if you would like it in C terminology - side effects are applied immediately one at a time) 12.4.4 http://www.ecma-international.org/publications/files/ECMA-ST/ECMA-262.pdf


There is no "undefined states" of expression evaluation in JavaScript like in C language. Also referring to Clang coding style standards in Javascript/Typescript rule is quite odd. Overall rule documentation is weak and usage is disturbing. Can you remove it please?