<!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">
It's not so much imperative/declarative but that if indictes its part
of a sequence of logic, when is more atomic - but it is contrived :)<br>
<br>
Michael Neale wrote:
<blockquote
cite="mid:96ab3ced0702261536h7c6f82e1pe0fb5d6ba55cf40d@mail.gmail.com"
type="cite">yes its only a tool thing, exactly. purely for the UI, so
it can say whatever we want. <br>
<br>
"When" is OK with me - but I am not sure if the argument of if ==
imperative vs. when == declarative is the best - it may make sense to
new users, but it does sound a little contrived to me (I always cringed
at the explanation). <br>
<br>
I guess pragmatically speaking: Java, C, C#, C++, perl, python, ruby
all have "if" but not "when" - given they are the most common
imperative languages, using "when" probably makes good sense as a
differentiation point now I think of it.
<br>
<br>
The Rule Modeller localisation mainly comes down to i18n style
.properties files anyway - whereas DSL is user customisable - but we
could make it use a DSL file eventually. <br>
<br>
basically, platofrm i18n will eventually be done by engineering
services here, but it will really be based on user demand, whereas DSL
allows users to do what they want when they want. <br>
<br>
<div><span class="gmail_quote">On 2/27/07, <b
class="gmail_sendername">Edson Tirelli</b> <<a
moz-do-not-send="true" href="mailto:tirelli@post.com">tirelli@post.com</a>>
wrote:</span>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
Mark,<br>
<br>
Yes, from a DSL Compiler perspective, keywords are customizable. But<br>
from tools perspective, they need to add support to that. Also, I think<br>
Michael is generating DRL directly from the editor, aren't you Mic? So
<br>
this is only a tool thing...<br>
<br>
[]s<br>
Edson<br>
<br>
<br>
Mark Proctor wrote:<br>
<br>
> Is using 'if' and 'when' confusing? should be not standardise over
it?<br>
><br>
> I think "when" is used as you say "when this then that" not "when
this
<br>
> maybe this or maybe that else that", where as if/else is a common<br>
> usage - so helps emphasis that rules are more atomic.<br>
><br>
> With Edson's work is this not all localisable now anyway? If so,
need
<br>
> to make sure that the guided editors obey his keyword localisation
work.<br>
><br>
> Mark<br>
> Michael Neale wrote:<br>
><br>
>> no, it was just to be different. It can be anything. It can be<br>
>>
<br>
>> "wassup" or something ;)<br>
>><br>
>> Not sure if that explanation has any real meaning, I mean it
makes a<br>
>> point, but "when" actually implies to me that it is slightly
temporal
<br>
>> (ie "when" means it will happen, at some point in time, where
as "if"<br>
>> means it may or may not happen - neither of which are<br>
>> procedural/imperative).<br>
>><br>
>> I think its ok to say IF, as people still say "if/then" for
<br>
>> production rules, its not really confusing - perhaps we need
another<br>
>> way to explain imperative versus declarative.<br>
>><br>
>> On 2/26/07, *Mark Proctor* <<a moz-do-not-send="true"
href="mailto:mproctor@codehaus.org">
mproctor@codehaus.org</a><br>
>> <mailto:<a moz-do-not-send="true"
href="mailto:mproctor@codehaus.org">mproctor@codehaus.org</a>>>
wrote:<br>
>><br>
>> I noticed that 'if' is used in the guided editor instead
of
<br>
>> 'when', whats the reason for this? As currently I explain
the use<br>
>> of 'when' because it indicates its not procedular, where
as 'if'<br>
>> is considered part of a procedural logic flow. Will this
confuse
<br>
>> that explanation?<br>
>><br>
>><br>
>><br>
>> Mark<br>
>><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>
<mailto:<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">
https://lists.jboss.org/mailman/listinfo/rules-dev</a><br>
>><br>
>><br>
>>------------------------------------------------------------------------<br>
>><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">https://lists.jboss.org/mailman/listinfo/rules-dev
</a><br>
>><br>
>><br>
><br>
>------------------------------------------------------------------------<br>
><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">https://lists.jboss.org/mailman/listinfo/rules-dev</a><br>
><br>
><br>
<br>
<br>
--<br>
Edson Tirelli<br>
Software Engineer - JBoss Rules Core Developer
<br>
Office: +55 11 3124-6000<br>
Mobile: +55 11 9218-4151<br>
JBoss, a division of Red Hat @ <a moz-do-not-send="true"
href="http://www.jboss.com">www.jboss.com</a><br>
<br>
<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">https://lists.jboss.org/mailman/listinfo/rules-dev</a><br>
</blockquote>
</div>
<br>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
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>