Minimum PHP Version?

[Angryboy]

It breaks extend..

An easy to use config file wrapper for plugins is easy with 3.4, if you want to make one go ahead ill add it to 3.4
The problem without plugin classes, is you have to throw the plugin id around, there is no way to know which plugin is trying to do stuff.

( we register hooks and use debugg_backtrace to log the file and stuff, but this is being removed in 3.4 as it is inefficient and unecessary, so it cannot be used, it is also a non production function )

only register_plugin knows what the plugin id is at runtime, hmm

Maybe a interesting back portable class could be reachable by old plugins.

Code:

$myplugin = getPlugin($thisfile);
$config = $myplugin->getConfig();
$config->addConfig('color','red');
$config->save;

of course making stuff like that plugin useful might be neat

configdatatype extends class plugin.config
plugin.config.adddatatype($configid);
datatype wysiwyg

Are you saying that the 5.2 closure stuff breaks extend, or removing the your_plugin.php file?

As for throwing the ID around, that is where anonymous functions could help. You'd create a collection of "curried" functions, and then pass the plugin's id into the curried function in the plugin loading loop:

PHP Code:

$register_plugin = function($id, ...) {
  return function (...) use ($id) { ... };
};

$add_hook = function($id, ...) {
  return function (...) use ($id) { ... };
};

$get_config =  function($id, ...) {
  return function (...) use ($id) { ... };
};

...

foreach ($plugins as $id => $file) {
  $register = $register_plugin($id);
  $hook     = $add_hook($id);
  $config   = $get_config($id);
  ...

  // Closure to protect variables declared within the function
  // Import the above local functions into said closure
  call_user_func(function() use ($file, $register, $hook, $config, ...) {
    include $file;
  });
}