4 ms·
It's too bad, since being a "standard" has helped CL to grow so much, despite some warts that the language inherited from old times habits. Without a standard,
by behnamoh 10y ago
It's too bad, since being a "standard" has helped CL to grow so much, despite some warts that the language inherited from old times habits.
Without a standard, it seems most efforts to build a new Lisp come to a naught (think Racket and Clojure and Arc and ...)
- deleted 10y ago[deleted]
- bjt 10y agoClojure seems to be thriving, as far as I can tell.
- shakna 10y agoClojure come to naught? Better tell everyone who is hiring! [0] [0] https://www.indeed.com/jobs?q=clojure https://www.indeed.com/jobs?q=clojure
- masukomi 10y agoyeah, i second this. Clojure is a major success. Depending on how you look at it Racket is a decent success too. It seems to just be more focused on things like helping universities/uni students explore language creation, instead of being a tool for use in businesses.
- RUG3Y 10y agoRacket seems focused on education and experimentation and in that arena I think it's very successful. I'm pretty impressed with where Racket has gone and I think it's very cool.
- jlarocco 10y agoI use CL quite a bit, and disagree with you. The standard was great for removing incompatibilities between all of the old competing Lisps, but now that all of the implementations are on the same page and support the base line standard, I don't see the point in updating and revising the standard. Is there really anything to add that couldn't be done as a library? And while there are warts, it's easy enough to avoid those parts or use macros and libraries to smooth over them. There may be some undefined behavior or implementation specific things in the standard, but it's far less than C or C++, and facilities like the features list makes it pretty easy for libraries to detect implementation differences and do the right thing. > Without a standard, it seems most efforts to build a new Lisp come to a naught (think Racket and Clojure and Arc and ...) Seems like a non sequitur. There are plenty of languages without standards that have become popular (Python, Perl, Java, Ruby, Go, etc.) and also plenty of non-Lisp languages that don't have standards and have gone no where. And then there's ILisp, which has a standard and has still gone basically nowhere.
- kazinator 10y ago> I don't see the point in updating and revising the standard. I'd like to see outstanding issues noted in the existing standard to be resolved. For instance, there is one ambiguity in unwinding. Unwinding occurs under the locus of a dynamic control transfer which has selected an exit point. Unwinding can be intercepted by a form like unwind-protect. That form can "hijack" the control transfer by initiating another one, possibly to a different exit point. The question is: what exit points are still visible and hence available when a given unwind protect cleanup block is executing? Can the unwind-protect choose a less distant exit point than the original control transfer? ANSI CL basically leaves this aspect nonportable: when an unwind protect cleanup is executing, it could be the case that all of the exit points which were "on the way" to the current exit point are already "torn down". Or it could be the case that the implementation performs "tear down as you unwind": exit points are torn down as their binding forms are terminated during unwinding. In a nutshell, it is implementation-defined whether to tear down intervening exit points during the original search for the exit point, or leave them up and take them down during the actual unwinding. The latter behavior is probably less surprising and should probably be ANSI CL standardized.