On 9/22/06, Jared Rypka-Hauer <[EMAIL PROTECTED]> wrote:
I'm thinking that it would be very handy sometimes to use CF-native functions in the XML as arguments to property or constructor-arg tags... like this:<property name="inputArray"> <value>$${listToArray("1,2,3,4,5")}</value> </property>
The trouble is that this opens a giant can of worms. It really needs evaluate() to make this work and then you can evaluate *anything*... However, having said that... Fusebox 4 and on has allowed evaluation of arbitrary expressions in certain context. Mach II also does this (the variable= attribute). I'm not sure whether Model-Glue has any evaluation contexts like that but there are clearly precedents for this sort of thing. Having said that... It really does make me uncomfortable. It's really hard to specify the execution context for evaluated expressions and as soon as you make it a documented part of the framework, people start to use it and then get confused by "strange behavior" which almost always follows hot on the heels of evaluate()... :) So, overall, I guess I'd have a weak vote against this but if it goes in, it should be unconstrained. -- Sean A Corfield -- (904) 302-SEAN An Architect's View -- http://corfield.org/ "If you're not annoying somebody, you're not really alive." -- Margaret Atwood
