Unmaintained implementations Antero Mejr (13 May 2024 14:25 UTC)
Re: Unmaintained implementations Arthur A. Gleckler (13 May 2024 14:39 UTC)
Re: Unmaintained implementations Lassi Kortela (13 May 2024 15:17 UTC)
Re: Unmaintained implementations Lassi Kortela (13 May 2024 17:46 UTC)
Re: Unmaintained implementations Antero Mejr (13 May 2024 18:05 UTC)
Categorizing and describing implementations Lassi Kortela (13 May 2024 18:24 UTC)
Re: Categorizing and describing implementations Jakub T. Jankiewicz (13 May 2024 20:16 UTC)
Re: Categorizing and describing implementations Arthur A. Gleckler (13 May 2024 20:23 UTC)
Re: Categorizing and describing implementations Lassi Kortela (13 May 2024 20:37 UTC)
Re: Categorizing and describing implementations Arthur A. Gleckler (13 May 2024 20:39 UTC)
Re: Categorizing and describing implementations Jakub T. Jankiewicz (13 May 2024 21:19 UTC)
Re: Categorizing and describing implementations Arthur A. Gleckler (13 May 2024 21:26 UTC)
Containers Lassi Kortela (13 May 2024 21:37 UTC)
Re: Containers Arthur A. Gleckler (13 May 2024 21:41 UTC)
Re: Categorizing and describing implementations John Cowan (13 May 2024 21:51 UTC)
Re: Categorizing and describing implementations Stephen De Gabrielle (14 May 2024 08:23 UTC)
Re: Categorizing and describing implementations Jakub T. Jankiewicz (14 May 2024 11:55 UTC)
Snap and Lisp Lassi Kortela (14 May 2024 12:15 UTC)
Re: Snap and Lisp Stephen De Gabrielle (14 May 2024 12:45 UTC)
Re: Snap and Lisp Lassi Kortela (14 May 2024 13:33 UTC)
Re: Categorizing and describing implementations Marc Feeley (14 May 2024 12:48 UTC)
Re: Categorizing and describing implementations Stephen De Gabrielle (14 May 2024 13:09 UTC)
Re: Categorizing and describing implementations Marc Feeley (14 May 2024 13:29 UTC)
Re: Categorizing and describing implementations Jakub T. Jankiewicz (14 May 2024 14:03 UTC)
Re: Categorizing and describing implementations Stephen De Gabrielle (14 May 2024 17:45 UTC)
Re: Categorizing and describing implementations Lassi Kortela (19 May 2024 13:47 UTC)
Re: Categorizing and describing implementations Antero Mejr (20 May 2024 14:03 UTC)
Re: Categorizing and describing implementations Arthur A. Gleckler (20 May 2024 14:24 UTC)
Definition of "Scheme" Lassi Kortela (14 May 2024 13:21 UTC)
Re: Categorizing and describing implementations Jakub T. Jankiewicz (14 May 2024 13:53 UTC)
Re: Unmaintained implementations Arthur A. Gleckler (13 May 2024 19:12 UTC)
Re: Unmaintained implementations Jakub T. Jankiewicz (13 May 2024 20:40 UTC)
Re: Unmaintained implementations Arthur A. Gleckler (13 May 2024 20:43 UTC)
Re: Unmaintained implementations Lassi Kortela (13 May 2024 20:49 UTC)
Re: Unmaintained implementations Arthur A. Gleckler (13 May 2024 20:55 UTC)
Re: Unmaintained implementations Lassi Kortela (13 May 2024 21:07 UTC)
Re: Unmaintained implementations Antero Mejr (13 May 2024 21:18 UTC)
Metadata files Lassi Kortela (13 May 2024 21:34 UTC)
Re: Metadata files Antero Mejr (13 May 2024 21:41 UTC)

Re: Unmaintained implementations Lassi Kortela 13 May 2024 20:49 UTC

> It doesn't support continuations, TCO, and libraries, but it support
> everything else from R5RS and a lot of R7RS (some functions need upgrade
> to include multiple arguments that were not in R5RS). It should at least be
> marked as "partial support". I know that TCO is fundamental for Scheme, but
> the same is syntax-rules that not all implementation have.
>
> But if you decide that it should be marked as "not supported" or something
> similar, I think it would be better than not being included.
+1

There are people who insist that continuations, full TCO, hygienic
macros, or complete RnRS support should be the criterion for something
to be called "Scheme". But ask one of these people and you get a
different answer than from the others. In practice, being that strict
will never work.

The fact is that a Scheme with no continuations, unhygienic macros, and
TCO only in "named let", can be perfectly useful.

Hygienic macros can be implemented almost everywhere without lossage;
they are only a matter of effort. Full TCO and continuations (beyond
escape procedures) are hard to do with good performance and
compatibility on foreign virtual machines like JavaScript, JVM, or CLR,
and the benefits for real world programs are not major.