Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!pt.cs.cmu.edu!dsl.pitt.edu!pitt!willett!ForthNet
From: ForthNet@willett.pgh.pa.us (ForthNet articles from GEnie)
Newsgroups: comp.lang.forth
Subject: Forth in the Marketplace
Message-ID: <1536.UUL1.3#5129@willett.pgh.pa.us>
Date: 16 Aug 90 11:47:37 GMT
Organization: String, Scotch tape, and Paperclips.  (in Pgh, PA)
Lines: 29


 Date: 08-14-90 (08:47)              Number: 3648 (Echo)
   To: HANS PIERROT                  Refer#: 3639
 From: JACK WOEHR                      Read: NO
 Subj: PROPER DOMAIN OF FORTH        Status: PUBLIC MESSAGE

 >>       2) Standalone operating system for any type of computer, as
 >>          long as the selected kernel provides for:
 >>               a) premptive as well as round-robin mtasking
 >
 >Jack I am surprised at your comment. After reading your article on 
 >Multitasking in a recent copy of Embedded Systems Progrogramming I 
 >thought that you were of the opinion that pre-emptive multitasking was 
 >not realy neccessary and that round robin would meet most if not all 
 >requirements. Maybe I misunderstood the intent of your article. 

        Oh, I'm all for the roundrobin in control projects ... I can see
 where a pure roundrobin would cause problems on a multiuser system like
 a VAX 11/180 though.

        Recently I designed (but did not build) a multiuser controller
 with a combination of round-robin and pre-emptive multitasking.

                =jax=

 NET/Mail : RCFB Golden, CO (303) 278-0364 VESTA & Denver FIG for Forth!
-----
This message came from GEnie via willett through a semi-automated process.
Report problems to: uunet!willett!dwp or dwp@willett.pgh.pa.us