|
Re: [Scheme-reports] REPL
Helmut Eller
(14 Nov 2012 08:51 UTC)
|
|
Re: [Scheme-reports] REPL
Alex Shinn
(14 Nov 2012 09:07 UTC)
|
|
Re: [Scheme-reports] REPL
Helmut Eller
(14 Nov 2012 09:13 UTC)
|
|
Re: [Scheme-reports] REPL
Alex Shinn
(14 Nov 2012 09:26 UTC)
|
|
Re: [Scheme-reports] REPL
Helmut Eller
(14 Nov 2012 10:22 UTC)
|
|
Re: [Scheme-reports] REPL
Marc Feeley
(14 Nov 2012 21:06 UTC)
|
|
Re: [Scheme-reports] REPL
John Cowan
(14 Nov 2012 21:26 UTC)
|
|
Re: [Scheme-reports] REPL
Marc Feeley
(14 Nov 2012 22:05 UTC)
|
|
Re: [Scheme-reports] REPL
Alex Shinn
(14 Nov 2012 23:46 UTC)
|
|
[Scheme-reports] equal?
Alan Watson
(15 Nov 2012 00:40 UTC)
|
|
Re: [Scheme-reports] equal?
Jim Rees
(15 Nov 2012 02:36 UTC)
|
|
Re: [Scheme-reports] equal?
John Cowan
(15 Nov 2012 16:26 UTC)
|
|
Re: [Scheme-reports] equal?
Alan Watson
(15 Nov 2012 16:35 UTC)
|
|
Re: equal?
Arthur A. Gleckler
(17 Nov 2012 20:32 UTC)
|
|
Re: [Scheme-reports] REPL John Cowan (15 Nov 2012 16:23 UTC)
|
|
Re: [Scheme-reports] REPL
Aaron W. Hsu
(15 Nov 2012 23:47 UTC)
|
|
Re: [Scheme-reports] REPL
Shiro Kawai
(16 Nov 2012 01:16 UTC)
|
|
Re: [Scheme-reports] REPL
Per Bothner
(14 Nov 2012 21:37 UTC)
|
|
Re: [Scheme-reports] REPL
Marc Feeley
(14 Nov 2012 21:49 UTC)
|
|
Re: [Scheme-reports] REPL
Andy Wingo
(04 Jan 2013 13:02 UTC)
|
|
Re: [Scheme-reports] REPL
John Cowan
(04 Jan 2013 15:42 UTC)
|
|
Re: [Scheme-reports] REPL
Alaric Snell-Pym
(04 Jan 2013 16:30 UTC)
|
|
Re: [Scheme-reports] REPL
Helmut Eller
(15 Nov 2012 07:44 UTC)
|
|
Re: [Scheme-reports] REPL
John Cowan
(15 Nov 2012 16:04 UTC)
|
|
Re: [Scheme-reports] REPL
Per Bothner
(15 Nov 2012 16:17 UTC)
|
Marc Feeley scripsit:
> R7RS defines mutation of imported variables as "an error". This looks
> like a restriction to me and goes against the Scheme mantra "Programming
> languages should be designed not by piling feature on top of feature,
> but by removing the weaknesses and restrictions...".
Please note the discussion of error situations that don't use the term
"signaled" in 1.3.2 (emphasis added):
If such wording does not appear in the discussion of an error,
then implementations are not required to detect or report the
error, though they are encouraged to do so. /Alternatively,
implementations may provide non-portable extensions./ Such
a situation is sometimes, but not always, referred to with the
phrase ``an error.'' For example, it is an error for a procedure
to be passed an argument of a type that the procedure is not
explicitly specified to handle, even though such domain errors
are seldom mentioned in this report. Implementations may extend
a procedure's domain of definition to include such arguments.
--
Why are well-meaning Westerners so concerned that John Cowan
the opening of a Colonel Sanders in Beijing means cowan@ccil.org
the end of Chinese culture? [...] We have had http://www.ccil.org/~cowan
Chinese restaurants in America for over a century,
and it hasn't made us Chinese. On the contrary,
we obliged the Chinese to invent chop suey. --Marshall Sahlins
_______________________________________________
Scheme-reports mailing list
Scheme-reports@scheme-reports.org
http://lists.scheme-reports.org/cgi-bin/mailman/listinfo/scheme-reports