<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>I got the same feeling that Geoffrey had about readability.</div><div><br></div><div>We added "from" its really easy to get, why not add "else".</div><div><br></div><div>when<br> Person( name == "darth" ) else [darthIsMissing] <br> A()<br>then<br> ....<br>then.darthIsMissing<br> log("Darth was never found");</div><div>end</div><div><br></div><div>or</div><div><br></div><div>when<br> Person( name == "darth" ) else { log("Darth was never found"); }<br> A()<br>then<br> ....<br>end</div><div><br></div><div>"Inline then" could be done with inner rules. Similar to what Mario suggested.</div><div><br></div><div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; ">rule "Handle Login"</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; "> when</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; "> $loginRequest :LoginRequest()</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; "> AuthorizedUsers( list contains $loginRequest.user ) else [unsuccessfulLoginAttempt]</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; min-height: 14px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; "> inner rule "Check if Admin"</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; "> $p :AdminRights( user == $loginRequest.user )</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; "> then </div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; "> showAdminMenu(); </div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; "> end</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; min-height: 14px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; "> then</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; "> logInUser( $loginRequest.user );</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; min-height: 14px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; "> then.unsuccessfulLoginAttempt</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; "> log( "There was and unsuccessful login attempt with the user name " + $loginRequest.user.name ); </div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; ">end</div></div><div><br></div><div>Toni</div><br><div><div>On Aug 19, 2011, at 2:59 PM, Geoffrey De Smet wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
<div text="#000000" bgcolor="#ffffff">
I like Mario's proposal because I can actually read it.<br>
Those special chars | < are gibberish to me.<br>
<br>
The only reason we're not debating to use a new readable, intuitive
keyword, is because of the back-wards compatibility issues involved.<br>
But using unreadable, unintuitive special char just for that, is
probably not a good idea.<br>
I wonder if we reserve new keywords by prefix them with reserved
special char like "@"?<br>
Then we can introduce as many keywords as we want without breaking
backwards compatibility.<br>
<br>
Who's our target users for DRL authors?<br>
A) Supersmart computer science guys<br>
B) Blue collar Java programmers<br>
C) Domain experts (= not programmers)<br>
<br>
I 'd classify "{notA} < A()" as (given some time to learn it)
readable for A, but not for B and C.<br>
<br>
Op 18-08-11 23:35, Mario Fusco schreef:
<blockquote cite="mid:CAPYjU_mV45SC5M-UYOmFk9bF7Pi34144pqPEjUtm1woZrdXDRg@mail.gmail.com" type="cite">Hi Mark,<br>
<br>
Since you're gathering 2 cents here and there I decided to add
also mine even if I am pretty sure that I am still missing the
whole picture and anyway at the moment I cannot see all the
consequences of what I am going to propose.<br>
<br>
To tell you the truth I find the label syntax not very intuitive
and I was wondering if we could avoid it in some way. In the end
what the 90% of the users are asking for is just something like:<br>
<br>
rule R<br>
when<br>
A()<br>
then<br>
do something<br>
else<br>
do something else<br>
end <br>
<br>
while we are going to give them something that is not exactly the
same:<br>
<br>
rule R<br>
when<br>
{notA} < A()<br>
then<br>
do something<br>
then.notA<br>
do something else<br>
end <br>
<br>
In particular I was thinking if we could keep the when ... then
... else syntax that should be familiar to the biggest part of the
users and at the same time obtain a flexibility similar to the one
provided by the labels syntax. Probably we could do it with a kind
of nested rules so, for instance, the rule:<br>
<br>
rule R1<br>
when<br>
{af} < A() > {at}<br>
B()<br>
then<br>
DO<br>
<a moz-do-not-send="true" href="http://then.af/">then.af</a><br>
DO.af<br>
<a moz-do-not-send="true" href="http://then.at/">then.at</a><br>
<a href="http://DO.at">DO.at</a><br>
end<br>
<br>
could be rewritten as it follows:<br>
<br>
rule R1<br>
when<br>
B()<br>
then<br>
DO<br>
rule R1A<br>
when<br>
A()<br>
then<br>
<a href="http://DO.at">DO.at</a><br>
else<br>
DO.af<br>
end <br>
end <br>
<br>
Of course the nested rule couldn't be used by the Drools engine as
it is, but we could implement a kind of "linearization" process at
compile time that translates it more or less as:<br>
<br>
rule R1_1<br>
when<br>
A()<br>
B()<br>
then<br>
DO<br>
<a href="http://DO.at">DO.at</a><br>
end<br>
<br>
rule R1_2<br>
when<br>
not A()<br>
B()<br>
then<br>
DO<br>
DO.af<br>
end<br>
<br>
In the same way the "or" example:<br>
<br>
rule R1<br>
when<br>
( A() > {a1} or<br>
B() > {b1} or<br>
C() > {c1} )<br>
D()<br>
then<br>
DO<br>
then.a1<br>
DO.a1<br>
then.b1<br>
DO.b1<br>
then.c1<br>
DO.c1<br>
end<br>
<br>
could be written as:<br>
<br>
rule R1<br>
when<br>
D()<br>
then<br>
DO<br>
rule R1A<br>
when<br>
A()<br>
then<br>
DO.a1<br>
end <br>
rule R1B<br>
when<br>
B()<br>
then<br>
DO.b1<br>
end <br>
rule R1C<br>
when<br>
C()<br>
then<br>
DO.c1<br>
end<br>
end <br>
<br>
and then linearized at compile time in a similar way as I wrote
before.<br>
<br>
Once again I still haven't evaluated all the implications of my
suggestion neither I know if we can cover with it all the cases
proposed by Mark. I am pretty sure I am missing something
important to be honest, but since we are in a "brainstorming
phase" I thought it could worth to consider it at least.<br>
<br>
My 2 cents,<br>
Mario<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>
<pre class="moz-signature" cols="72">--
With kind regards,
Geoffrey De Smet</pre>
</div>
_______________________________________________<br>rules-dev mailing list<br><a href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</a><br>https://lists.jboss.org/mailman/listinfo/rules-dev<br></blockquote></div><br></body></html>