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 24 and the first side effect is on line 13.
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
use SG\HookRegistry;
4
use SMW\ApplicationFactory;
5
6
/**
7
* A terminology markup extension with a Semantic MediaWiki backend
8
*
9
* @defgroup SemanticGlossary Semantic Glossary
10
* @author Stephan Gambke
11
*/
12
if ( !defined( 'MEDIAWIKI' ) ) {
13
die( 'This file is part of a MediaWiki extension, it is not a valid entry point.' );
14
}
15
16
if ( defined( 'SG_VERSION' ) ) {
17
// Do not initialize more than once.
18
return 1;
19
}
20
21
/**
22
* The Semantic Glossary version
23
*/
24
define( 'SG_VERSION', '1.2.0-alpha' );
25
26
if ( !defined( 'SMW_VERSION' ) ) {
27
die( 'Semantic Glossary depends on the Semantic MediaWiki extension. You need to install Semantic MediaWiki first.' );
28
}
29
30
if ( !defined( 'LINGO_VERSION' ) ) {
31
die( 'Semantic Glossary depends on the Lingo extension. You need to install Lingo first.' );
SemanticMediaWiki /
SemanticGlossary
Stephan Gambke
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.