mo@messy.bellcore.com (Michael O'Dell) (10/10/90)
where can I find a processor for this interesting "expect" language? -Mike
jik@athena.mit.edu (Jonathan I. Kamens) (10/14/90)
In article <27713@bellcore.bellcore.com>, mo@messy.bellcore.com (Michael O'Dell) writes: |> where can I find a processor for this interesting "expect" language? This is the README file from "expect", a program that performs programmed dialogue with other interactive programs. It is briefly described by its man page, expect(1). More examples and further discussion about implementation, philosophy, and design are in "expect: Curing Those Uncontrollable Fits of Interaction" by Don Libes, Proceedings of the Summer 1990 USENIX Conference, Anaheim, California, June 11-15, 1990. expect was designed and written by Don Libes, January - March, 1990. Design and implementation of this program was paid for by U.S. tax dollars. Therefore it is public domain. However, the author and NIST would appreciate credit if this program or parts of it are used. expect may be ftp'd as pub/expect.shar.Z from durer.cme.nist.gov. expect requires Tcl. Tcl may be ftp'd as pub/tcl.tar.Z from ucbvax.berkeley.edu. If not available, a potentially older but working version of Tcl may be ftp'd as pub/tcl.tar.Z from durer.cme.nist.gov. If you cannot ftp, you may request email copies of Tcl by writing to ouster@sprite.berkeley.edu. At this time, I am not distributing expect over email or uucp, however a mail archive server will be available after June 15, 1990. Once you have retrieved the system, please read the INSTALL file. expect is known to work on SunOS 4.0 systems but it does nothing Sun specific and will probably work on most BSD-derived systems. While it has not been compiled on SV or POSIX systems, I have made provisions enough so that probably only minor changes remain. (See the Makefile for more info.) This might be presumptive however, as I recently looked at the process control in gnuemacs and am amazed how much pain it took them to make it portable. Perhaps someday I will change to using their code. I would be willing to work with you to complete a port. Although I can't promise anything in the way of support, I'd be interested to hear about your experiences using it (either good or bad). I'm also interested in hearing bug reports and suggestions for improvement even though I can't promise to implement them immediately. Please send money, love letters, and bug reports to: Don Libes National Institute of Standards and Technology Bldg 220, Rm A-127 Gaithersburg, MD 20899 (301) 975-3535 libes@cme.nist.gov or uunet!cme-durer!libes -- Jonathan Kamens USnail: MIT Project Athena 11 Ashford Terrace jik@Athena.MIT.EDU Allston, MA 02134 Office: 617-253-8495 Home: 617-782-0710