1. Extension developer puts his PHP code into manifest.xml file.
He specifies the name of the hook, where he wants his code to be executed.
E.g. I want to print out the list of extensions installed in ft_about_end hook:
<hook id="ft_about_end" priority="10"><![CDATA[
if (!defined('PUN_EXTENSIONS_USED') && !empty($pun_extensions_used))
{
define('PUN_EXTENSIONS_USED', 1);
echo '<p id="extensions-used">Currently used extensions: '.implode(', ', $pun_extensions_used).'. Copyright © 2008 <a href="http://punbb.informer.com/">PunBB</a></p>';
}
]]></hook>
(pun_bbcode/manifest.xml)
You may find this hook in footer.php.
2. When you install the extension, PunBB parses its' manifest.xml and places the code for each hook into database. After extension installation, you have pairs (hook_id, code) in DB.
3. Before PunBB generates the page, it caches the code for each hook. It iterates through the pairs (hook_id, code) and creates the PHP array containing all the codes for every hook used by all the extensions enabled. This array is being included on every page hit. You may find the cache file in /cache/cache_hooks.php. Different extensions may use the same hook. Their codes are joined in the cache then (ordered by priority, if given in manifest.xml).
4. PunBB developers has placed hook calls in the code like this:
($hook = get_hook('ft_about_end')) ? eval($hook) : null;
When PHP finds this line, it looks through the cache for the code for the hook name given. E.g. $forum_hooks['ft_about_end'].
5. If the code for the hook is present. It is being evaluated in eval($hook). This means that the code is virtually inserted just in the place of hook. The code has the same variable scope as the hook: you may use all the variables around, create new ones and s.o. (This differs from function call.)
That's it.
Ooh...
UPDATE: Fixed mistakes noted by lie2815 :-)
]]>
]]>
Thanks!]]>