The standard CL behavior is to remove files that contain partial output (when using with-open-file). This is often not what I want. The macros WITH-FILE-OUTPUT and WITH-FILES-FOR-OUTPUT will open files that will be closed, but not removed (e.g. left in a partially written state) if the computation is aborted via a restart.
…ant, exactly. These should probably be deprecated: they are not unique enough to move to ppcre master, but the tools in master cannot do this exactly. All and all it is a bit annoying and I will have to keep them around.
If you need infix, use the version that is accesible via Quicklisp (kept with the FEMLisp project).
See library cl-factoring
See library CL-Primality. This is now a dependency of the toolbox library. Also, prime? -> primep
…ese are now in index-mapped-arrays.
…rapper code (think around methods for arbitrary functions) for debugging purposes. There are some caveats on using it that are undocumented, you must call the underlying function (like with around methods and call-next-method) except you must pass the arguments of the function and you must refer to the function literal, not use the symbol as a function designator.
… in the background by starting a new thread using Bordeaux-Threads.
…). This is necessary for several applications.
…age. It is now in its own library, Pythonic-String-Reader, which is loaded from Toolbox.
…use it). It was erring when given no arguments.
…atches the syntax of the REDUCING collector.
…ges to the text.
…ow it will take multiline strings delimited by three or four double quotation marks. The three marks are useful when you want your Lisp, editor, whatever, to recognize this as a string, the four are good for when you are quoting a program and want the editor to recognize it as code (perform indentation, symbol completion, what-have-you.)