maclab@reed.UUCP (Mac Lab Login) (02/11/85)
11 February 1985 From: Scott Gillespie, Reed College MacLab Here in the MacLab (as you may have read in an earlier article "Millisecond Timing/ Serial Technology") our primary research goal is to create a sophisticated laboratory environment using the Macintosh as the central control/display device for networks of single-board microcomputers -- multiple windows on the Mac screen take the place of multiple displays on individual laboratory instruments, and flexible 8031-based microcontrollers take the place of the standard instruments found in the lab (oscilloscopes, frequency counters, function generators, etc.). We call these systems 'BenchTop Laboratory Environments.' On the road to this goal, we have designed and written a new language for the Macintosh: Rascal (real-time Pascal). The purpose of Rascal and a brief description of the language follow: In order to draw fast pictures on the Mac, and provide for high speed serial data processing, we needed a language that would compile to 68000 mac code, and support the multi-tasking environment which is to be the foundation of BenchTop systems. We needed built in serial routines, built in fast-graphics routines and we wanted a development system which resided on disk as a single application. In addition to technical considerations, we could not put up with the infinite problems of licensing fees for applications, required by many commerical companies: and we would not wish such annoyances upon anyone else. We looked at most of the products available, and decided that we would only be satisfied with something produced here at Reed, designed specifically for serial/fast-graphics/multi-tasking Rascal is a single application, containing an editor, compiler, linker, and executor (a tiny supervisor-like package is required to run the code, due to Rascal's multi-tasking design). We can now sit down at the Mac, write programs (very much like Pascal), compile, link and test them without ever switching applications. The code produced is extremely fast (it had better be, it's compiled), toolbox routines are supported, and any executable Rascal object may be turned into a stand-alone application. Alpha Testing: Rascal is probably 4-5 months from completion (total cosmetic and documented form) and heavy testing is under way right now. We are forming an Alpha test group for Rascal. If you are interested in participating, please mail me a message to that effect, and include your telephone#. We are looking for people who really want to help us on this, and will expect a lot of feedback on the software (documentation on Rascal is very minimal at this point, so it's a real adventure). We may not be able to include everyone in the Alpha test group, but I hope this won't be the case. Also, I am open to suggestions regarding the mechanics of alpha testing (method, distribution and frequency of updates, new documentation, etc.). We will solidify plans for the Alpha group in about 2-3 weeks: I will try to get back to everyone who responds to this article by that time. Thanks in advance for your advice, and interest. -- Scott Scott Gillespie, MacLab Coordinator Physics Department Reed College Portland, OR 97202 (503) 771-1112 x277 USEnet: ...!decvax!tektronix!reed!maclab Apple E-mail: supt.uc20t