Using Drupal GPL code in a non-Drupal project

Hi Crell, I read you said, "not in this thread", but here are my views in response to this:

"So far no one has figured out a good way to emulate that efficiently in OO code e as well as we can in procedural code (hooks). If someone can, though, I'm interested in hearing about it."

I think there's an easy way to accomplish this. Make each module implement a class with the same name as the module. Then the class needs to provide public methods for each hook it needs to implement. e.g.

class MyModule {
public function init() {
}

public function user() {
}
}

The Drupal framework itself will create an instance of the class for each module, and then can use PHP built-in function, method_exists (http://www.php.net/manual/en/function.method-exists.php), to check if a module implements a hook. If it does, call the method normally as a hook.

Now, there are other modules e.g. Views, that have their own requirements. Certainly I would not like to have Views code in the main MyModule.module file, as that would bloat the code.

The solution is also easy. As a module developer, I would provide 2 classes:

mymodule.module, and
mymodule_views.module

The first contains: class MyModule {}

and the second contains: class MyModule_Views {}

There's only 1 thing that needs to be considered in the above approach, how do I access methods of MyModule from another class, like we can today call methods of one module from another module.

This takes me to present 2 options:

1) The methods in the module class (i.e. hooks) should be static. I personally am not in favor of this appraoch, as this is not extensible.
2) The Drupal framework exposes the object for each module it has created, so I can get the object for each module class from Drupal framework, and use it to access oublich methods provided by that module. I am more inclined to this approach, as this allows me benefits of OO approach like inheritance, overriding etc.

Would be interesting to see, what you think...