Make WordPress Core


Ignore:
Timestamp:
09/09/2023 09:26:01 AM (8 months ago)
Author:
SergeyBiryukov
Message:

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:

Props jrf.
See #59161, #58831.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/src/wp-includes/html-api/class-wp-html-tag-processor.php

    r56301 r56549  
    952952            if ( '/' === $this->html[ $at + 1 ] ) {
    953953                $this->is_closing_tag = true;
    954                 $at++;
     954                ++$at;
    955955            } else {
    956956                $this->is_closing_tag = false;
     
    10211021                     * See https://html.spec.whatwg.org/#parse-error-incorrectly-closed-comment
    10221022                     */
    1023                     $closer_at--; // Pre-increment inside condition below reduces risk of accidental infinite looping.
     1023                    --$closer_at; // Pre-increment inside condition below reduces risk of accidental infinite looping.
    10241024                    while ( ++$closer_at < strlen( $html ) ) {
    10251025                        $closer_at = strpos( $html, '--', $closer_at );
     
    11021102             */
    11031103            if ( '>' === $html[ $at + 1 ] ) {
    1104                 $at++;
     1104                ++$at;
    11051105                continue;
    11061106            }
Note: See TracChangeset for help on using the changeset viewer.