Hi Mark,<br><br>here now:<br><br>Ooh, it seems Eclipse outwitted me once again. But I think I
made it on the 2nd try...<br>
-W<br>
<br>
PS: <br>
(1) A decision on the matter of DSL variables would be
appreciated. I'm currently<br>
developing a non-trivial DSL, and learning a lot about what's
needed for a<br>
<i>real world </i>application. Most importantly, some means of
structuring the<br>
DSL definition, so that they can be applied distinctively to
specific groups of<br>
rules. This reduces the risk of "ricochets" if you know what I
mean. <br>
<br>
I've thought about proposing an entirely new approach, based on
DRL syntactic<br>
entities, i.e., the expansion of a DSL phrase must be a "medium
level" non-terminal<br>
of the DRL language. But this certainly restricts phrase
parameters to terminals.<br>
If it's too sophisticated, you end up with a parser/compiler
almost as nasty as ANTLR3.<br>
<br>
(2) I haven't forgotten the spreadsheet fixes. There's another
relic I found: some of<br>
the column keywords have single letter alternatives (e.g. "U"
for "no-loop", "X" for<br>
"activation-group"). Should I retain them - they are NOT
documented in Expert.<br>
<br>
Should I add timer(int:)? Duration is deprecated, I'll leave
this in but it ought to<br>
be marked clearly as such in the documentation, at least.<br>
<br>
Please advise - I can live with everything - non of this is
important for my company,<br>
but I want to get the fixes and additions out of my thinning
hair ;-)<br>
<br>