SergeyBiryukov 54e1b4b959 Coding Standards: Use pre-increment/decrement for stand-alone statements. ... Note: This is enforced by WPCS 3.0.0: 1. There should be no space between an increment/decrement operator and the variable it applies to. 2. Pre-increment/decrement should be favoured over post-increment/decrement for stand-alone statements. “Pre” will in/decrement and then return, “post” will return and then in/decrement. Using the “pre” version is slightly more performant and can prevent future bugs when code gets moved around. References: * [https://developer.wordpress.org/coding-standards/wordpress-coding-standards/php/#increment-decrement-operators WordPress PHP Coding Standards: Increment/decrement operators] * [https://github.com/WordPress/WordPress-Coding-Standards/pull/2130 WPCS: PR #2130 Core: add sniffs to check formatting of increment/decrement operators] Props jrf. See #59161, #58831. git-svn-id: https://develop.svn.wordpress.org/trunk@56549 602fd350-edb4-49c9-b593-d223f7449a82		2023-09-09 09:26:01 +00:00
..
base.php	Coding Standards: Use pre-increment/decrement for stand-alone statements.	2023-09-09 09:26:01 +00:00
import.php	Tests: Replace some occurrences of assertEquals() with assertSame().	2022-10-07 01:02:07 +00:00
parser.php	Coding Standards: Always use parentheses when instantiating an object.	2022-11-29 15:49:49 +00:00
postmeta.php	Tests: Replace some occurrences of assertEquals() with assertSame().	2022-10-07 01:02:07 +00:00