Am Do., 8. Sept. 2022 um 01:48 Uhr schrieb John Cowan <[email protected]>:
> 1) The word "contributions" suggests "original contributions". Change to > "topics" or "concepts". > Changed to "topics". > > 2) "the former be implemented": insert "can" > Done. > > 3) 4.2 first sentence: insert comma after "standards" > Done. > > 4) 4.4 insert comma after "without space leaks" > Done. > > 5) 4.4 for "in favor of" read "instead of" > Dito. > > 6) 4.4 for "reset/shift" read "reset and shift" (looks like a single > operator) > Likewise. > > 7) (Non-editorial) Rather than overloading `equal?`, introduce new > equivalence relations `continuation-prompt-tag=?`, > `continuation-prompt-key=?`, and `thread-local=?`. > `equal?` is not really overloaded; here I just want to point out that a new prompt tag/thread local is created and that `equal?` is fine enough to detect "newness". It's like saying that the results of two invocations of, say, `cons`, are not `eqv?`. In particular, I want that `eq?`, `eqv?`, and `equal?`-bases hash tables can be used when the keys are continuation prompts or thread locals. > > 8) Italics: Article titles should be in double quotes, not italics. > R6RS, R7RS , and SRFI nnn should not be in italics. > I use the <cite> element of HTML to mark R6RS, R7RS, etc., which seems to be semantically the correct choice by the definition of the <cite> element in the HTML standard. The browser's default CSS renders it in italics. I can add an extra rule in the CSS included in the SRFI document but I don't think it is that important. > 9) Add a note that %call-with-current-continuation is the R4RS procedure > call-with-current-continuation. > > > Done. Thank you a lot for your careful and valuable reading.
