WordPress.org

Make WordPress Core


Ignore:
Timestamp:
05/13/2016 06:40:19 PM (5 years ago)
Author:
DrewAPicture
Message:

Docs: Standardize on 'backward compatibility/compatible' nomenclature in core inline docs.

Also use 'back-compat' in some inline comments where backward compatibility is the subject and shorthand feels more natural.

Note: 'backwards compatibility/compatibile' can also be considered correct, though it's primary seen in regular use in British English.

Props ocean90.
Fixes #36835.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/src/wp-includes/wp-diff.php

    r34348 r37431  
    459459
    460460    /**
    461      * Make private properties readable for backwards compatibility.
     461     * Make private properties readable for backward compatibility.
    462462     *
    463463     * @since 4.0.0
     
    474474
    475475    /**
    476      * Make private properties settable for backwards compatibility.
     476     * Make private properties settable for backward compatibility.
    477477     *
    478478     * @since 4.0.0
     
    490490
    491491    /**
    492      * Make private properties checkable for backwards compatibility.
     492     * Make private properties checkable for backward compatibility.
    493493     *
    494494     * @since 4.0.0
     
    505505
    506506    /**
    507      * Make private properties un-settable for backwards compatibility.
     507     * Make private properties un-settable for backward compatibility.
    508508     *
    509509     * @since 4.0.0
Note: See TracChangeset for help on using the changeset viewer.