On Saturday 14 June 2008, Earnie Boyd wrote:
Quoting Syscrusher <syscrusher@4th.com>:
On Sat, 2008-06-14 at 16:47 +0200, Adrian Rossouw wrote:
Dries didn't like the idea when i floated it 5 years ago, but maybe it's time =)
If we're talking about that kind of a major change, is it time to revisit the question of whether Drupal should use PHP's OOP features, now that the PHP language has better OO support than it did several years ago?
My opinion is that no and yes. Some modules would benefit from the use of OO while the Drupal core functionality should remain procedural.
Drupal core should use procedural where it makes sense to do so, and OO where it makes sense to do so. Contrib should use procedural where it makes sense to do so, and OO where it makes sense to do so. PHP code should use procedural where it makes sense to do so, and OO where it makes sense to do so. Religious adherence or distaste for one mechanism or the other is simply naive and damaging to the architecture of the project (any project, not just Drupal). -- Larry Garfield AIM: LOLG42 larry@garfieldtech.com ICQ: 6817012 "If nature has made any one thing less susceptible than all others of exclusive property, it is the action of the thinking power called an idea, which an individual may exclusively possess as long as he keeps it to himself; but the moment it is divulged, it forces itself into the possession of every one, and the receiver cannot dispossess himself of it." -- Thomas Jefferson