News for hackers. Stuff that matters.

A comment on Common Lisp Implementations in 2023. Parent comment

Re:Common Lisp Implementations in 2023 by tmtvl on Thursday February 23, 2023 @09:39AM (#34911123)
Not really, but there are ways around it: http://blog.quicklisp.org/2011/08/going-back-in-dist-time.ht...
[ Parent | on HN ]
Re:Common Lisp Implementations in 2023 by oblio on Thursday February 23, 2023 @11:04AM (#34912278)
I'm confused, is this about Quicklisp itself or about the packages it manages?

I.e. quicklisp 1.1 versus quicklisp 1.0 or libfoo 1.1 vs libfoo 1.0?

[ Parent | on HN ]
Re:Common Lisp Implementations in 2023 by tmtvl on Thursday February 23, 2023 @01:09PM (#34914186)
It's about the packages, a Quicklisp dist has a list of packages of specific versions (like libfoo 1.1, libbar 1.0, and libbaz 1.2) and you can switch to an older dist (which can have libfoo 1.0, no libbar, and libbaz 1.2).
[ Parent | on HN ]
Re:Common Lisp Implementations in 2023 by oblio on Thursday February 23, 2023 @04:37PM (#34916862)
Oh, so it's actually a carefully curated limited list? Because otherwise the combinatorial explosion would make this unmanageable super fast.
[ Parent | on HN ]