On Thu, Oct 10, 2019 at 3:37 PM 'Jim Russell' via General <[email protected]> wrote: > I'm from the old "code, keypunch, test, repeat" school. With J, I'm more > "Discover, try, fail, investigate, study, get distracted, jump down rabbit > holes, capture an expression in a script, repeat. " > > For those who have achieved some level of profanity (I tried to swipe the > word "productivity", but either might work), how do you mix using the > execution window, the log, and the script editor to end up with a working J > application? > > (BTW, is it just me, or is the whole internet dying today?)
It's not just you, and it's not just today. But that's more an issue for the chat forum. That said, once upon a time, for a variety of programming languages, software development involved frequent reboots and crashing was a typical runtime error symptom. Anyways, ... for script development, I usually use control-S, control-L with echo statements for things I want to keep an eye on and occasional "use globals so I can temporarily comment out slow lines" if the script takes a long time to execute. This usually gets me near where I want to be, but I need to spin up a separate J session and try running it there (usually copying and pasting the load statement does the trick) to make sure I've not overlooked something important. Thanks, -- Raul ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
