<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
On 07/04/2011 07:15, Wolfgang Laun wrote:
<blockquote
cite="mid:BANLkTi=Agc4kc1Jo+1zSP1G1YT8S29XxsQ@mail.gmail.com"
type="cite">The main point I was trying to make here was that very
complex expressions are very, very rare.<br>
<br>
An acceptable compromise would be to analyse what can be done
without busting a vein, and to flag anything anthing else as an
error ("expression too complicated") and document the way around,
presumably a user-defined variable where the user provides the
type. And if the expressions is really so complex, this might even
imrove readability ;-)<br>
</blockquote>
MVEL returns Object as the return type if it can't figure out what
it is. So that could be possability. So on Object as the return type
we use the expr on each and every setter. Good idea. Do we need to
throw an exception or just default to re-evaluating the expr for
each setter?<br>
<br>
Mark<br>
<blockquote
cite="mid:BANLkTi=Agc4kc1Jo+1zSP1G1YT8S29XxsQ@mail.gmail.com"
type="cite">
<br>
Wolfgang<br>
<br>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
rules-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/rules-dev">https://lists.jboss.org/mailman/listinfo/rules-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>