Using timers like that is somewhat "old fashioned", it has the disadvantage that it "mixes" all your timers in a single handler. Using tickAction's (and delayCall for one shots) has a more direct handler approach: clauses new() :- applicationWindow::new(), generatedInitialize(), ...

Unfortunately, that dream will not come through. Interfaces define the interface of objects the implementation is written in the implementation. Also recall that though you think of a class and interface together, a single interface can be used for many classes. Likewise a class defines the "in...

Regarding string: I didn't supply a value. I assumed it would work since that worked for integer, etc.

Well, I have two "problems" with this suggestion. First of all it is a strict rule that implementation details are written in the implementation; interfaces only defines the interface. Secondly, the suggested auto code has exactly the same effect as implementing the property with a fact: i...

I think you should use the sciLexer instead of an edit control. So I have update a few files.
I have problems with string properties.

You should also notice that auto-formatting will write the code differently.

Ok .

Ok.

In future releases the sciLexer will have these key binding predicates, where the three last ones are new: predicates assignCmdKey : (unsigned KeyDefinition, integer SciCommand). % This assigns the given key definition to a Scintilla command identified by sciCommand. % sciCommand can be any SCI_* co...

In the sciLexer itself you can assign sciLexer -built-in actions to keys. But to perform your own custom commands you will need to handle the keypress before it reaches the sciLexer . We have done that in a "hard coded" fashion to deal with the tab mechanism we want(ed). I think it makes s...

Sorry, I overlooked some details .

The second argument of assignCmdKey is a command (sciLexer_native::sci_...) not a key:

It is a bug. Actually, this bug turns up over and over in different contexts, but I guess that it will eventually be solved for all contexts. The usual work-around also helps in this case. Redefine your domains like this: domains repDomain{T} = repDomain(arrayM{T} ArM, recoverableState State). And c...

Also, a few notes on your library: In many ways an interesting data structure. But ... :-) It seems to me that the "more" abstract data type you are "actually" implementing is something like this: interface chain{@Data} predicates insertBefore : (@Data Reference, @Data Data). % p...

Well, that was a lot. Not sure I fully get everything. Before I go into details, I can tell you the conclusion: you have not changed my view on the matter. Regarding "analysis" in the compiler. Implementing this as a hook into the runtime system instead of making this a first-class languag...

Our show predicate for the sciLexer makes the following settings: tabWidth := 4, tabIndents := true, backSpaceUnIndents := true, useTabs := false, If you want to change any of them, you will have to change the settings after show has run: mySciLexer_ctl:addShowListener( { :- mySciLexer_ctltabWidth :...

We do not have such a syntax. But you can use a list comprehension like this: