This is great, I understand the pros of this approach, however, when first learning about hooks and $op, it was nice to be able to dsm($op) and find out what all was available to me. How would a newer dev find this information now? In the registry?<br>
<br><div class="gmail_quote">On Tue, May 13, 2008 at 11:34 AM, Adrian Rossouw <<a href="mailto:adrian@bryght.com">adrian@bryght.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d"><br>
On 13 May 2008, at 6:40 AM, Larry Garfield wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
I have an irrational hatred of switch statements, so eliminating hooks that<br>
are nothing but nested switch statements half the time gets a big +1 from<br>
me. :-)<br>
</blockquote></div>
the very first iteration of fapi was to have each form be one function with<br>
a switch statement.<br>
<br>
can you imagine how nasty that would have been ?<br>
<br>
i'm _firmly_ in the multiple function camp. I even write little stubs for<br>
my own nodeapi functions, that call modulename_nodeapi_$op functions<br>
etc.<br>
<br>
</blockquote></div><br>