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?
18:45:54flip214does that destroy the package, or will that just remove the package from the list of packages?
18:46:03Bikei mean, i thought it would hit a package lock.
18:46:20flip214that would only help against _modifications_, not _deleting_ the package...
18:46:43Bikei thought there was a lock on deleting it as well. evidently not.
18:46:50flip214same as a write-bit on a file resp. having write rights on the containing directory
18:47:02Bikeand delete-package makes it so later package operations on the package are undefined, so it can be destroyed.
19:23:57rpgI just upgraded my linux distro and now my copy of CCL doesn't work. When I try to start it up, I just get a "file not found" error, although the executable is there. Anyone seen this?
19:26:07rpgAs far as I can tell, yes, because this is in my home dir. ccl64 works, though and ccl not, so that's probably a clue. Investigating further.