Start using UIOP instead of CL-FAD and Osicat #75
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've replaced Common Lisp samples that used CL-FAD and Osicat to use UIOP instead. Most modern Common Lisp implementations already include UIOP as part of ASDF and the samples don't need to use external libraries. In addition to that, a part of Common Lisp community is calling for consolidation of competing libraries and UIOP seems to be the winner in this area. See, for example, http://eudoxia.me/article/common-lisp-sotu-2015.
I've replaced a few other samples that wouldn't work in many Common Lisp implementations with the corresponding UIOP function calls.
I've removed a sample about creating symbolic links. Even though UIOP does not directly offer a way to create them, symbolic link handling in Common Lisp is a tricky issue and I didn't think it would be beneficial to replace it with some indirect way as it could cause misunderstandings. Keeping the old Osicat sample seemed inappropriate because of the reasons outlined in the first paragraph. In addition to that, Osicat doesn't support creating symbolic links on Windows which is, I think, a rather dangerous move for an interoperability library.