mambax7 /
pedigree
| 1 | <?php namespace XoopsModules\Pedigree; |
||
| 2 | |||
| 3 | /* |
||
| 4 | You may not change or alter any portion of this comment or credits |
||
| 5 | of supporting developers from this source code or any supporting source code |
||
| 6 | which is considered copyrighted (c) material of the original comment or credit authors. |
||
| 7 | |||
| 8 | This program is distributed in the hope that it will be useful, |
||
| 9 | but WITHOUT ANY WARRANTY; without even the implied warranty of |
||
| 10 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. |
||
| 11 | */ |
||
| 12 | /** |
||
| 13 | * Pedigree module for XOOPS |
||
| 14 | * |
||
| 15 | * @copyright XOOPS Project (https://xoops.org) |
||
| 16 | * @license GPL 2.0 or later |
||
| 17 | * @package pedigree |
||
| 18 | * @since 2.5.x |
||
| 19 | * @author XOOPS Module Dev Team (https://xoops.org) |
||
| 20 | */ |
||
| 21 | |||
| 22 | use XoopsModules\Pedigree; |
||
|
0 ignored issues
–
show
|
|||
| 23 | |||
| 24 | defined('XOOPS_ROOT_PATH') || die('Restricted access'); |
||
| 25 | |||
| 26 | /** |
||
| 27 | * Class Pedigree\TempHandler |
||
| 28 | */ |
||
| 29 | class TempHandler extends \XoopsPersistableObjectHandler |
||
| 30 | { |
||
| 31 | /** |
||
| 32 | * @param null|\XoopsDatabase $db |
||
| 33 | */ |
||
| 34 | public function __construct(\XoopsDatabase $db) |
||
| 35 | { |
||
| 36 | parent::__construct($db, 'pedigree_temp', Temp::class, 'id', 'naam'); |
||
| 37 | } |
||
| 38 | } |
||
| 39 |
Let?s assume that you have a directory layout like this:
. |-- OtherDir | |-- Bar.php | `-- Foo.php `-- SomeDir `-- Foo.phpand let?s assume the following content of
Bar.php:If both files
OtherDir/Foo.phpandSomeDir/Foo.phpare loaded in the same runtime, you will see a PHP error such as the following:PHP Fatal error: Cannot use SomeDir\Foo as Foo because the name is already in use in OtherDir/Foo.phpHowever, as
OtherDir/Foo.phpdoes not necessarily have to be loaded and the error is only triggered if it is loaded beforeOtherDir/Bar.php, this problem might go unnoticed for a while. In order to prevent this error from surfacing, you must import the namespace with a different alias: