Path: utzoo!attcan!uunet!decwrl!ucbvax!bloom-beacon!mitech.COM!gjc
From: gjc@mitech.COM
Newsgroups: comp.lang.scheme
Subject: what makes scheme?
Message-ID: <9008031618.AA02461@mailhost.samsung.com>
Date: 3 Aug 90 12:21:27 GMT
Sender: daemon@athena.mit.edu (Mr Background)
Reply-To: gjc@mitech.com
Organization: The Internet
Lines: 25

ted@opus writes:
>... except for the fact that siod is not scheme.  all kinds of things
>are missing.

>better to grab elk or fool's lisp if you want small ones, scheme->c or
>t if you want compiled programs.

Maybe it is possible to have an intelligent discussion about this.
Q: What is Scheme?

What makes something scheme?
What is "all kinds of things are missing" from siod?

For what purposes would elk or fool's lisp be better (than siod)?

How about some concrete examples: Like, here is a type of program
you can run in *x* but not in siod.

True, times are changing. But how? Is it not true that *today*
it is extremely important to have a straightforward interface to
code written in C? (That is, to respect the C calling sequence
by making the Lisp calling sequence the *same* as the C calling
sequence/conventions).

-gjc