Path: csiph.com!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail From: Paul Rubin Newsgroups: comp.lang.forth Subject: Re: BBC MicroBit has arrived - which Forth in Python is recommended for now? Date: Mon, 25 Apr 2016 14:23:15 -0700 Organization: A noiseless patient Spider Lines: 15 Message-ID: <87twipjscc.fsf@nightsong.com> References: <840cddee-749a-4aab-9644-4cfe42371840@googlegroups.com> <0e4ead10-f77c-4ca4-b882-42313c482e96@googlegroups.com> <6dcfff29-092b-42be-96e6-8510cd43665d@googlegroups.com> <7fc17e48-1d2c-43c8-aace-bcba3285e70c@googlegroups.com> <2016Apr24.174508@mips.complang.tuwien.ac.at> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: mx02.eternal-september.org; posting-host="6f8cc70e6892455e89d230a40ec2704b"; logging-data="20709"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19RsSqLxB3hwwnlG7ckFeUe" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) Cancel-Lock: sha1:yApwXcj2T0qxDWfi24r18llk3M4= sha1:/rDRtnW+xN9knGMT1LWxRwMp4F4= Xref: csiph.com comp.lang.forth:46763 Andrew Haley writes: > I have never seen separate tasks for send and receive. But you're > quite right, it doesn't work with full duplex. Interesting, wonder why they did it that way, given how lightweight Forth tasks are. > If you want that, you have to do something different. (This is a case > of the more general rule which is not to over-generalize solutions: > just do the simple thing that you need.) I think it's simpler to use two tasks than use extra logic to keep track of which way the port is going, swap directions, etc. I've always done it with two (not in Forth yet though) and it's quite natural.