info-mac@uw-beaver (info-mac) (08/18/84)
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)
info-mac@uw-beaver (info-mac) (09/26/84)
From: Ed Pattermann <PATTERMANN@SUMEX-AIM.ARPA>
The tohex form of XLISP, mentioned in the Dan Winkler report on Manx C,
is stored on {SUMEX-AIM}<INFO-MAC>XLISP.DL.
-- Ed
-------info-mac@uw-beaver (info-mac) (11/19/84)
From: Peter.Su@CMU-CS-GANDALF I downloaded xlisp and loked over the documentation. it looks interesting, but how do youusave source files?
info-mac@uw-beaver (info-mac) (11/20/84)
From: Mark Cornwell <cornwell@nrl-css> Concerning saving sources... For now, I'm not not saving sources in XLISP. I edit source files with file (you could also use macwrite saving "text only".) Then I quit the file application and start the XLISP application. From XLISP one loads the sources with (load "<filename>"). If your parentheses are balanced, you're ready to go. I prefer file to macwrite for editing sources. It allows multiple windows onto different files -- something I can't live without. Unhappily, it does not allow multiple windows onto the same file. My biggest complaint is the time it takes my little 128k mac to close and open applications in moving back and forth between XLISP and file. This one minute or so delay is a far cry from my beloved Symbolics. I can think of many ways to try to speed this up. Even as is, it compares favorably with the "couple of minutes" I've heard for the current crop of C compliers. Mark Cornwell cornwell@nrl-css