If the "documented behaviour" is "expression is evaluated once" you cannot deviate silently and must flag an error. If you say that it is "implementation defined" you can<br>do what you like. Either way, you <i>must</i> document it ;-)<br>
<br>Wolfgang<br><br>On 7 April 2011 16:36, Mark Proctor <<a href="mailto:mproctor@codehaus.org">mproctor@codehaus.org</a>> wrote:<br>> On 07/04/2011 07:15, Wolfgang Laun wrote:<br>><br>> The main point I was trying to make here was that very complex expressions<br>
> are very, very rare.<br>><br>> An acceptable compromise would be to analyse what can be done without<br>> busting a vein, and to flag anything anthing else as an error ("expression<br>> too complicated") and document the way around, presumably a user-defined<br>
> variable where the user provides the type. And if the expressions is really<br>> so complex, this might even imrove readability ;-)<br>><br>> MVEL returns Object as the return type if it can't figure out what it is. So<br>
> that could be possability. So on Object as the return type we use the expr<br>> on each and every setter. Good idea. Do we need to throw an exception or<br>> just default to re-evaluating the expr for each setter?<br>
><br>> Mark<br>><br>> Wolfgang<br>><br>><br>> _______________________________________________<br>> rules-dev mailing list<br>> <a href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/rules-dev">https://lists.jboss.org/mailman/listinfo/rules-dev</a><br>><br>><br>> _______________________________________________<br>> rules-dev mailing list<br>
> <a href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</a><br>> <a href="https://lists.jboss.org/mailman/listinfo/rules-dev">https://lists.jboss.org/mailman/listinfo/rules-dev</a><br>><br>><br>
<br>