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/cache.php

    r37216 r37431  
    345345
    346346    /**
    347      * Makes private properties readable for backwards compatibility.
     347     * Makes private properties readable for backward compatibility.
    348348     *
    349349     * @since 4.0.0
     
    358358
    359359    /**
    360      * Makes private properties settable for backwards compatibility.
     360     * Makes private properties settable for backward compatibility.
    361361     *
    362362     * @since 4.0.0
     
    372372
    373373    /**
    374      * Makes private properties checkable for backwards compatibility.
     374     * Makes private properties checkable for backward compatibility.
    375375     *
    376376     * @since 4.0.0
     
    385385
    386386    /**
    387      * Makes private properties un-settable for backwards compatibility.
     387     * Makes private properties un-settable for backward compatibility.
    388388     *
    389389     * @since 4.0.0
Note: See TracChangeset for help on using the changeset viewer.