Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!snorkelwacker!ira.uka.de!fauern!tub!net From: net@tub.UUCP (Oliver Laumann) Newsgroups: comp.lang.scheme Subject: Re: what makes scheme? Message-ID: <1457@tub.UUCP> Date: 9 Aug 90 10:43:47 GMT References: <9008031618.AA02461@mailhost.samsung.com> <1990Aug5.175401@sprawl.yorku.ca> Reply-To: net@tub.UUCP (Oliver Laumann) Organization: Technical University of Berlin, Germany Lines: 24 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 Speaking about Elk, do you really think that 8000 lines of C code is large for a Scheme implementation that supports bignums, call/cc, dynamic loading of .o-files and "dump"? Any implementation I have seen so far that claims to be "small" (SIOD, XScheme, ...) supports at most one of these. Note that the size of Elk's bignum implementation alone makes up 10 percent of the entire size. > and even Jason Coughlin's interpreter, and I wouldn't even > think about trying to port them to ms-dos. Guess what I'm doing right now. Our local DOS guru says "No problem!", but I'm not so sure... :-) Regards, -- Oliver Laumann, Technical University of Berlin, Germany. pyramid!tub!net net@TUB.BITNET net@tub.cs.tu-berlin.de