| commit | 46ca19e3db3fc054743290cdf6e1cc51ff3ec588 | |
| author | Nikodemus Siivola <nikodemus@random-state.net> | |
| Fri, 19 Dec 2008 16:14:58 +0000 (19 16:14 +0000) | ||
| committer | Nikodemus Siivola <nikodemus@random-state.net> | |
| Fri, 19 Dec 2008 16:14:58 +0000 (19 16:14 +0000) | ||
| tree | b02a7dc4b564d4a52fc4ead3fbffe915a2f218f4 | treesnapshot (tar.gz zip) |
| parent | bc2977763a323f3e180dfb227081688cd8d021af | commitdiff |
1.0.23.57: rewrite bug 217
* Case A is a non-issue. SBCL interprets "unpredictable but harmless"
to mean "anything, but heap will no be corrupted, data lost, etc"
-- that is, an error may or may not be signalled, but it the lisp
session will remain sane and operable.
* Case B is negated by the portability argument: since specifying both
is unspecified, we should not build useful-seeming extensions on top
of it, as it will only create portability problems for users.
* Case C remains partially valid, except for the runtime WARNINGs.
Integrated into the new text.
* Case A is a non-issue. SBCL interprets "unpredictable but harmless"
to mean "anything, but heap will no be corrupted, data lost, etc"
-- that is, an error may or may not be signalled, but it the lisp
session will remain sane and operable.
* Case B is negated by the portability argument: since specifying both
is unspecified, we should not build useful-seeming extensions on top
of it, as it will only create portability problems for users.
* Case C remains partially valid, except for the runtime WARNINGs.
Integrated into the new text.
| BUGS | diffblobblamehistory | |
| version.lisp-expr | diffblobblamehistory |