Jon Stevens wrote:
>
> on 1/15/01 11:20 AM, "bob mcwhirter" <[EMAIL PROTECTED]> wrote:
>
> > ! applies to the operator it's glued to. $!foo means that if something
> > goes wonky during the deref of 'foo', then don't complain.
>
> I like that definition. I would be +1 then to having a #!directive to match
> having $!object for consistency.
>
> -jon
I like the consistency, but I have some concerns, because we are mixing
up template design stuff with system / programming / logging stuff.
For references, using $! vs $ is a 'template engineer' decision, where
they say "I don't want schmoo in the output if the reference isn't
valid. It's ok if the reference isn't valid - I would check with #if()
if I cared"
Whereas #!set($foo = $bar) is problematic, because now the template
designer has determined that they don't want anything in the *log* if
the *programmer* made an error, if indeed a null is unexpected.
So then we have to add another switch to turn off this behavior when
testing and debugging, or else you won't have clue what's going on w/o
reading all the templates.
Doesn't this kinda re-couple the view and model/controller decoupling
that Vel provides?
So can we have further discussion?
geir
--
Geir Magnusson Jr. [EMAIL PROTECTED]
Velocity : it's not just a good idea. It should be the law.
http://jakarta.apache.org/velocity
