Path: csiph.com!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Paul Rubin <no.email@nospam.invalid>
Newsgroups: comp.lang.forth
Subject: Re: polyForth multitasker question
Date: Wed, 12 Apr 2017 18:02:58 -0700
Organization: A noiseless patient Spider
Lines: 12
Message-ID: <8760i9jf0d.fsf@nightsong.com>
References: <ocafkt$1929$1@gioia.aioe.org> <koGdneROYv-Yg3TFnZ2dnUU7-KvNnZ2d@supernews.com> <ocehe0$19ks$1@gioia.aioe.org> <CM2dnXuhx9lfTnfFnZ2dnUU7-TfNnZ2d@supernews.com> <ocfehb$467$1@dont-email.me> <bIydnby3AqzK03bFnZ2dnUU7-VfNnZ2d@supernews.com> <ocfkhb$8ig$1@dont-email.me> <ochdnu$1r70$1@gioia.aioe.org> <ocile6$7ro$1@dont-email.me> <e11a25dd-5c4c-404e-bbfa-3ec67c7b1d08@googlegroups.com> <2ef60cba-5577-4813-ae93-3946cd4b415b@googlegroups.com> <877f2ql73h.fsf@nightsong.com> <f3ba41b0-66e3-4688-afed-8aebed8f9c49@googlegroups.com>
Mime-Version: 1.0
Content-Type: text/plain
Injection-Info: mx02.eternal-september.org; posting-host="5c6ba07a94a3a9002ee547dbda0699b9"; logging-data="10276"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+aNAO7839rlNX/4o4lka1y"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux)
Cancel-Lock: sha1:uf7oMZxR4Xy5Lr753RTxGOdKSHk= sha1:IDFpwg+6EOMWtrbgterw7EO4f4Y=
Xref: csiph.com comp.lang.forth:57198

foxaudioresearch@gmail.com writes:
>> Do you mean your db would lock up the system til disk i/o had completed?

> "Locking your database" is not accurate when it could be a single
> field write that is the protected if the application allows that.

I still don't understand this.  You need to do some database operation
that involves reading or updating the disk.  Do you mean you wait for
that to complete before your task yields?  Or do you yield leaving the
possibility of another task interfering?  Or do you set some flag
telling other tasks to not mess with the db until the current task is
done with it?  Such a flag is called a "lock" of course.