Prefixes and Suffixes Do Not Belong in Interface Names

about a month ago by David Grudl  

Using the I prefix or Interface suffix for interfaces, and Abstract for abstract classes, is an antipattern. It doesn't belong in pure code. Distinguishing interface names actually blurs OOP principles, adds noise to the code, and causes complications while developing. Here are the reasons.

Using the I prefix or Interface suffix for interfaces, and Abstract for abstract classes, is an antipattern. It doesn't belong in pure code. Distinguishing interface names actually blurs OOP principles, adds noise to the code, and causes complications while developing. Here are the reasons.
Unlock this premium content by becoming a partner. Are you already a partner? Please log in.

Recent posts

I-prefixes disappear from interface names

In Nette, interfaces were named with the letter I at the beginning (e.g. IRequest). A couple of years ago, an extremely slow and long term process began, which quietly while maintaining backwards compatibility is getting rid of these prefixes. How exactly is this happening and why?

about a month ago  ·  5 minutes to read

Latte 3: an impressive leap

The fanfare resounds through the hall and Latte 3 comes on the scene. With a completely rewritten compiler. The new version represents the biggest evolutionary leap ever made in Latte.

about a month ago  ·  7 minutes to read

For less screaming in the code

The Nette coding style is undergoing a minor modification: the PascalCase notation is now used for class constants instead of the original SCREAMING_SNAKE_CASE.

about a month ago  ·  5 minutes to read