- #local directive
no... :)
Sorry - I didn't mean to be that abrupt. See above re the tools - are
there really enough people using #local that it warrants inclusion in
the core? I threw that together in about 10 minutes, if I remember.
That people are using it is thrilling (and scary... :) but I think that
tools would be a great place.
Well, I was asking for it but I have never used this. I didn't like
it. It seems to me like dirty hack ;-) and I wasn't sure, whether
it will solve my issues.
When we're talking about 2.0, I'd like to see major changes.
Only global variables and parameter passed by name are very
limiting Velocity in my eyes. #local is not solution.
I'm sure, that with current Context semantics it should be
easy to introduce real local variables. The biggest issue
is to decide, how user will create them. E.g. syntax.
For example:
-----
#macro(test $b)
#set($a = 2 * $b)
double of $b is $a
#end
#set($a=4)
#test($a)
$a
------
will produce:
---
double of 4 is 8
4
---
but Rc2 produces:
---
double of 8 is 8
8
---
Well, this is the BIG THINK, I'd love. For 2.0 we should
have big goals, not minor enhancements ;-) And that it
will break backward compatibility? Who cares? It is 2.0,
it may break things.
Sincerelly
Leos
--
Leos Literak
http://AbcLinuxu.cz - tady je tucnakum hej!
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
