Recommend using cl-package-locks instead of #+sb-package-locks (:lock t)

[minghu6]

When I read the source, I find that :

serapeum/package.lisp

Line 12 in 408abcc

#+sb-package-locks (:lock t)

However, there is a cl-package-locks have provided a uniform way of dealing with package-locks across implementations.

Why not just import it from defsystem and replace the sbcl-package-lock using (cl-package-locks:lock-package 'serapeum) on package.lisp?

[ruricolist]

For two reasons:

1. cl-package-locks is very old and probably obsolete (hasn't been touched in 10 years, doesn't even mention ECL)
2. I use the feature of SBCL's package locks that lets one package implement parts of another; not all Lisps that support package locks support that.

However there may be a better, more portable way to do this so I will leave this issue open for the present.

[minghu6]

cl-package-locks is indeed very old and keeps unmaintained for a long time...
(I just use it in sbcl, and still works fine for package lock function)

Maybe we can try to email the author (if still alive 😂) and take over it? en... maybe some day, waiting for Godot

[elliottjohnson]

Hi. Reviving an old topic becauseI just found this via a random Google search.

No updates in a long time because there hasn't been a need on my end. Let me know if you have a pull request for your needs.

Best,
Elliott