News Feed
Sections




News Archive
Looking for more information on how to do PHP the right way? Check out PHP: The Right Way

Web Builder Zone:
What we don't need in object-oriented programming
October 04, 2010 @ 10:53:08

On the Web Builder Zone, Giorgio Sironi has a few suggestions about things that aren't really needed in object-oriented development but seem to have found their way in none the less (most of them are in PHP too).

It is in general true that you should strive for writing code as simple as possible (in length but in complexity too) to obtain an end result specified by a requirement or a user story. If there are two designs for a feature, almost always we would choose the simplest. This article takes a broader view on object-oriented programming, and ask the following question: What are the constructs we don't need in an object-oriented language? What we can take away without hampering our capabilities of building software?

He has a whole list of things that he thinks could be removed - "extra features" that wouldn't cause heartache if dropped including:

  • instanceof
  • break/continue
  • protected subclassing scope
  • if (conditional)
  • switch (conditional chain)
  • public (for fields)
0 comments voice your opinion now!
oop opinion remove feature functionality


blog comments powered by Disqus

Similar Posts

Artur Ejsmont's Blog: A few words on bugs and software quality

Jani Hartikainen's Blog: Should a failed function return a value or throw an exception?

Scott Mattocks' Blog: PHP-GTK 2 Alpha Released

SymfonyForge: Updates and New Features

Helgi\'s Blog: People and feature requests


Community Events





Don't see your event here?
Let us know!


list language refactor threedevsandamaybe install series release introduction interview podcast opinion api developer testing symfony2 unittest laravel code community framework

All content copyright, 2014 PHPDeveloper.org :: info@phpdeveloper.org - Powered by the Solar PHP Framework