[RFC] [VOTE] Preloading View as Markdown

The preloading RFC is turned into voting state.
Apologies if it's been asked before but from:

Only classes without unresolved parent, interfaces, traits and constant
values may be preloaded. If a class doesn't satisfy to this condition, ...
Is it possible to inspect which classes have been successfully
preloaded, and/or which classes have failed to be preloaded due to
violation of the appropriate conditions?
The RFC states:

| opcache_get_status is extended to provide information about preloaded
| functions, classes and scripts under the “preload_statistics” index.

Right, if I remember properly, this was Rasmus idea.

$ sapi/cli/php -r 'var_dump(opcache_get_status());'

array(9) {
  ...
  ["preload_statistics"]=>
  array(4) {
    ["memory_consumption"]=>
    int(912672)
    ["functions"]=>
    array(?) {
      [0]=>
      string(8) "_preload"
      ...
    }
    ["classes"]=>
    array(?) {
      [0]=>
      string(38) "Zend_Controller_Action_Helper_Abstract"
      ...
    }
    array(?) {
      [0]=>
      string(46) "/home/dmitry/php/etc/preload.php"
      ...
    }
  }
  ...
}

Thanks. Dmitry.

Now on the convention, is there any reason why single underscore () is
used instead of double underscores (_)?

Are you talking about _preload()? I guess this is just an example userland
code in the RFC, not a new internal or magic method.

Now on the convention, is there any reason why single underscore () is
used instead of double underscores (_)? We already have __autoload,
__sleep, __toString, __wakeup, etc.

There is no convention at all. The ini directive opcache.preload allows
to specify a PHP script which will be evaluated. Period.

--
Christoph M. Becker