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 21 and the first side effect is on line 11.
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.
It seems like you do not handle an error condition here. This can introduce security issues, and is generally not recommended.
If you suppress an error, we recommend checking for the error condition explicitly:
// For example instead of@mkdir($dir);// Better useif(@mkdir($dir)===false){thrownew\RuntimeException('The directory '.$dir.' could not be created.');}
Loading history...
12
'The '.__NAMESPACE__.'\PointsCollection class is deprecated since version 1.1 and will be removed in 2.0.',
13
E_USER_DEPRECATED
14
);
15
16
/**
17
* Class PointsCollection.
18
*
19
* @deprecated Since version 1.1, to be removed in 2.0.
20
*/
21
class PointsCollection extends ArrayCollection
22
{
23
/**
24
* @var string
25
*/
26
public $precision;
27
28
/**
29
* Initializes a new ArrayCollection.
30
*
31
* @param Point[] $elements
32
* @param string $precision
33
*/
34
public function __construct(array $elements = [], string $precision = Database::PRECISION_SECONDS)
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.