Personally, i feel that templates whose macro calls don't match up to
the macro definitions are *already* broken.
this is my general thought on the whole thing too.
and as we deal in financial transactions, I take a general view of
it is better not to show something than to show something wrong.
however, I can understand that in an entertainment situation you might have
the exact opposite view.
again though, I think this goes back to a 2 modes of running.
development - always halt on errors - someone's there to fix them.
deployment - do the best you can - log what goes wrong
and see a setting much more in this idea.
btw: this is also why I always develop with the UberspectTestImpl and rather
think that it should be default Uberspect, while currently it is only in the
test classes.
Llewellyn.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
