Path: csiph.com!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Paul Rubin Newsgroups: comp.lang.forth Subject: Re: polyForth multitasker question Date: Sat, 15 Apr 2017 17:36:24 -0700 Organization: A noiseless patient Spider Lines: 5 Message-ID: <8737d9fat3.fsf@nightsong.com> References: <8737dcixu5.fsf@nightsong.com> <87vaq7hg4l.fsf@nightsong.com> <6_ydnXUzTNeS523FnZ2dnUU7-THNnZ2d@supernews.com> <2017Apr14.095322@mips.complang.tuwien.ac.at> <2017Apr14.161245@mips.complang.tuwien.ac.at> <2017Apr15.184706@mips.complang.tuwien.ac.at> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: mx02.eternal-september.org; posting-host="104886ca34cb06a03d33248390dbe2ae"; logging-data="6599"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/hwex3kW7141Mwz0A0e06s" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) Cancel-Lock: sha1:WcqlEaw3P0EVEDePbJadDTf6pL8= sha1:S9sKjDfSkRcuJWDVnwBSRJojkJU= Xref: csiph.com comp.lang.forth:57405 anton@mips.complang.tuwien.ac.at (Anton Ertl) writes: at least the O(n log(n)) implementation of looking up the next > task to be woken would probably be overkill. I'd expect O(log n) using a heap as priority queue.