I\'m searching for following issue i have. The class file names of our project are named logon.class.php But the interface file for that class is named logon.interface.php
You should have some naming conventions for your classes and interfaces e.g. your class name is logon
and interface name logon_interface
, then you can easily differentiate between the two. For example, explode $name
by underscore and check if last element is interface
.
You can use ReflectionClass::isInterface to determine if the class is an interface.
$reflection = new ReflectionClass($name);
if ($reflection->isInterface()){
//Is an interface
}else{
//Not an interface
}
In your case, you would probably have to use file_exist
first on $name.interface.php
and $name.class.php
to determine if they exist, require the one that exists, then check if it's an interface.
However, my opinion is that this might cause problems down the track. What if you have MyClass.class.php
and MyClass.interface.php
?
To avoid class name clashes you can use namespaces. Check The PSR-0 specifications.
Also check this post. If you read the contents of the file before including it, you can tokenize it and figure if the file contains an Interface or a class, without actually loading the class/interface. Keep in mind that interfaces and classes can't have the same name
Note: Using this method you can actually change the name of the interface at runtime (before loading the class, although that does seem very good practice)