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.
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.