Search Results

General style remarks lst is more of a Scheme idiom, in Common Lisp you don't eat vowels but write directly list if your variable is a list (to be honest, some CL standard functions have weird names …

There is not much to say about this code, it is fine. You can get rid of incf and setf; the varying x is replaced by a variable named z; I express the comparison as a boolean variable greater (for la …

Can you process code like that in a single glance? That's my really my point. Yes, and it is in fact a way of expressing code that I miss in other languages, where the equivalent code feels nee …

Code review - mostly style You did a litteral translation from C++ to CL that seems good. I have some stylistic issues with it: (defclass training-data () ((training-data-stream :reader training-d …

Split Here is an alternative implementation of split using the loop facility. (defun split (split-char string-to-split) (loop for start = 0 then (1+ end) for end = (position split-char str …

Your code works but has some efficieny problems, as already pointed out by Rainer Joswig ("it conses like mad"). Now that you posted a modified version I added some details at the end of the answer. …

Note that Alexandria defines random-elt (and whichever). My only complain is that random-element does too much, both digits and characters. This would be the kind of use cases where I would rely on g …

The Common Lisp standard does not require implementations to eliminate tail calls, but this is an optimization supported by many implementations. It is the case for Lispworks. You can write your code …