allegro-cl

Nested `defun` produces a repeated warning in Allegro Common Lisp

别等时光非礼了梦想. 提交于 2019-12-12 15:42:57
问题 I have a generic implementation of merge sort in Common Lisp: I have different implementation of split and merge functions and, for each combination of a split and merge function I want to construct a merge sort function. Any split function takes a list of strings as input and returns a list of two list: the two halves of the original list. Any merge function takes two sorted lists as input and returns the sorted merged list. Each merge sort function is created by invoking the following

Where should a Quicklisp QUICKLOAD go in my source? Nowhere?

白昼怎懂夜的黑 提交于 2019-12-09 10:39:26
问题 Let's say I build an application on top of net.aserve and bordeaux-threads . My package declaration might look like this: (defpackage :my-package (:use :cl :net.aserve :bordeaux-threads) (:export …)) I use Quicklisp, so I run (ql:quickload "aserve") (ql:quickload "bordeaux-threads") in SLIME before compiling my package, and everything is fine. Of course, tomorrow I start up SLIME again and I have to remember to issue the QUICKLOAD s before I compile, otherwise I'm in for trouble. I could put