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/class-wp-user-query.php

    r37360 r37431  
    737737
    738738    /**
    739      * Make private properties readable for backwards compatibility.
     739     * Make private properties readable for backward compatibility.
    740740     *
    741741     * @since 4.0.0
     
    752752
    753753    /**
    754      * Make private properties settable for backwards compatibility.
     754     * Make private properties settable for backward compatibility.
    755755     *
    756756     * @since 4.0.0
     
    768768
    769769    /**
    770      * Make private properties checkable for backwards compatibility.
     770     * Make private properties checkable for backward compatibility.
    771771     *
    772772     * @since 4.0.0
     
    783783
    784784    /**
    785      * Make private properties un-settable for backwards compatibility.
     785     * Make private properties un-settable for backward compatibility.
    786786     *
    787787     * @since 4.0.0
     
    797797
    798798    /**
    799      * Make private/protected methods readable for backwards compatibility.
     799     * Make private/protected methods readable for backward compatibility.
    800800     *
    801801     * @since 4.0.0
Note: See TracChangeset for help on using the changeset viewer.