IIRC J, being a single thread process, just cannot breath once in a while and then resume running without terminating and returning control to os. However it should be doable to divide the job into several smaller ones and running one job and then finish and then the user press a button to running the second job, etc. Does it justify the effort for fif?
Птн, 22 Окт 2010, Björn Helgason писал(а): > If you for example write every hit into a file you do not have to lose the > results even if the program brakes because of something like running out of > memory because the file is still there. > > If the programs stops once in a while to ask the user for confirmation if it > should continue it is possible to make it stop then and there. > > You can put a control mechanism on top of the search that decides how > long/much the program should search and at the start it can see how many > files to search how big they are etc and then come up and breath once in a > while to see if it should go on or not. > > You can thus have different criteria for the program if the search material > is big or small. > > 2010/10/22 bill lam <[email protected]> > > [---=| TOFU protection by t-prot: 26 lines snipped |=---] > -- regards, ==================================================== GPG key 1024D/4434BAB3 2008-08-24 gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3 ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
