🚀 go-pugleaf

In article <ROCKWELL.92Apr9231849@socrates.umd.edu>, rockwell@socrates.umd.edu (Raul Deluth Miller-Rockwell) writes:
|> [...]
|> define a set of arbitrary assertions (about code and data, e.g. x is
|>  a member of the set 5, 6, 7, 9)
|> trace execution until an assertion fails
|> allow programmer to modify program
|> allow programmer to continue execution from present location, or after
|>  backtracking, if desired.

I can do that with any language with explicit run-time tests.  Which
is what I assume you must do with J. 

|> [...]
|> The advantage of an interactive session is that you don't have to
|> go through the process of writing programs to solve simple problems.

Ok.  I'll consider J for simple problems.  But it's hardly worth 
learning such an obscure language for such applications.  And the
interaction you covet is a definite liability for large-scale 
programming tasks.

|> [...]
|> Note that if you use access "functions" (verbs) for your global
|> variables you get similar properties.

How do you denote simple variables as functions without paying a
severe run-time penalty?

J. Giles