NetNews Offline 2/NetNews Offline Volume 2.iso/news/comp/sys/amiga/programmer/7130

Internet Message Format | 1996-08-05 | 1.6 KB

Path: god.bel.alcatel.be!nlev00!barnhoorn
From: barnhoorn@nlev00 ()
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Messages vs. Semaphores for external clocking
Date: 10 Apr 1996 07:02:51 GMT
Organization: Alcatel Bell
Distribution: world
Message-ID: <4kfmes$[e-mail]>
References: <4ju349$[e-mail]> <4jvrqs$[e-mail]> <[e-mail]>
Reply-To: barnhoorn@nlev00 ()
NNTP-Posting-Host: 138.203.178.61
X-Newsreader: mxrn 6.18-10


In article <[e-mail]>, [e-mail] (Heinz Wrobel) writes:
>barnhoorn@nlev00 wrote:
>>Use global data, which your subtask fills with the timer-values,
>>and the parent process reads. Disable() and Enable() multitasking
>>when performing such a critical action (reading or writing from the
>>global data). No message port or semaphore needed.
>
>Obviously this is the dumb c0d3r non multitasking solution, i.e.
>plain stupid.
>
.not so obviously. When you have two tasks, and one of them is
collecting data from some source, and the other one needs this data
with regular intervals, I don't see a more easier way to do this
then by using global data and disable/enable multitasking. It is
a very multitasking-friendly solution, and there is nothing
'dumb c0d3r' (whatever that may be) about it.

--
---------------------------------------------------------------------------
Jaco Barnhoorn               [e-mail]
Software Test Engineer       [e-mail]
Alcatel Telecom Systems
Rijswijk, The Netherlands
---------------------------------------------------------------------------