Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!news.stack.nl!aioe.org!.POSTED!not-for-mail From: "Rod Pemberton" Newsgroups: comp.lang.forth Subject: Re: What for Break Key No Work? Date: Fri, 25 Jul 2014 16:56:21 -0400 Organization: Aioe.org NNTP Server Lines: 35 Message-ID: References: <5b562e18-08c0-4d57-8134-c56682cc95da@googlegroups.com> <0a8998a8-09f8-46fb-bec9-bebbdfebe1fa@googlegroups.com> <2014Jul25.125044@mips.complang.tuwien.ac.at> <5JCdndHx1dFQ-k_OnZ2dnUVZ8jmdnZ2d@supernews.com> NNTP-Posting-Host: CNsg4fVcCsvs3UaOgZtQCw.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org User-Agent: Opera Mail/12.16 (Linux) X-Notice: Filtered by postfilter v. 0.8.2 Xref: csiph.com comp.lang.forth:32659 On Fri, 25 Jul 2014 10:21:01 -0400, Andrew Haley wrote: > Anton Ertl wrote: >> Andrew Haley writes: >>> bruce.mcfarling wrote: >>>> Doing it with an interrupt seems a more natural approach, if >>>> available. >>> >>> Indeed it is, but you have to guarantee that at every point it's >>> possible to abort without breaking something. >> >> That's quite an effort. > > It is the simplest correct solution of which I know, which is why I > mention it here. In general, asynchronous exceptions are a hard > problem. > Um... Why isn't the host OS for SwiftForth sending a signal to the main Forth app upon receiving a Ctrl-C, Ctrl-Break, etc? Shouldn't the host OS be doing so? ... SwiftForth should only be getting keyboard input after it has been processed by the host OS. SwiftForth shouldn't be reading the hardware directly. I.e., offhand, I would guess that SwiftForth is ignoring or blocking something. Rod Pemberton