This is an old revision of the document!

Request for Comments: Function autoloading through spl_autoload*


The topic of supporting function autoloading was brought up many times in the past, this RFC introduces a potential implementation which would be consistent with what we have for autoloading classes.


The suggested change would be pretty straightforward and BC compatible:

  • Add a fourth optional parameter for spl_autoload_register called $types with the default value of T_CLASS (this would keep the BC), supported values would be any combination of T_CLASS and T_FUNCTION for now.
    • As you would guess, this would work the same way as the $error_types parameter works for set_error_handler: you can specify for which type(s) of missing tokens the autoloader should be called.
  • The type for the missing token should also be passed to the $autoload_function callback as a second param.
    • This is needed to be able to handle multiple types of tokens with a common callback.
    • Note that passing more parameters to a function than it has in its definition is valid, this would also be a backward compatible change.
  • Change the current class autoloading to only call the autoloaders which match with the T_CLASS types.
  • Add the function autoloading to only call the autoloaders which match with the T_FUNCTION types.

Future improvements

Notice that currently only functions are proposed, but we could implement autoloading other tokens (T_CONST?) with this interface.


Patches welcome! :)

rfc/autofunc.1312505116.txt.gz · Last modified: 2017/09/22 13:28 (external edit)