Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10 UW 5/3/83; site uw-beaver Path: utzoo!watmath!clyde!burl!ulysses!mhuxl!ihnp4!houxm!houxz!vax135!cornell!uw-beaver!info-mac From: info-mac@uw-beaver (info-mac) Newsgroups: fa.info-mac Subject: XLISP Message-ID: <1502@uw-beaver> Date: Fri, 17-Aug-84 19:31:28 EDT Article-I.D.: uw-beaver>.1502 Posted: Fri Aug 17 19:31:28 1984 Date-Received: Sun, 19-Aug-84 03:26:13 EDT Sender: daemon@uw-beave Organization: U of Washington Computer Science Lines: 41 From: chavez@harvard.ARPA (R. Martin Chavez) I've been working on a stdio package for the Mac; it works reasonably well, but I haven't fully tested it yet. I have implemented the binding of suitable enhanced _iobuf structures to Macintosh windows; all the normal stdio operations are supported. The application agrees to call a Listen routine very often; Listen handles all the usual update, activate, mouse-down, and key-down events. Intelligent scroll-bar support is included. Listen will deal with windows that have an associated FILE pointer; other windows are handled by user-specified routines. The implementation details are rather complicated and I don't want to make any promises until the package is ready for release, but I do have a couple of questions: (1) I modeled many of my event-handling routines after the FILE code given as an example program in Inside Mac. Has anyone out there noticed that the whole input line flashes when you hold a key down? It looks like everything from the line start to the character that's just been TEKey'ed gets updated. The effect is particularly annoying when one tries to backspace repeatedly (by holding the key down.) Am I doing a spurious TEUpdate? Does anyone know exactly which TextEdit routines generate update events, and which parts of the window are bundled into the update region? (It seems that TextEdit is causing the whole line to be re-drawn, not just the last position.) MacWrite doesn't exhibit that flashing behaviour. (2) I am fiddling with a Macintosh implementation of XLISP, the minimal object-oriented Lisp interpreter released on net.sources a while back. I haven't done a thorough investigation yet, but here's the bug: XLISP launches without incident, sets up the interpreter window, and cogitates for a couple of seconds. Then I hear the infamous bell and the system reboots WITHOUT GIVING ME THE USUAL ALERT BOX. Does anyone have any suggestions? Thanks, R. Martin Chavez (chavez@harvard.ARPA)