Hi Gary, Ah ok, thanks for explaining both my questions. I circumvented the issue by using the smaller case version-files. Weird that the quicklisp version is different though. Thank you both for the help! Noldus

Date: Mon, 28 Nov 2011 10:50:41 -0500 From: gwking@franz.com To: n_reijnders@hotmail.com CC: cl-ppcre-devel@common-lisp.net; support@franz.com Subject: Re: [cl-ppcre-devel] Error loading cl-unicode

Hi Noldus,

On 11/25/11 12:46 PM, Noldus Reijnders wrote:

...

I mentioned the extra error when using quicklisp > it is thrown when compiling "lists.lisp", so I just opened lists.lisp in the quicklisp dist folder and the one I downloaded from your site, Edi. I found the following differences: Quicklisp:(|COMMON-LISP|::|IN-PACKAGE| :|CL-UNICODE|) (|COMMON-LISP|::|SETQ| |CL-UNICODE|::|*GENERAL-CATEGORIES*| '(|CL-UNICODE-NAMES|::|CO| etc... Edi's site:(in-package :cl-unicode) (setq *general-categories* (quote (cl-unicode-names::CO etc... Both are version 0.1.2 so I don't understand why this is, but it is clear that my CL implementation has trouble with that. I actually use "GDL" btw, which is build on top of AllegroCL and for some reason it doesn't recognise COMMON-LISP. From: n_reijnders@hotmail.com To: cl-ppcre-devel@common-lisp.net

This is caused by the same case issue as the first issue you found. In Allegro mlisp, COMMON-LISP and common-lisp are not the same symbols. In an ANSI-Lisp, they are. It may be that an additional patch is needed to make quicklisp happy too. I'll try to look into that this coming weekend.

HTH,

Gary Warren King, gwking@franz.com, http://www.franz.com/ Franz Inc., 2201 Broadway, Suite 715, Oakland CA 94612 Cell: (413) 559-8738 * FAX: (206) 338-4052