and maintainer of:
At YAPC::Europe I heard a presentation by Mark-Jason Dominus (mjd/MJD). He stated that he would like to see more modules on CPAN that inherited from other modules on CPAN.
Since I am that kind of module builder and it gives me great opportunity to create some of the modules which I find useful. Well I am thinking whether this would require a module (package/class) namespace rule so you could easily see that a given module was a child class of another.
There are currently many "wrapper" modules on CPAN and many of them are modules inheriting from other modules. Some of these follow the naming convention *::Simple and the *::Lite namespace seem also to be growing.
So maybe what I am asking has already been decided, so the
But what happens when we start inheriting from these modules, will we end up with: *::Simple::Lite and *::Simple::Simple?
Well also this problem seem to have taken care of itself, apparently *::Simple::* and *::Lite::* seem to be quite controlled namespaces. I only found one weird one: Bot::BasicBot::Pluggable::Module::SimpleBlog::Store::SQLite, this one has the words Basic, Simple and Lite in its name - it must be easy to use?
At the same time you have the inheriting modules which do not use the naming conventions of *::Simple and *::Lite?
I guess that the way it works for now is ok, CPAN works and it grows...
The last problem is the modules which are not inheritable - now THEY are annoying
Well I better stop these ramblings and go back to work...