There are!
Right, but my point is, this approach doesn't seem to be sustainable, I imagine that it's like documentation - define a new function or piece of code - add a hook later when someone points out one doesn't exist.
Well, if you run a debugger, you could put breakpoints at any line of code and possibly at arbitrary expressions. It also slows down your code to a crawl, and it gives far more modifiability than anyone really needs.
I guess I wasn't too clear. Ideally, an extension should be something that an admin can just unzip, add a line to LocalSettings.php, and boom, it works. About half the extensions I've written, or installed myself, require modifying the actual code base, which makes it a) harder for the end user to configure and b) more of a pain to upgrade to the next version of Mediawiki. If there were a better system in place that really opened up Mediawiki (instead of just definining more hooks), extensions would gel better with the current software, would be more accessible and would have longer longevity.
Of course, I don't have any ideas, other than the not so great idea of tapping into wfProfileIn and wfProfileOut, but it seems that if we call these 2 functions for each function just to profile the software, it would be probably even more useful to use that space to call any available hooks that have been defined for any extensions, it just would seem more applicable.
Travis