cl-ppcre-devel

Download

cl-ppcre-devel@lists.common-lisp.net

November 2011

4 participants
2 discussions

[cl-ppcre-devel] Error loading cl-unicode
by Noldus Reijnders 30 Nov '11

30 Nov '11

Hello everyone! I'm a student from the netherlands working on a parser (using cl-yacc) and I use dso-lex as the lexer-generator, which depends on cl-ppcre (as you might know). Since I want to parse RIF files that require unicode encoded characters, I wanted to extend cl-ppcre with unicode, using cl-unicode. Unfortunately I receive an error when I try to install cl-unicode. When it tries to compute the Hangul syllable names (this happens when loading hash-tables.fasl) I get the following: Error: `("Unbound Value")' is not of the expected type `number' [condition type: type-error] Some extra info: - I tried to install cl-unicode with, and without installing flexi-streams and trivial-gray-streams, but both give me the error. - I use Allegro CL Could you perhaps help me? Regards, Noldus Reijnders PS I also get an error when it tries to load util.lisp saying that +t-count+ is unknown. However, I fixed that by replacing that with the number in the assignment of TCount. Same thing for VCount btw. Maybe that has something to do with Allegro CL?

4 15

Re: [cl-ppcre-devel] Error loading cl-unicode
by Noldus Reijnders 28 Nov '11

28 Nov '11

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(a)franz.com > To: n_reijnders(a)hotmail.com > CC: cl-ppcre-devel(a)common-lisp.net; support(a)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(a)hotmail.com > > To: cl-ppcre-devel(a)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(a)franz.com, http://www.franz.com/ > Franz Inc., 2201 Broadway, Suite 715, Oakland CA 94612 > Cell: (413) 559-8738 * FAX: (206) 338-4052

1 0