On 6/2/07, R.A. MacDonald <[EMAIL PROTECTED]> wrote:
Exactly. Test-first works wonders here. A verb that passes by without being tested can fester and be nasty to sort out.
Ok, but that wasn't the question which was asked. Also, I can think of several ways where testing can fall down, for example, when a session contains a definition which script does not, but the script relies on that definition. Copy and paste error can also be frustrating. Or, more generally: debugging someone else's code can get tedious sometimes. I can also imagine other scenarios where a little extra detail about undefined words in the session could be handy -- even if it does nothing for explicit verbs. Anyways, limited use techniques are not the same as useless techniques. That said, another useful technique for finding undefined tacit verbs is to bring up the debugger, and look at a stack trace. This will identify the verb whose definition contains the reference to the undefined verb. For example, with: a=:b + c b=: * c=: d * e d=:%: e=: f - ] a 3 |value error: f | a 3 -- Raul ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
