Re: yet again, lisp vs. scheme

Mike wrote: 
I like the scheme implementations that are to me small (plt)
and do not take up a lot of resources. The books and articles
I find deal more with lisp.

What is a smaller lisp implementation that runs on both
gnu/linux and windows?

You don't say what you mean by small. Do you mean "doesn't use a lot of memory" or do you mean "I don't want to learn the language all at once".

For the first meaning, there are implementations like clisp that tends to be compact and ECL whose purpose is to be embedded. For the second meaning, it's good to pick a tutorial that matches your interests and/or your learning speed. Good tutorials present the material in easily digestable steps. Keep in mind that "real" Scheme systems are also quite large when you want to take advantage of everything they provide.


Pascal

--
2nd European Lisp and Scheme Workshop
July 26 - Glasgow, Scotland - co-located with ECOOP 2005
http://lisp-ecoop05.bknr.net/
.

Relevant Pages

  • Re: An ode to Erlang
    ... I thought you were familiar with Lisp macros. ... Erlang has processes. ... > Why do you think you need to rewrite the Lisp implementation? ...
    (comp.lang.lisp)
  • Re: An ode to Erlang
    ... I thought you were familiar with Lisp macros. ... You had gone on to suggest that objects only cross process boundaries ... Why do you think you need to rewrite the Lisp implementation? ...
    (comp.lang.lisp)
  • Re: Request for comment: follow-up to Summer of Code
    ... One is that a good lisp implementation produces code ... >produced by a good C compiler, ...
    (comp.lang.lisp)
  • Re: Smug scheme weenies?
    ... > I didn't know all of the folks involved, but I can't imagine that ... That's Olin Shivers talking about the history of T (the Lisp dialect), ... dynamically scoped and his exact reply was that lexical scope was ... experts in the area of lisp implementation, ...
    (comp.lang.lisp)
  • Re: CL failure stories?
    ... Thomas, at the end of the day your Lisp implementation only provides more ... I believe this benchmark hits a weak point of Lisp. ...
    (comp.lang.lisp)