Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!cbmvax!jesup From: jesup@cbmvax.commodore.com (Randell Jesup) Newsgroups: comp.sys.amiga.tech Subject: Re: More Questions About Using raw/cooked Message-ID: <14464@cbmvax.commodore.com> Date: 14 Sep 90 22:10:15 GMT References: <2570@mcrware.UUCP> Reply-To: jesup@cbmvax.commodore.com (Randell Jesup) Organization: Commodore, West Chester, PA Lines: 28 In article dillon@overload.Berkeley.CA.US (Matthew Dillon) writes: > Use WaitForChar(). Alternately, you can manually construct and send > a READ request to the console handler and construct a replyport for > that request, in which case you get the reply when data is ready. The > downside to this is that there is no way to *abort* the request... you > *must* wait for the request to be fullfilled. So WaitForChar() is the > only supported way of 'polling' the console. Well, I believe the con: device aborts a read request if you attempt to close the filehandle - I think it may even be documented somewhere, but I haven't checked and the memory is vague. In order for this to work, the read request would have had to have been sent asynchronously and with a separate port for it to return to. > Commodore definitely needs some kind of support for asynchronous > abortable requests. Yes. You'll note that Asynch packets are now supported in 2.0, and I hope to get a working AbortPkt into a future version - right now it's a NOP. Unfortunately, it's not so easy to do retroactively - a lot of our design options are limited by compatibility issues. > Matthew Dillon dillon@Overload.Berkeley.CA.US -- Randell Jesup, Keeper of AmigaDos, Commodore Engineering. {uunet|rutgers}!cbmvax!jesup, jesup@cbmvax.cbm.commodore.com BIX: rjesup Common phrase heard at Amiga Devcon '89: "It's in there!"