Passed
Push — master ( d2520f...3f8ec2 )
by Michael
02:50
created

Calendar_Second   A

Complexity

Total Complexity 5

Size/Duplication

Total Lines 47
Duplicated Lines 0 %

Importance

Changes 0
Metric Value
wmc 5
dl 0
loc 47
rs 10
c 0
b 0
f 0

5 Methods

Rating   Name   Duplication   Size   Complexity  
A fetch() 0 3 1
A fetchAll() 0 3 1
A size() 0 3 1
A build() 0 3 1
A __construct() 0 3 1
1
<?php
0 ignored issues
show
Coding Style Compatibility introduced by
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 46 and the first side effect is on line 52.

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
/* vim: set expandtab tabstop=4 shiftwidth=4: */
4
5
/**
6
 * Contains the Calendar_Second class.
7
 *
8
 * PHP versions 4 and 5
9
 *
10
 * LICENSE: Redistribution and use in source and binary forms, with or without
11
 * modification, are permitted provided that the following conditions are met:
12
 * 1. Redistributions of source code must retain the above copyright
13
 *    notice, this list of conditions and the following disclaimer.
14
 * 2. Redistributions in binary form must reproduce the above copyright
15
 *    notice, this list of conditions and the following disclaimer in the
16
 *    documentation and/or other materials provided with the distribution.
17
 * 3. The name of the author may not be used to endorse or promote products
18
 *    derived from this software without specific prior written permission.
19
 *
20
 * THIS SOFTWARE IS PROVIDED BY THE AUTHOR "AS IS" AND ANY EXPRESS OR IMPLIED
21
 * WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
22
 * MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
23
 * IN NO EVENT SHALL THE FREEBSD PROJECT OR CONTRIBUTORS BE LIABLE FOR ANY
24
 * DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
25
 * (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
26
 * LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
27
 * ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
28
 * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
29
 * THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
30
 *
31
 * @category  Date and Time
32
 *
33
 * @author    Harry Fuecks <[email protected]>
34
 * @copyright 2003-2007 Harry Fuecks
35
 * @license   http://www.debian.org/misc/bsd.license  BSD License (3 Clause)
36
 *
37
 * @link      http://pear.php.net/package/Calendar
38
 */
39
40
/**
41
 * Allows Calendar include path to be redefined.
42
 *
43
 * @ignore
44
 */
45
if (!defined('CALENDAR_ROOT')) {
46
    define('CALENDAR_ROOT', 'Calendar/');
47
}
48
49
/**
50
 * Load Calendar base class.
51
 */
52
require_once CALENDAR_ROOT . 'Calendar.php';
53
54
/**
55
 * Represents a Second<br>
56
 * <b>Note:</b> Seconds do not build other objects
57
 * so related methods are overridden to return NULL.
58
 *
59
 * @category  Date and Time
60
 *
61
 * @author    Harry Fuecks <[email protected]>
62
 * @copyright 2003-2007 Harry Fuecks
63
 * @license   http://www.debian.org/misc/bsd.license  BSD License (3 Clause)
64
 *
65
 * @link      http://pear.php.net/package/Calendar
66
 */
67
class Calendar_Second extends Calendar
0 ignored issues
show
Coding Style Compatibility introduced by
PSR1 recommends that each class must be in a namespace of at least one level to avoid collisions.

You can fix this by adding a namespace to your class:

namespace YourVendor;

class YourClass { }

When choosing a vendor namespace, try to pick something that is not too generic to avoid conflicts with other libraries.

Loading history...
68
{
69
    /**
70
     * Constructs Second.
71
     *
72
     * @param int $y year e.g. 2003
73
     * @param int $m month e.g. 5
74
     * @param int $d day e.g. 11
75
     * @param int $h hour e.g. 13
76
     * @param int $i minute e.g. 31
77
     * @param int $s second e.g. 45
78
     */
79
    public function __construct($y, $m, $d, $h, $i, $s)
80
    {
81
        parent::__construct($y, $m, $d, $h, $i, $s);
82
    }
83
84
    /**
85
     * Overwrite build.
86
     */
87
    public function build()
88
    {
89
        return;
90
    }
91
92
    /**
93
     * Overwrite fetch.
94
     */
95
    public function fetch()
96
    {
97
        return;
98
    }
99
100
    /**
101
     * Overwrite fetchAll.
102
     */
103
    public function fetchAll()
104
    {
105
        return;
106
    }
107
108
    /**
109
     * Overwrite size.
110
     */
111
    public function size()
112
    {
113
        return;
114
    }
115
}
116