On 7/9/07, Rob Church <robchur(a)gmail.com> wrote:
Just a quick note; if you're adding any cleverness
to the parser
(section edit links, etc.), don't forget to maintain cache coherency.
don't understand what you mean, here. I'm not adding any cleverness
to the parser, though, so I suppose it's not really a big deal.
My gut says it might be saner to return a simple array( const, message
), where const is one of a set of constants defined somewhere, perhaps
abusing a class for namespace purposes, which provides a simple
meaningful check. You might as well render the message *for* the
caller, since you're basically passing back all the pieces.
That's a really
interesting, and good, idea. It makes interpreting the
data for purposes other than simply displaying the message much easier
(and it saves an issue I had with the cascading protection message.