News for hackers. Stuff that matters.

A comment on How did Ruby and Python prevent fragmentation while ML and Lisp did not?. Parent comment

Re:How did Ruby and Python prevent fragmentation while ML an... by groovy2shoes on Sunday May 06, 2012 @11:10PM (#3937404)
Racket didn't opt out of R6RS. Racket has multiple language modes, one of which is actually R6RS Scheme. It also has a "legacy mode" for R5RS, along with modes for a handful of other languages such as Datalog, ALGOL 60, and some teaching languages.
[ Parent | on HN ]
Re:How did Ruby and Python prevent fragmentation while ML an... by masklinn on Monday May 07, 2012 @02:13AM (#3937839)
> Racket didn't opt out of R6RS.

That definitely isn't what I wrote.

[ Parent | on HN ]
Re:How did Ruby and Python prevent fragmentation while ML an... by groovy2shoes on Monday May 07, 2012 @07:25AM (#3938529)
Sorry, not sure what else to make of this:

> There are even implementations (e.g. DrRacket, formerly DrScheme) which forked/opted out the whole language.

[ Parent | on HN ]
Re:How did Ruby and Python prevent fragmentation while ML an... by klez on Monday May 07, 2012 @08:47AM (#3938741)
They opted out from scheme as a whole.

This is reflected by the name change.

http://www.racket-lang.org/new-name.html

[ Parent | on HN ]
Re:How did Ruby and Python prevent fragmentation while ML an... by groovy2shoes on Monday May 07, 2012 @10:37AM (#3939148)
I'm familiar with the name change, but they didn't opt out of Scheme at all. Racket still supports both R5RS and R6RS. And before someone starts going on about the "default language" not being Scheme anymore, Racket doesn't have a default language. You have to specify one. Many of the things that have been added to Racket beyond the Scheme standard also have analogs in other Scheme systems.
[ Parent | on HN ]