> This is indeed the right kind of solution. I just went back to
> look at the implementation, and discovered the documentation is
> incorrect for that hook. It claims that if a hook value returns
> nil, then the cache is returned. This is no longer true. Parsing
> will now also returns nil if a hook fails.
Oh, does this mean: If one of these hooks fails then always nil is returned,
regardless of the cache-contents??
Why this change? What are the advantages compared to the previous
behavior where simply the parsing is not performed and the cache returned??
> I don't think this matters for Richard's case, but it may for other
Eric Ludlam: zappo@..., eric@...
Home: http://www.ludlam.net Siege: http://www.siege-engine.com
Emacs: http://cedet.sourceforge.net GNU: http://www.gnu.org