It's always been a mystery to me why it is OK to spend several hours (or sometimes days) analyzing several pages of FORTRAN or C but when reading a few lines of APL or J which do the same thing I must grasp it in a few minutes or I start feeling overwhelmed. But I have written similar "run-ons". Why? Because I can set up test data and add a little at a time to a line or a few lines, executing it and looking at the results as I go. I have to force myself to break that monster up into more readable chunks. I can't do that in other languages as I have to compile or whatever, So I tend to write all the code then start debugging.
Then comes documenting. I put a brief description of what it's for and expected arguments. Then add references and why the code does what it does. I try not to repeat describing what the code does. But then I end out with comments many time larger than the code. That just seems weird! ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
