Re: Interface naming standards?
| From: | Patrick Müller | Date: | Thu, 01 Jun 2006 17:45:00 +0000 |
| Subject: | Re: Interface naming standards? | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-42727@lists.php.net to get a copy of this message | ||
hi,
Foo_Bar_IFooBar
imho this is the most common form if you want to indicate interfaces in the name. i've seen this in many languages.
Foo_Bar_FooBarInterface
is stupid if you use typehints, because you have to type it pretty often and method signatures getting pretty long.
Foo_Bar_FooBar
is often a lazy solution if you start with an implementation called Foo_Bar_FooBar but need an interface afterwards. Foo_Bar_FooBar turns into an interface so the typehints don't change and the implementation turns into something like Foo_Bar_(Default|Simple|Special)FooBar.
because pear is a library and the stable releases should be thought-out i tend to Foo_Bar_IFooBar.
elias