Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!mit-eddie!uw-beaver!rice!news!rich From: rich@Rice.edu (Carey Richard Murphey) Newsgroups: comp.lang.scheme Subject: Re: what makes scheme? Message-ID: Date: 12 Aug 90 05:59:14 GMT References: <9008031618.AA02461@mailhost.samsung.com> <1990Aug5.175401@sprawl.yorku.ca> <1457@tub.UUCP> Sender: news@rice.edu (News) Reply-To: Rich Murphey Organization: Department of Electrical and Computer Engineering, Rice University Lines: 25 In-Reply-To: net@tub.UUCP's message of 9 Aug 90 10:43:47 GMT In article Rich Murphey writes: > I'm curious to know what else is out there that's a minimal > implementation, easy to modify, port, interface with other C code, and > redistribute. As a scheme novice, I am easily overwhelmed by the size > of elk I've had several responses which recomended siod highly. Robert C. Pettengill writes: >This is exactly what SIOD is good for! All the others are much >larger. Although Elk and Jason Coughlin's interpreter are relatively small compared to distribuitions like mit-scheme, siod's under 2000 lines. Neil MacDonald writes: >siod (Scheme in One Day/Defun) is a small, clearly written, easily >ported implementation of a Scheme subset. I have built it on a variety >of Unix-ish systems. I'm still learning scheme, and the simplicity of siod is a great help. The small source size makes the task of understanding the interpreter much more manageable. Rich