Originally Posted by Phinix
Excellent!
Now, we just need some sort of "go/no-go" list for commonly hooked functions that are "safe" and ones that are "not safe."
However, as we have seen with Homestead, the chains that bind these functions together can change in the source and result in previously safe hooks becoming unsafe.
As a general rule I suppose you could say never post-hook unless it is ABSOLUTELY necessary.
|
In general, hooking or overriding code which sets up objects will be prone to error. It's on the author to research their code paths and determine the outcomes (dropped the ball here myself this patch).
A manual posthook does not have to be regarded as a sort of boogyman, just use care when researching if it will work as expected.