Revision aceaf18c
Added by Phil Davis almost 9 years ago
| src/usr/local/www/status_queues.php | ||
|---|---|---|
| 66 | 66 |
header("Pragma: no-cache"); // HTTP/1.0
|
| 67 | 67 |
*/ |
| 68 | 68 |
|
| 69 |
require("guiconfig.inc");
|
|
| 69 |
require_once("guiconfig.inc");
|
|
| 70 | 70 |
class QueueStats {
|
| 71 | 71 |
public $queuename; |
| 72 | 72 |
public $queuelength; |
Also available in: Unified diff
Always use require_once
The usage of require() and require_once() throughout the system is
inconsistent, and "bugs" come up now and then when the order of
"requires" is a bit different and some require() happens after the
include file is already included/required.
It seems to me that there is no harm at all in always using
require_once().