cl-ppcre-devel

cl-ppcre-devel@common-lisp.net

182 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

[cl-ppcre-devel] Component "cl-ppcre-unicode" not found
by Nicolas Garcia Belmonte 31 Oct '11

31 Oct '11

Hello there - Thank you very much for this library! I'm not sure if this has been reported in the mailing list before, but since I haven't found a similar thread in a couple of months I thought I would just inform this myself. I've been unsuccessfully trying to install cl-ppcre from asdf, I'm getting "Component cl-ppcre-unicode not found" as an error message. Here's the installation procedure I went through: https://gist.github.com/1327673 Could you provide me with more information on what I'm doing wrong? Thanks :) -- Nicolas Garcia Belmonte - http://philogb.github.com/

3 3

[cl-ppcre-devel] My open source libraries (aka "ediware")
by Edi Weitz 02 Sep '11

02 Sep '11

[My apologies if you receive multiple copies of this email.] Hi everybody! As some of you will know, I'll start on a new job tomorrow. This new job won't involve much hacking, if at all, and thus it doesn't look like I'll have a lot of time to maintain my open source libraries in the near future. I have no plans to suddenly disappear from the CL world, but don't expect new releases of any of my libs any time soon. (At least none published by me or on my server.) Luckily, Hans Hübner - who already did most of the maintenance and development work for Hunchentoot in the last two years or so - offered to coordinate further development via github. See his full announcement at <http://netzhansa.blogspot.com/2011/08/ediware-moving-to-github.html>. I'll continue to read the mailing lists for my libs and I'm still interested in fixing bugs you might find in the release tarballs available on my web server. However, I will likely not bother to discuss or work on new features or compatibility code for implementations other than LispWorks (which happens to be the one I'm using). Lastly, I hope to see a lot of you in Amsterdam <http://weitz.de/eclm2011/> in October. The number of registrations so far has been pretty disappointing, but you still have three weeks left to change your mind... :) Take care, Edi.

3 2

[cl-ppcre-devel] Problem with pathnames
by Juan Jose Garcia-Ripoll 31 Aug '11

31 Aug '11

I reported a related problem some time ago http://lists.common-lisp.net/pipermail/cl-ppcre-devel/2011-January/000706.h… However, instead of the values I supplied now cl-unicode is using :unspecific for the :type of a pathname. (defun dump-derived-tests () "Parses the Unicode data file \"DerivedCoreProperties.txt\" \(which is not used in read.lisp) and uses it to create a file \"derived-properties\" which will be used by CL-UNICODE-TEST." (with-output-to-source-file (out (make-pathname :name "derived-properties" :type :unspecific :directory '(:relative :up "test")) :no-header-p t) This is not supported by ECL, which uses NIL to represent an unfilled value (absent therefore). From the Hyperspec http://www.lispworks.com/documentation/HyperSpec/Body/19_bbbc.htm A conforming program must never unconditionally use a :unspecific as the value of a pathname component because such a value is not guaranteed to be permissible in all implementations. Probably what you want to solve is the merge-pathnames above the code (in the macro), which might instead read `(let* ((directory (make-pathname :name nil :type nil :version nil :defaults *this-file*)) (pathname (merge-pathnames ,relative-path directory)) Cheers, Juanjo -- Instituto de Física Fundamental, CSIC c/ Serrano, 113b, Madrid 28006 (Spain) http://juanjose.garciaripoll.googlepages.com

4 8

[cl-ppcre-devel] How to use it after installation?
by 徐迪 04 Jul '11

04 Jul '11

Hi, there , excuse me for asking this stupid question, but I'm fresh to common-lisp. I knew from http://weitz.de/cl-ppcre/#install that debian can install cl-ppcre from native package, so I use "apt-get install cl-ppcre" to install, and there are no problem during installation, but i don't know how to use it at all, should i just require from REPL? But it get a error. Maybe i just don't know how to use library in lisp, and i'm using clisp.

3 6

[cl-ppcre-devel] easy way to let regex-replace-all be case-unsensitive
by Mario Maio 24 Jun '11

24 Jun '11

Can I make regex-replace-all search being case insensitive ? Isn't there a direct option for that ? I've seen such an option in create-scanner , but I need nothing else than regex-replace-all, and I do not understand how to deal with create-scanner. Thanks Mario (clisp newbie) P.S. I'd like to give you my best compliments for your great job with ppcre, it's really fast and reliable, keep up the good work!

2 1

[cl-ppcre-devel] missing replacement
by Mario Maio 14 Apr '11

14 Apr '11

If i try this regexp (cl-ppcre:regex-replace-all " d {1-3}'" "la presa d 'aria" " d'" :preserve-case t) I don't get the expected replacement (remove the space before the apostrophe) "la presa d'aria" whereas Regex Coach works as expected. Thanks. Mario

2 1

[cl-ppcre-devel] Fwd: string length limit ?
by Mario Maio 14 Apr '11

14 Apr '11

Sorry if this is a trivial issue, I'm a common lisp newbie. If I apply the following very simple command (replacing one or more consecutive CR chars with one LF char) (cl-ppcre:regex-replace-all (concatenate 'string (string #\return) "+") mystring (string #\linefeed)) to my string of 455079 characters (loaded from a utf-8 file), some of the last #\return characters are not substituted (even if they should, since if a apply again the command to the resulting string they ARE subsituted). It looks like in the search there is a sort of length limit, or maybe some string length mistake connected to multi-byte characters representation ? Cheers. Mario

2 3

[cl-ppcre-devel] compiling cl-ppcre with lisps
by Leo T Butler 15 Feb '11

15 Feb '11

Hi, I've been trying to use cl-ppcre in Maxima (in order to generate the online help). This has worked very nicely with clisp, cmucl and sbcl but other lisps have had problems. Gcl does not compile cl-ppcre and ecl does but it runs *very* slow. I wonder if you might have any thoughts about this? Here is a link to part of the thread discussing this: http://www.math.utexas.edu/pipermail/maxima/2011/024147.html and here is the first item in the thread, with a link to the source http://www.math.utexas.edu/pipermail/maxima/2011/024118.html Thanks, Leo -- The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336.

3 2

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

cl-ppcre-devel