15:39:08jackdanielanother popular choice is uiop. osicat gives you truly implementation-independent primitives for that though.
15:39:22jackdanielbut osicat depends on ffi (if that's a problem for you)
15:40:18malice`Yeah, I was wondering because http://eudoxia.me/article/common-lisp-sotu-2015 mentioned osicat as preferred one (not sure how legit the site is though)
15:40:21slyrusuiop is built in on modern systems with ASDF
15:41:54malice`They mentioned uiop as preferred one. I missed "don't" before "use osicat", lol.
15:43:08jackdanielslyrus: but built-in version may be different between systems, it's better to depend on uiop from quicklisp for being up-to-date. I have some doubts about uiop api stability too.
15:53:01malice`Can I somehow iterate on the pathname in UIOP? Like (with-each-file-in-path (file my-path) (delete-file file)) ?
18:41:45pjbflip214: (map nil 'delete-file (directory "**;*.*")) but CL implementations are not necessarily able to access all the files in a file system.
18:45:11flip214well, won't deleting the keyword package mean that KEYWORDP is no longer working, and so the &rest argument lists can't be parsed anymore?