greg heil wrote: > If i knew it would crash, i wouldn't do it;-) Also the ijs window > lacks a line stack for trying variations so it is not really where one > would like to have the inner loop of coding. i tend to treat it as > where i put the final results, so i can resume the next day etc. Thus > it lacks the latest fragments.
I don't think it good practice to develop code in ijx, and use ijs only for storing the code. This might work for trivial code fragments but would quickly bog down for larger systems. The J IDE makes working with scripts pretty easy. Project Manager can organize them, and a click of the Test button, or running a test script from a programmed function key, can save all open scripts, then run your application. That all open scripts can be automatically saved makes it crash-proof. The debugger can then let you step through the function you are working on. I believe that time spent learning the IDE will be quickly repaid in improved productivity. At least, you don't have to reinvent the wheel. ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
