For compatibility and reusability of your code, PSR1 recommends that a file should introduce either new symbols (like classes, functions, etc.) or have side-effects (like outputting something, or including other files), but not both at the same time. The first symbol is defined on line 19 and the first side effect is on line 8.
The PSR-1: Basic Coding Standard recommends that a file should either introduce
new symbols, that is classes, functions, constants or similar, or have side effects.
Side effects are anything that executes logic, like for example printing output,
changing ini settings or writing to a file.
The idea behind this recommendation is that merely auto-loading a class should not change the state
of an application. It also promotes a cleaner style of programming and makes your code
less prone to errors, because the logic is not spread out all over the place.
To learn more about the PSR-1, please see the PHP-FIG site on the
PSR-1.
Loading history...
2
/**
3
* Autoloader.
4
*/
5
6
// Bail if WordPress isn't loaded.
7
if ( ! defined( 'WPINC' ) ) {
8
die();
9
}
10
11
/**
12
* Custom autoloader for the Easy MailChimp Extender plugin.
13
*
14
* @author Jeremy Pry
15
* @since 6.2.0
16
*
17
* @param string $class The name of the class to autoload.
18
*/
19
function yikes_inc_easy_mailchimp_extender_autoloader( $class ) {
yikesinc /
yikes-inc-easy-mailchimp-extender
Jeremy Pry
The PSR-1: Basic Coding Standard recommends that a file should either introduce new symbols, that is classes, functions, constants or similar, or have side effects. Side effects are anything that executes logic, like for example printing output, changing ini settings or writing to a file.
The idea behind this recommendation is that merely auto-loading a class should not change the state of an application. It also promotes a cleaner style of programming and makes your code less prone to errors, because the logic is not spread out all over the place.
To learn more about the PSR-1, please see the PHP-FIG site on the PSR-1.