(tu50.txt)
The purpose of tu5 is the discussion of available coding and debugging 
procedures.
Development of j-code for verbs and checking/debugging of j-code is a 
time consuming process especialy for beginners and intermediate programmers.
The availability of the verbs described in J introduction & dictionary
appendix D section B is useful, especially if there is only one or two 
isolated errors. In that condition the debug.js group of verbs is all that"s 
needed.
However personally I like too see all of the code of a verb to be tested
on the screen in such a manner that I can walk through the code and test 
each line one after the other. Also I want to be able to change or correct 
any code found at the spot and continue checking, without having to go 
through the painful process to have to go out of the J session; use an asci 
editor to correct the code of the script file and then return to J. 
In addition if the verb has subverbs,it would be desirable to be able to feed 
the input test data from the mainverb to the subverb and check the subverb out 
in the same session. In that case the mainverb testing should then continue in 
the same session with the testdata output by the subverb, fed back into the 
mainverb at the right location in the code. 
While I have not yet been able to meet all of the above requirements, I am 
getting close. 
The capabilities of the verbs included in files "testof.scr" combined with
"edit.scr" are developed for that purpose and discussed next in this tutorial 
tu5.
