<!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 bgcolor="#ffffff" text="#000000">
On 22/09/2010 17:20, Wolfgang Laun wrote:
<blockquote
cite="mid:AANLkTikH8pEwZruJH-=kXf6o9H0_T3ejqFAHsejW=zwG@mail.gmail.com"
type="cite">See my remarks inline.<br>
<br>
On 22 September 2010 17:03, Mark Proctor <span dir="ltr"><<a
moz-do-not-send="true" href="mailto:mproctor@codehaus.org">mproctor@codehaus.org</a>></span>
wrote:<br>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="border-left: 1px solid
rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left:
1ex;">
<div bgcolor="#ffffff" text="#000000"> So things that are
doing are:<br>
<br>
Single binding on 'or'<br>
$binding : ( Pattern() || Pattern() )<br>
<br>
We are thinking of only allowing 'or' between patterns and
not allowing users to mix and match 'or' and '||'. Inside
of patterns '||' is the only connective allowed and will
remain so.<br>
</div>
</blockquote>
<div><br>
OK, a clear distinction avoids confusion.<br>
</div>
<blockquote class="gmail_quote" style="border-left: 1px solid
rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left:
1ex;">
<div bgcolor="#ffffff" text="#000000"> <br>
We will also probably make a choice and only allow infix
'or' and 'and', at the moment users can chose infix or
prefix. Personally I find prefix quite attractive as it
works sort of like a "choice":<br>
(or Person( ... )<br>
Person( ... )<br>
Person( ...) )<br>
<br>
But I think most peopel are more comfortable with infix:<br>
(Person( ... ) or<br>
Person( ... ) or<br>
Person( ...) )<br>
<br>
</div>
</blockquote>
<div>(name ... ) is neither function style nor infix, so
removing yet another way of writing expressions is OK. Let's
infix. <br>
</div>
</div>
</blockquote>
The prefix way, shown above was following what jess and clips did.
Our initial mindset was based on those two engines, in trying to
make a more comfortable environment for them to transition too. We
are now in a more comfortable position and able to do what is right
for our existing community and worry less about appealing to other
communities.<br>
<br>
Mark<br>
<blockquote
cite="mid:AANLkTikH8pEwZruJH-=kXf6o9H0_T3ejqFAHsejW=zwG@mail.gmail.com"
type="cite">
<div class="gmail_quote">
<div><br>
</div>
<blockquote class="gmail_quote" style="border-left: 1px solid
rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left:
1ex;">
<div> return value, eval, literal constraint, variable
constraint are going. These are left overs of a Clips based
grammar. So instead we'll have a generic "expr" class that
follow more common modern ASTs for expression engines, like
say MVEL.<br>
</div>
</blockquote>
<div> OK!<br>
</div>
<blockquote class="gmail_quote" style="border-left: 1px solid
rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left:
1ex;">
<div bgcolor="#ffffff" text="#000000"> <br>
Davide has also requested that we make $ prefix mandatory
for LHS bindings as that is deterministic and again makes
the grammar cleaner.</div>
</blockquote>
<div>I don't understand why it should be "cleaner". After all, a
'$' could even result from a Java identifier although this is
discouraged, according to the Language Spec.<br>
<br>
</div>
<blockquote class="gmail_quote" style="border-left: 1px solid
rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left:
1ex;">
<div bgcolor="#ffffff" text="#000000"> I personally like it
being optional and it's still open to debate. But I
recognise the need to have better maintained grammar, that
is more consistent and regular with easy to main
documentation.<br>
<font color="#888888"> <br>
</font></div>
</blockquote>
<div>There's one thing that would help: Make the NT identifiers
in the grammar "user friendly". I had to replace all of them
with NT identifiers that are self-explanatory. Also, whenever
possible, stick to the terms in the Java grammar if it's the
same thing, e.g. "QualifiedIdentifier", "Block", "Expression",
etc.<br>
<br>
-W<br>
</div>
<blockquote class="gmail_quote" style="border-left: 1px solid
rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left:
1ex;">
<div bgcolor="#ffffff" text="#000000"><font color="#888888">
Mark</font>
<div>
<div class="h5"><br>
<blockquote type="cite"><br>
Some rules can be omitted if they coincide with Java's
own rules; just add an explanation.<br>
<br>
-W<br>
<br>
<br>
<div class="gmail_quote"> On 22 September 2010 14:56,
Anstis, Michael (M.) <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:manstis1@ford.com" target="_blank">manstis1@ford.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="border-left:
1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt
0.8ex; padding-left: 1ex;"> What was the service
and was it the ANTLR grammar you uploaded to<br>
generate the images?<br>
<br>
Thanks,<br>
<br>
Mike<br>
<div>
<div><br>
-----Original Message-----<br>
From: <a moz-do-not-send="true"
href="mailto:rules-dev-bounces@lists.jboss.org"
target="_blank">rules-dev-bounces@lists.jboss.org</a><br>
[mailto:<a moz-do-not-send="true"
href="mailto:rules-dev-bounces@lists.jboss.org"
target="_blank">rules-dev-bounces@lists.jboss.org</a>]
On Behalf Of Wolfgang Laun<br>
Sent: 22 September 2010 13:38<br>
To: Rules Dev List<br>
Subject: [rules-dev] Drools syntax diagrams -
redrawn<br>
<br>
I've found this online service and stuffed the
Drools grammar into it.<br>
<br>
You may see the results while they are still
there:<br>
<a moz-do-not-send="true"
href="http://www-cgi.uni-regensburg.de/%7Ebrf09510/syntax.tmp/x45371x0x0x.ebnf.h%0Atml"
target="_blank">http://www-cgi.uni-regensburg.de/~brf09510/syntax.tmp/x45371x0x0x.ebnf.h<br>
tml</a><br>
</div>
</div>
<<a moz-do-not-send="true"
href="http://www-cgi.uni-regensburg.de/%7Ebrf09510/syntax.tmp/x45371x0x0x.ebn%0Af.html"
target="_blank">http://www-cgi.uni-regensburg.de/%7Ebrf09510/syntax.tmp/x45371x0x0x.ebn<br>
f.html</a>><br>
<br>
-W<br>
<br>
<br>
<br>
_______________________________________________<br>
rules-dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:rules-dev@lists.jboss.org"
target="_blank">rules-dev@lists.jboss.org</a><br>
<a moz-do-not-send="true"
href="https://lists.jboss.org/mailman/listinfo/rules-dev"
target="_blank">https://lists.jboss.org/mailman/listinfo/rules-dev</a><br>
</blockquote>
</div>
<br>
<pre><fieldset></fieldset>
_______________________________________________
rules-dev mailing list
<a moz-do-not-send="true" href="mailto:rules-dev@lists.jboss.org" target="_blank">rules-dev@lists.jboss.org</a>
<a moz-do-not-send="true" href="https://lists.jboss.org/mailman/listinfo/rules-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-dev</a>
</pre>
</blockquote>
<br>
</div>
</div>
</div>
<br>
_______________________________________________<br>
rules-dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</a><br>
<a moz-do-not-send="true"
href="https://lists.jboss.org/mailman/listinfo/rules-dev"
target="_blank">https://lists.jboss.org/mailman/listinfo/rules-dev</a><br>
<br>
</blockquote>
</div>
<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>