Naming of interfaces/abstract classes in PHP 5.3 (using namespaces)

Question

Prior to PHP 5.3 I used to name interfaces/abstract classes like this:

abstract class Framework_Package_Subpackage_Abstract {} Framework/Package/Subpackage/Abstract.php  interface Framework_Package_Subpackage_Interface {} Framework/Package/Subpackage/Interface.php 

Now with PHP 5.3 and using namespaces I can't use my convention anymore, because interface and abstract are reserved keywords.

namespace Framework\Package\Subpackage; abstract class Abstract {} Framework/Package/Subpackage/Abstract.php  namespace Framework\Package\Subpackage; interface Interface {} Framework/Package/Subpackage/Interface.php 

So, what should I name my classes/interfaces like?

Answer 1

A current coding guide "PSR-2" basically suggests you drop the interface down one directory and combine the name.

eg:

File \Vendor\Foo\Interface.php ===> \Vendor\FooInterface.php. 

and the use stament eg:

use \Vendor\Foo\Interface; ===> use\Vendor\FooInterface; 

see: https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-2-coding-style-guide.md

Answer 2

About this question (Abstract and Interface), you might have a look at the post "Migrating OOP Libraries and Frameworks to PHP 5.3" on Matthew Weier O'Phinney's blog -- it's about Zend Framework, and how they could solve that problem in 2.0.

One of the things they note is :

In other OOP languages, such as Python, C#, interfaces are denoted by prefixing the interface with a capital 'I'; in the example above, we would then have Zend::View::IView.

So, in your example, you would have something like this, I guess :

namespace Framework\Package\Subpackage; abstract class ASubpackage {} Framework/Package/Subpackage/ASubpackage.php  namespace Framework\Package\Subpackage; interface ISubpackage {} Framework/Package/Subpackage/ISubpackage.php 

What do you think about that ? (I have not tested this way, but it doesn't look like a bad idea ? )