On 7/9/07, Rob Church <robchur(a)gmail.com> wrote:
On 09/07/07, Andrew Garrett <andrew(a)epstone.net>
wrote:
On second thoughts, I wonder if this'd make
it harder to take and use
the parameters, which are passed back in the array currently, but
you'd have to do some string parsing to get them with your
suggestion...
The main thing I'm concerned about here is that the first parameter be
some sort of constant value, because message keys change for various
reasons, and we want to be as free as possible to change them when
needed without hunting down 49 odd files...
I suppose it wouldn't kill any small furry animals if we tacked a
constant on the beginning and shifted it off before passing to
call_user_func_array( 'wfMsg' )...
...although I suppose we could just do a s/Simetrical// ;)
Rob Church