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: Why does the location of PAD move around? Date: Sun, 02 Apr 2017 18:22:59 -0700 Organization: A noiseless patient Spider Lines: 16 Message-ID: <87h9265los.fsf@nightsong.com> References: <20170401210719.376d37f4@_> <1fOdnVjc191fXX3FnZ2dnUU7-YfNnZ2d@supernews.com> <87o9we5mc8.fsf@nightsong.com> <0719e78c-1196-4465-b0a6-a604f3f73b96@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: mx02.eternal-september.org; posting-host="62d9a336d2b9e5ea583f81abcb742873"; logging-data="4454"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/6nKLQOryG8wNmXhBP7rer" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) Cancel-Lock: sha1:k9P1YKZOeV6tTDqTtTMinx8UThM= sha1:snqtynH1YMM+0bwxUSMlQP4jCzk= Xref: csiph.com comp.lang.forth:56611 Julian Fondren writes: >> I'm presuming the tasks all have the same HERE but maybe that's wrong. > Yes. that's wrong. Hmm, ok. Does that mean each task has its own wordlist and dictionary area that threads to a parent dictionary? For some reason I thought Forth's extremely lightweight tasking meant task memory of just the two stacks and a few saved registers. Task locals would come from the main heap. I got this impression from looking at the eForth tasker on Bill Muench's site. Is there any documentation I can find about a traditional Forth multitasker? The full sized Forths these days tend to use OS threads. Brad Rodriguez's articles are tantalizing but not very detailed about this subject.