On Wed, 9 Apr 2014 19:07:27 +0200 big stone <stonebi...@gmail.com> wrote:
> Threading Plumbery is managed via DOS ".bat commands, as below : > - a "main.bat" dos command : > . pre-clears the 4 "ok finished" files, > . launch the 4 threads, > . then check every 2 seconds that all "ok finished" files are > generated. > - a "test_sqlite_this.bat" command launcher was necessary to pass > parameters for each sqlite session, ... > rem each thread is writing a "ok" file after it outputed its 1/4th of > big result ... > start cmd /C "%~dp0test_sqlite_this.bat" %sqlite% > test_sqlite3_script_v30_0.txt zout_sqlite_v30_0ok.txt debug > start cmd /C "%~dp0test_sqlite_this.bat" %sqlite% > test_sqlite3_script_v30_1.txt zout_sqlite_v30_1ok.txt nodebug ... I think it bears mentioning that "start cmd /c" starts a separate *process*, each in its own address space, each with its own file descriptors. Calling them threads is technically accurate -- every process is 1 or more threads -- but misleading because it implies issues that don't exist between distinct processes. --jkl _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users