cl-ppcre-devel

cl-ppcre-devel@common-lisp.net

182 discussions

[cl-ppcre-devel] Multi-line-mode
by Klaus Harbo 02 May '04

02 May '04

I have been using cl-ppcre for quite some time - great program library, thx! - but I am now looking to match multi-line data, and Iøm having some difficulties... I would expect (scan (create-scanner ".+" :multi-line-mode t) (concatenate 'string '(#\a #\Newline #\b))) to match all three characters, but it matches only #\a. I downloaded cl-ppcre from CVS just now to check that this occurs in the most recent version; I'm using Lispworks 4.3.6. CMUCL 18d seems to behave the same way. Can I make :everything (".") match multiple lines of input, and if so, how? Any help much appreciated. best, -Klaus.

2 1

[cl-ppcre-devel] New release 0.7.6
by Edi Weitz 20 Apr '04

20 Apr '04

Hi! A new release is available from <http://weitz.de/files/cl-ppcre.tgz>. Here's the relevant part from the changelog: Version 0.7.6 2004-04-20 The closures created by CREATE-BMH-MATCHER now cleanly cope with negative arguments (bug caught by Damien Kick) Have fun, Edi.

1 0

RE: [cl-ppcre-devel] Problems with a regexp using CL-PPCRE 0.7.4
by Kick Damien-DKICK1 20 Apr '04

20 Apr '04

Edi Weitz [edi(a)agharta.de] wrote: > [...] I /think/ I've found the bug. [...] Anyway, please try if you > still get your bug with this version: [...] Good news! I was able to execute the following on my original platform (Solaris 8) (loop :repeat 100 :do (break-cl-ppcre::test-telnet-argsmmgts5--case-2 "localhost" :prompt break-cl-ppcre::+default-mgts-server-prompt--break-cl-ppcre+)) with no problems. Looks like it did the trick.

2 1

RE: [cl-ppcre-devel] Problems with a regexp using CL-PPCRE 0.7.4
by Kick Damien-DKICK1 19 Apr '04

19 Apr '04

Edi Weitz [edi(a)agharta.de] wrote: > On Mon, 19 Apr 2004 13:40:29 -0500, Kick Damien-DKICK1 > <DKICK1(a)motorola.com> wrote: > > Can you reproduce this behavior on your GNU/Linux setup? > No. But I /think/ I've found the bug. The reason I couldn't > reproduce your results seems to be that you either didn't compile > CL-PPCRE or that you used a "safe core" or somesuch. [...] <nod> Yeah, I compiled CL-PPCRE after having removed the optimization declarations via reader macros, #-:CL-PPCRE-SAFE-AND-SLOW, per the tar ball I sent you a while back. It was too difficult to try and determine from where the problem was originating with everything compiled with maximal optimization and minimal safety. For example: % diff -u scanner.lisp@@/main/kick_lti--e3-base/2 scanner.lisp --- scanner.lisp@@/main/kick_lti--e3-base/2 Fri Mar 5 02:36:37 2004 +++ scanner.lisp Sat Mar 6 17:35:27 2004 @@ -52,6 +52,7 @@ (return-from bmh-matcher (1+ i))))))))) (defun create-bmh-matcher (pattern case-insensitive-p) + #-:cl-ppcre-safe-and-slow (declare (optimize speed (safety 0) (space 0) @@ -101,6 +102,7 @@ thereis (and (,char-compare (schar *string* i) chr) i))))) (defun create-char-searcher (chr case-insensitive-p) + #-:cl-ppcre-safe-and-slow (declare (optimize speed (safety 0) (space 0) @@ -119,6 +121,7 @@ (declaim (inline newline-skipper)) (defun newline-skipper (start-pos) + #-:cl-ppcre-safe-and-slow (declare (optimize speed (safety 0) (space 0) @@ -328,6 +331,7 @@ rep-num zero-length-num reg-num) + #-:cl-ppcre-safe-and-slow (declare (optimize speed (safety 0) (space 0) > [...] Anyway, please try if you still get your bug with this > version: [...] I'll let you know the results as soon as I've had a chance to try it.

1 0

RE: [cl-ppcre-devel] Problems with a regexp using CL-PPCRE 0.7.4
by Kick Damien-DKICK1 19 Apr '04

19 Apr '04

Edi, Can you reproduce this behavior on your GNU/Linux setup? -----Original Message----- From: cl-ppcre-devel-bounces(a)common-lisp.net [mailto:cl-ppcre-devel-bounces@common-lisp.net] On Behalf Of Kick Damien-DKICK1 Sent: Sunday, 18 April, 2004 03:38 To: edi(a)agharta.de Cc: cl-ppcre-devel(a)common-lisp.net Subject: RE: [cl-ppcre-devel] Problems with a regexp using CL-PPCRE 0.7.4 Edi Weitz [edi(a)agharta.de] wrote: > I forgot two things: > > 1. Maybe this is an error that can only be seen on Sun OS. I don't > have a Sun to test so you might want to use an x86 machine as your > client if possible and see if it exposes the same problem. Okay, I just tried this on a GNU/Linux box... (BREAK-CL-PPCRE::EXPECT #<Closure Over Function "DEFUN CREATE-SCANNER-AUX" {48271F41}> " kick Password:" (FUNCTION (T T T) (VALUES (OR NULL FIXNUM) &OPTIONAL T SIMPLE-VECTOR SIMPLE-VECTOR)) (BASE-STRING 1)) (BREAK-CL-PPCRE::EXPECT #<Closure Over Function "DEFUN CREATE-SCANNER-AUX" {482BA659}> " " (FUNCTION (T T T) (VALUES (OR NULL FIXNUM) &OPTIONAL T SIMPLE-VECTOR SIMPLE-VECTOR)) Type-error in KERNEL::OBJECT-NOT-TYPE-ERROR-HANDLER: -1 is not of type (MOD 536870911) Restarts: 0: [ABORT] Return to Top-Level. Debug (type H for help) ("DEFUN CREATE-BMH-MATCHER" -2) Source: ; File: /home/kick/lti/cl-ppcre-0.7.4/scanner.lisp (BMH-MATCHER-AUX) 0] backtrace 0: ("DEFUN CREATE-BMH-MATCHER" -2) 1: ("DEFUN CREATE-SCANNER-AUX" " " 0 1) 2: (BREAK-CL-PPCRE::|(PCL::FAST-METHOD EXPECT (FUNCTION STREAM))| #<unused-arg> #<unused-arg> #<Closure Over Function "DEFUN CREATE-SCANNER-AUX" {482BA659}> #<Stream for descriptor 5> ...) 3: (BREAK-CL-PPCRE::TEST-TELNET-ARGSMMGTS5--CASE-2 "localhost" :LOGIN "kick" :PASSWORD ...) 4: (INTERACTIVE-EVAL (BREAK-CL-PPCRE::TEST-TELNET-ARGSMMGTS5--CASE-2 "localhost" :LOGIN "kick" :PASSWORD ...)) 5: (COMMON-LISP::%TOP-LEVEL) 6: (COMMON-LISP::RESTART-LISP) 0] (software-version) "n/a" 0] (software-type) "Linux" 0] (lisp-implementation-version) "18d" 0] *features* (:ASDF :CL-PPCRE :CL-PPCRE-SAFE-AND-SLOW :PCL-STRUCTURES :PORTABLE-COMMONLOOPS :PCL :PYTHON :CMU18 :CMU18D :GENCGC :CONSERVATIVE-FLOAT-TYPE :RANDOM-MT19937 :HASH-NEW :MP :I486 :X86 :LINUX :GLIBC2 :UNIX :COMMON :CMU :NEW-COMPILER :COMMON-LISP :ANSI-CL :IEEE-FLOATING-POINT) 0] _______________________________________________ cl-ppcre-devel site list cl-ppcre-devel(a)common-lisp.net http://common-lisp.net/mailman/listinfo/cl-ppcre-devel

2 1

[cl-ppcre-devel] New release 0.7.4
by Edi Weitz 19 Apr '04

19 Apr '04

Hi! A new release is available from <http://weitz.de/files/cl-ppcre.tgz>. Here's the relevant part from the changelog: Version 0.7.5 2004-04-19 Fixed a bug with constant-length repetitions of . (dot) in single-line mode (caught by RegexCoach user Lee Gold) Have fun, Edi.

1 1

[cl-ppcre-devel] Startup issues [fixed]
by Randall Randall 19 Apr '04

19 Apr '04

Hi, all. So, Jim Prewett pointed out offlist that this certainly should not be happening if I use a saved core. The reason it was still happening with a saved core was that I still had that (load ...) line in the .cmucl-init.lisp file. With that removed, using the .core I saved, it doesn't do the long compilation on startup. I'm still curious as to why it was doing it at all, but at least it's not tapping me on the shoulder whenever I start up my lisp now. :) Thanks, Jim! -- Randall Randall <randall(a)randallsquared.com> 'I say we put up a huge sign next to the Sun that says "You must be at least this big (insert huge red line) to ride this ride".' -- tghdrdeath(a)hotmail.com

2 1

[cl-ppcre-devel] (no subject)
by Randall Randall 19 Apr '04

19 Apr '04

Hi, I'm new to lisp and new to cl-ppcre. After building cl-ppcre, every time I start lisp, even if I don't explicitly load cl-ppcre.ppcf, I get ~150 lines of: ; Compiling LAMBDA (PCL::.PV-CELL. PCL::.NEXT-METHOD-CALL. CONDITIONS::X): ; Compiling Top-Level Form: before a lisp prompt. Is this usual? Of course, in production it won't matter, since I'll only very occasionally be restarting, but it's surprising and I wonder if it might be indicative of an actual problem with the build or install or something? Thanks! -- Randall Randall <randall(a)randallsquared.com> 'I say we put up a huge sign next to the Sun that says "You must be at least this big (insert huge red line) to ride this ride".' -- tghdrdeath(a)hotmail.com

2 3

RE: [cl-ppcre-devel] Problems with a regexp using CL-PPCRE 0.7.4
by Kick Damien-DKICK1 18 Apr '04

18 Apr '04

Edi Weitz [edi(a)agharta.de] wrote: > I forgot two things: > > 1. Maybe this is an error that can only be seen on Sun OS. I don't > have a Sun to test so you might want to use an x86 machine as your > client if possible and see if it exposes the same problem. Okay, I just tried this on a GNU/Linux box... (BREAK-CL-PPCRE::EXPECT #<Closure Over Function "DEFUN CREATE-SCANNER-AUX" {48271F41}> " kick Password:" (FUNCTION (T T T) (VALUES (OR NULL FIXNUM) &OPTIONAL T SIMPLE-VECTOR SIMPLE-VECTOR)) (BASE-STRING 1)) (BREAK-CL-PPCRE::EXPECT #<Closure Over Function "DEFUN CREATE-SCANNER-AUX" {482BA659}> " " (FUNCTION (T T T) (VALUES (OR NULL FIXNUM) &OPTIONAL T SIMPLE-VECTOR SIMPLE-VECTOR)) Type-error in KERNEL::OBJECT-NOT-TYPE-ERROR-HANDLER: -1 is not of type (MOD 536870911) Restarts: 0: [ABORT] Return to Top-Level. Debug (type H for help) ("DEFUN CREATE-BMH-MATCHER" -2) Source: ; File: /home/kick/lti/cl-ppcre-0.7.4/scanner.lisp (BMH-MATCHER-AUX) 0] backtrace 0: ("DEFUN CREATE-BMH-MATCHER" -2) 1: ("DEFUN CREATE-SCANNER-AUX" " " 0 1) 2: (BREAK-CL-PPCRE::|(PCL::FAST-METHOD EXPECT (FUNCTION STREAM))| #<unused-arg> #<unused-arg> #<Closure Over Function "DEFUN CREATE-SCANNER-AUX" {482BA659}> #<Stream for descriptor 5> ...) 3: (BREAK-CL-PPCRE::TEST-TELNET-ARGSMMGTS5--CASE-2 "localhost" :LOGIN "kick" :PASSWORD ...) 4: (INTERACTIVE-EVAL (BREAK-CL-PPCRE::TEST-TELNET-ARGSMMGTS5--CASE-2 "localhost" :LOGIN "kick" :PASSWORD ...)) 5: (COMMON-LISP::%TOP-LEVEL) 6: (COMMON-LISP::RESTART-LISP) 0] (software-version) "n/a" 0] (software-type) "Linux" 0] (lisp-implementation-version) "18d" 0] *features* (:ASDF :CL-PPCRE :CL-PPCRE-SAFE-AND-SLOW :PCL-STRUCTURES :PORTABLE-COMMONLOOPS :PCL :PYTHON :CMU18 :CMU18D :GENCGC :CONSERVATIVE-FLOAT-TYPE :RANDOM-MT19937 :HASH-NEW :MP :I486 :X86 :LINUX :GLIBC2 :UNIX :COMMON :CMU :NEW-COMPILER :COMMON-LISP :ANSI-CL :IEEE-FLOATING-POINT) 0]

1 0

RE: [cl-ppcre-devel] Problems with a regexp using CL-PPCRE 0.7.4
by Kick Damien-DKICK1 14 Apr '04

14 Apr '04

Sorry for the delay... (EXPECT #<Closure Over Function "DEFUN CREATE-SCANNER-AUX" {40333B01}> " " (FUNCTION (T T T) (VALUES (OR NULL FIXNUM) &OPTIONAL T SIMPLE-VECTOR SIMPLE-VECTOR)) (BASE-STRING 1)) Type-error in KERNEL::OBJECT-NOT-TYPE-ERROR-HANDLER: -1 is not of type (MOD 536870911) Restarts: 0: [ABORT] Return to Top-Level. Debug (type H for help) ("DEFUN CREATE-BMH-MATCHER" -2) Source: ; File: /usr/vob/2gtt/lti/cl-ppcre-0.7.4/scanner.lisp (AREF SKIP (CHAR-CODE (SCHAR PATTERN K))) 0] -----Original Message----- From: cl-ppcre-devel-bounces(a)common-lisp.net [mailto:cl-ppcre-devel-bounces@common-lisp.net] On Behalf Of Edi Weitz Sent: Friday, 12 March, 2004 02:55 To: Kick Damien-DKICK1 Cc: cl-ppcre-devel(a)common-lisp.net Subject: Re: [cl-ppcre-devel] Problems with a regexp using CL-PPCRE 0.7.4 OK, what you've sent so far looks OK. Could you now please add the following code, try again, and show me the output (you can of course leave out the login/password stuff as long as it doesn't cause the error)? 1. In your EXPECT function between (READ-CHAR IO) and (MULTIPLE-VALUE-BIND ...) add (print (list 'expect expected buffer (type-of expected) (type-of buffer))) 2. In BMH-MATCHER-AUX in scanner.lisp (from CL-PPCRE) after the line `(LAMBDA (START-POS) remove the declaration and replace it with (print (list 'bmh start-pos *end-pos* *string* pattern (type-of *string*) (type-of pattern))) Let's see what we get... Thanks, Edi. _______________________________________________ cl-ppcre-devel site list cl-ppcre-devel(a)common-lisp.net http://common-lisp.net/mailman/listinfo/cl-ppcre-devel

2 1

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