3 ms·
Interesting that he didn't add the aftermath inside of his own mistakes in the standard. He was the best person to write it down and defend it later publicly. b
by rurban 7y ago
Interesting that he didn't add the aftermath inside of his own mistakes in the standard. He was the best person to write it down and defend it later publicly. but he also added a chapter by himself, the nes (new error system), the new conditioning system, which was by far the worst part of the standard. Almost nobody uses it, way too overarchitectured. All the rest is very solid, people only complain that threads and ffi are missing from the standard.
- rauhl 7y agoI think that the condition system is one of the better parts of Lisp, and miss it in every language where the libraries I use unwind the stack to provide me an error. It’s true that it’s not used too much in small programs, because small programs don’t need it. But in large systems, it’s invaluable.
- rurban 7y agoConditions are invaluable, but not Ken's. It faces the same problems as my stderror AutoLISP library: overarchitectured. Slim and small, not so big and fragile. CLOS is small and easy compared to the conditions. scheme did it right
- lispm 7y ago> CLOS is small and easy compared to the conditions CLOS is much more complex than conditions. > scheme did it right Not at all. Scheme was not providing any error handling in the language up to R5RS and had then zillions of different implementation specific extensions, many of them influenced by Common Lisp's condition system. Compare: https://www.gnu.org/software/mit-scheme/documentation/mit-scheme-ref/Error-System.html#Error-System https://www.gnu.org/software/mit-scheme/documentation/mit-sc... https://docs.racket-lang.org/reference/exns.html https://docs.racket-lang.org/reference/exns.html https://wiki.call-cc.org/man/4/Exceptions https://wiki.call-cc.org/man/4/Exceptions https://www.scheme.com/tspl4/exceptions.html https://www.scheme.com/tspl4/exceptions.html For R7RS large they are still finding out what to do. https://bitbucket.org/cowan/r7rs-wg1-infra/src/default/ExceptionsErrorsAndConditions.md https://bitbucket.org/cowan/r7rs-wg1-infra/src/default/Excep...
- kazinator 7y agoIndeed, right through R5RS, Scheme specified that certain situations in the processing of a Scheme program constitute an "error", without explaining what that word means, or any mechanism to catch such a thing, recover from it, or generate it on purpose (without provoking an erroneous condition). A conforming R5RS Scheme implementation can crash or abort upon encountering an error.
- deleted 7y ago[deleted]
- pfdietz 7y ago> All the rest is very solid Logical pathnames are very solid? Let's also talk about the complex types and their operations. Their specification has a big internal inconsistency. Oh, and read strictly, the subtype relationship is undecidable, which makes array element upgrading impossible to implement in a fully conforming way. There are also all those places where the standard does not define what happens. Why are some operations required to signal errors in safe code when argument type constraints are violated, but not others? This lack of specificity is the opposite of "solid".
- rurban 7y agoOK, logical pathnames are not solid. Agreed. Types and subtypes were a very late decision and not in CLtL2 I believe. Those lack of exact error descriptions is also in most other standards, and many are implementation defined. CL set the first standard there with its strict formalization even for the most mundane forms. Still very solid to me. I'm still fighting daily with the C standards which should know better by now.
- pfdietz 7y agoSo, conditions are the least solid part of the standard, if we are allowed to make excuses for and ignore any other part. Ok then.
- lispm 7y ago> but he also added a chapter by himself He was chair of the ANSI CL subcommittee for error handling. > far the worst part of the standard That's a very very rarely heard complaint.