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: Tue, 26 Apr 2016 02:53:02 -0700 Organization: A noiseless patient Spider Lines: 19 Message-ID: <877ffkk875.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> <87twipjscc.fsf@nightsong.com> <2rSdnc6QpZ-WgILKnZ2dnUU78amdnZ2d@supernews.com> <87bn4wkcvh.fsf@nightsong.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: mx02.eternal-september.org; posting-host="6f8cc70e6892455e89d230a40ec2704b"; logging-data="16987"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/HSV9/N3RysUWzB23MLp/n" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) Cancel-Lock: sha1:zjuEtOcl361XLnObsP1VogPEqp4= sha1:7RTlh/DqCn39OCFjQyYP4Hcc/JM= Xref: csiph.com comp.lang.forth:46775 Andrew Haley writes: > I'm sure it wouldn't, because you don't really think in the Forth way. > Don't speculate! The Forth way seems to be to speculate that full duplex is not needed. I'd rather write something that works all the time, than write something that only works if a speculative presumption happens to come true. I wrote an application fairly recently that talked to a dozen or so devices. I can't remember for sure how many were "really" full duplex since I didn't care. I merely wrote a straightforward wrapper that launched a pair of threads for each device and it handled everything fine. It was almost the first thing I wrote in the program, before I studied much what the individual devices were doing. That set down the API that the later code would use. Why would I worry my beautiful mind trying to analyze whether bidirectional i/o would happen sometime later in the program development? That would be premature optimization.