Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!rpi!batcomputer!riley
From: riley@batcomputer.tn.cornell.edu (Daniel S. Riley)
Newsgroups: comp.sys.amiga.tech
Subject: Re: window/event/conman questions
Message-ID: <9403@batcomputer.tn.cornell.edu>
Date: 9 Dec 89 15:11:32 GMT
References: <29800002@inmet> <4688@sugar.hackercorp.com> <6377@stsusa.com> <4699@sugar.hackercorp.com> <6447@stsusa.com>
Reply-To: riley@tcgould.tn.cornell.edu (Daniel S. Riley)
Organization: Cornell Theory Center, Cornell University, Ithaca NY
Lines: 25

In article <6447@stsusa.com> jellson@stsusa.com writes:
>In article <4699@sugar.hackercorp.com>, peter@sugar.hackercorp.com (Peter da Silva) writes:
>> I thought ConMan was a straight drop in for CON:, just like NEWCON: is. If
>> that's the case, why wouldn't you have access to it from Xlisp?

>	You clearly know much more than I do about this topic so forgive me if
>I am all screwed up here.  I messed around with XLISP (can't remember version
>number) for some time trying unsuccessfully to get CONMAN to work with it and
>I thought the reason it didn't work was because it used the RAW: device for
>console I/O.

This is true.  Back in the XLISP days, David Betz was into processing raw
keyboard events himself.  XLISP opened its own raw: window, did all the
keyboard processing for line editting, and periodically polled the keyboard
for input to see if any interrupt characters had arrived.

Since then, judging from the XSCHEME code, he's decided that at least on
some systems (e.g. Unix), it's ok to let the system worry about those things.
I don't know if the amiga interface for XSCHEME uses raw:, since I've never
seen the amiga code--I use the unix code, which doesn't do anything strange,
and is trivial to port to any C compiler that has a decent io library and
signal().

-Dan Riley (riley@tcgould.tn.cornell.edu, cornell!batcomputer!riley)
-Wilson Lab, Cornell University