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

    r37114 r37431  
    20622062function wp_specialchars( $string, $quote_style = ENT_NOQUOTES, $charset = false, $double_encode = false ) {
    20632063    _deprecated_function( __FUNCTION__, '2.8', 'esc_html()' );
    2064     if ( func_num_args() > 1 ) { // Maintain backwards compat for people passing additional args
     2064    if ( func_num_args() > 1 ) { // Maintain back-compat for people passing additional arguments.
    20652065        $args = func_get_args();
    20662066        return call_user_func_array( '_wp_specialchars', $args );
     
    20862086
    20872087/**
    2088  * Register widget for sidebar with backwards compatibility.
     2088 * Register widget for sidebar with backward compatibility.
    20892089 *
    20902090 * Allows $name to be an array that accepts either three elements to grab the
     
    20922092 * the array for the name.
    20932093 *
    2094  * Passes to {@link wp_register_sidebar_widget()} after argument list and
    2095  * backwards compatibility is complete.
     2094 * Passes to wp_register_sidebar_widget() after argument list and backward
     2095 * compatibility is complete.
    20962096 *
    20972097 * @since 2.2.0
Note: See TracChangeset for help on using the changeset viewer.