Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!mcsun!i2unix!inria!mirsa!avahi.inria.fr!colas From: colas@avahi.inria.fr (Colas Nahaboo) Newsgroups: comp.lang.scheme Subject: Re: what makes scheme? Message-ID: <1990Aug10.133859@avahi.inria.fr> Date: 11 Aug 90 11:02:59 GMT References: <9008031618.AA02461@mailhost.samsung.com> <1990Aug5.175401@sprawl.yorku.ca> <1457@tub.UUCP> Sender: news@mirsa.inria.fr Reply-To: colas@avahi.inria.fr (Colas Nahaboo) Organization: Koala Project, Bull Research France Lines: 32 In article <1457@tub.UUCP>, net@tub.UUCP (Oliver Laumann) writes: > 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"? Size of code is not very relevant... the allocated size is MUCH more important, since it can't be shared. Then, when I do a ps -l and I see that elk takes 1600K of memory whereas xscheme only 300, for me xscheme is smaller. Of course, real dump/undump capabilities will make this size a "text" (sharable) size, and will change the picture... Is this the case with Elk? -- Colas Nahaboo, Bull Research France -- Koala Project -- GWM X11 Window Manager colas@avahi.inria.fr Phone: (33) 93.65.77.70, Fax: (33) 93 65 77 66 INRIA - Sophia Antipolis, 2004, rte des Lucioles, 06565 Valbonne Cedex, FRANCE