Last call for comments on SRFI 172: Two Safer Subsets of R7RS
Arthur A. Gleckler
(02 Sep 2019 04:28 UTC)
|
Re: Last call for comments on SRFI 172: Two Safer Subsets of R7RS
Lassi Kortela
(02 Sep 2019 07:37 UTC)
|
Evaluating definitions Lassi Kortela (02 Sep 2019 07:38 UTC)
|
Re: Evaluating definitions
John Cowan
(20 Oct 2019 22:11 UTC)
|
Re: Evaluating definitions
(no sender)
(21 Oct 2019 06:37 UTC)
|
Re: Evaluating definitions
John Cowan
(21 Oct 2019 16:51 UTC)
|
Re: Last call for comments on SRFI 172: Two Safer Subsets of R7RS
(no sender)
(02 Sep 2019 08:46 UTC)
|
Re: Last call for comments on SRFI 172: Two Safer Subsets of R7RS
Lassi Kortela
(02 Sep 2019 08:56 UTC)
|
Re: Last call for comments on SRFI 172: Two Safer Subsets of R7RS
(no sender)
(02 Sep 2019 09:09 UTC)
|
Evaluating definitions Lassi Kortela 02 Sep 2019 07:38 UTC
It might be worth clarifying what happens with: (eval '(define foo 1) (environment '(srfi 172))) The SRFI says that it specifies an "*immutable* global environment containing only specified libraries" which hints that trying to define anything in that environment is an error. (From the R7RS definition of eval: "If <expr-or-def> [...] is a definition, the specified identifier(s) are defined in the specified environment, provided the environment is *not immutable*." It'd be good to state this explicitly.