Google SOC Proposal: Re-write Drupal in OOP

Hi guys, I submitted a proposal for GSOC and its now approved. We have 3 mentors and 1 student but were hoping Drupal developers from PH will also join!

Please support "Re-write Drupal in OOP"

Abstract:
Adopting Object-Oriented Programming for Drupal is basically one of the oldest issue that existed between module developers; It basically a battle between simplicity and efficiency vs code management. As much as I'm convinced to support simplicity; as a module developer, its quite annoying to encounter namespace collision because of Drupal's non-OOP feture.

For example: PHP Fatal error: Cannot redeclare test_perm() (previously declared in /var/www/path/to/drupal)...

Finally as more modules are added, the chance for namespace collision increases; and since most of the short, descriptive and effective names are already taken, it forces developers to use ridiculously long function names.

For example, using forms API alone requires:

function my_module_name_this_creates_a_form() { ... }

then you must also define a function for validation:

function my_module_name_this_creates_a_form_validate() { ... }

finally you must also define a function for submission:

function my_module_name_this_creates_a_form_submit() { ... }

Proposal:
We should re-write Drupal as OOP such that a main class contains all the core while allowing developers to use the same function name on a separate module class as hooks.

For example:

Class Drupal() { ... } // is the main class while
Class MyModule() { ... } // is a module class

then
$site = new Drupal(); // will initiate a site with the configuration
$drupal.loadmodule(new MyModule()); // will load the module
$drupal.hook_cron(); // invokes both the cron related method for Drupal and MyModule.

As we can see, It's shorter and solves the problem with namespace collision effectively.