Re: [racket-users] R6RS history

2019-02-28 Thread Matthias Felleisen
> On Feb 27, 2019, at 1:42 PM, Arthur Nunes-Harwitt wrote: > > Dear Matthias, > > Would you be willing to share your thoughts about the history of > denotational versus operational semantics in the report? [[ This is probably totally off topic for the list. ]] Denotational semantics emer

Re: [racket-users] R6RS history

2019-02-27 Thread Arthur Nunes-Harwitt
Dear Matthias, Would you be willing to share your thoughts about the history of denotational versus operational semantics in the report? Thanks. == Arthur Nunes-Harwitt Computer Science Department, Rochester Institute of Technolo

Re: [racket-users] R6RS history

2019-02-27 Thread Will Jukes
This question has been burning me up as well. On Tue, Feb 26, 2019 at 4:16 PM Matthias Felleisen wrote: > > > Let me inject some comments that make it a bit more obvious what’s > happening here: > > > > On Feb 26, 2019, at 3:33 PM, Sam Tobin-Hochstadt > wrote: > > > > RnRS meetings from 1984 th

Re: [racket-users] R6RS history

2019-02-26 Thread Matthias Felleisen
Let me inject some comments that make it a bit more obvious what’s happening here: > On Feb 26, 2019, at 3:33 PM, Sam Tobin-Hochstadt wrote: > RnRS meetings from 1984 thru 2003 adhere to the “unanimity rule” originating from the MIT group. In 2001, I created and ran “Scheme and Functio

Re: [racket-users] R6RS history

2019-02-26 Thread Sam Tobin-Hochstadt
I think a genuinely detailed accounting of this has to wait for a conversation over beer, but: 2003: New Scheme Standard proposed at the Scheme Workshop 2006: First draft of R6RS released 2007: R6RS Ratified by community vote after extensive discussion and revision 2009: A new Scheme Standard stee

[racket-users] R6RS history

2019-02-26 Thread Jack Firth
What exactly is the history surrounding scheme, racket, and r6rs? I've gotten vague impressions of serious scheme community conflicts around that time but nothing specific. Does anyone have a timeline of important events related to that? -- You received this message because you are subscribed to