From DKICK1 at motorola.com Tue Apr 6 05:12:46 2004 From: DKICK1 at motorola.com (Kick Damien-DKICK1) Date: Tue, 6 Apr 2004 00:12:46 -0500 Subject: [cl-ppcre-devel] Problems with a regexp using CL-PPCRE 0.7.4 Message-ID: <8E4E38BF6D087F4488E80ABAACA2F3F4B29EFA@il27exm02.cig.mot.com> Sorry for the delay... (EXPECT # " " (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 at common-lisp.net [mailto:cl-ppcre-devel-bounces at common-lisp.net] On Behalf Of Edi Weitz Sent: Friday, 12 March, 2004 02:55 To: Kick Damien-DKICK1 Cc: cl-ppcre-devel at 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 at common-lisp.net http://common-lisp.net/mailman/listinfo/cl-ppcre-devel From DKICK1 at motorola.com Tue Apr 6 05:34:49 2004 From: DKICK1 at motorola.com (Kick Damien-DKICK1) Date: Tue, 6 Apr 2004 00:34:49 -0500 Subject: [cl-ppcre-devel] Problems with a regexp using CL-PPCRE 0.7.4 Message-ID: <8E4E38BF6D087F4488E80ABAACA2F3F4B29EFB@il27exm02.cig.mot.com> Oh, and exiting from the debugger... 0] 0 (CL-PPCRE::BMH -2 1 " " " % " (SIMPLE-BASE-STRING 1) (SIMPLE-BASE-STRING 3)) * -----Original Message----- From: cl-ppcre-devel-bounces at common-lisp.net [mailto:cl-ppcre-devel-bounces at common-lisp.net] On Behalf Of Kick Damien-DKICK1 Sent: Tuesday, 06 April, 2004 00:13 To: edi at agharta.de Cc: cl-ppcre-devel at common-lisp.net Subject: RE: [cl-ppcre-devel] Problems with a regexp using CL-PPCRE 0.7.4 Sorry for the delay... (EXPECT # " " (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 at common-lisp.net [mailto:cl-ppcre-devel-bounces at common-lisp.net] On Behalf Of Edi Weitz Sent: Friday, 12 March, 2004 02:55 To: Kick Damien-DKICK1 Cc: cl-ppcre-devel at 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 at common-lisp.net http://common-lisp.net/mailman/listinfo/cl-ppcre-devel _______________________________________________ cl-ppcre-devel site list cl-ppcre-devel at common-lisp.net http://common-lisp.net/mailman/listinfo/cl-ppcre-devel From edi at agharta.de Wed Apr 14 10:57:07 2004 From: edi at agharta.de (Edi Weitz) Date: Wed, 14 Apr 2004 12:57:07 +0200 Subject: [cl-ppcre-devel] Problems with a regexp using CL-PPCRE 0.7.4 In-Reply-To: <8E4E38BF6D087F4488E80ABAACA2F3F4B29EFA@il27exm02.cig.mot.com> (Kick Damien-DKICK's message of "Tue, 6 Apr 2004 00:12:46 -0500") References: <8E4E38BF6D087F4488E80ABAACA2F3F4B29EFA@il27exm02.cig.mot.com> Message-ID: On Tue, 6 Apr 2004 00:12:46 -0500 , Kick Damien-DKICK1 wrote: > Sorry for the delay... Same here... :) As you might have guessed I'm busy right now. I'll try to look into this by the end of this week. Thanks, Edi. From DKICK1 at motorola.com Sun Apr 18 08:37:48 2004 From: DKICK1 at motorola.com (Kick Damien-DKICK1) Date: Sun, 18 Apr 2004 03:37:48 -0500 Subject: [cl-ppcre-devel] Problems with a regexp using CL-PPCRE 0.7.4 Message-ID: <8E4E38BF6D087F4488E80ABAACA2F3F4B29F43@il27exm02.cig.mot.com> Edi Weitz [edi at 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 # " kick Password:" (FUNCTION (T T T) (VALUES (OR NULL FIXNUM) &OPTIONAL T SIMPLE-VECTOR SIMPLE-VECTOR)) (BASE-STRING 1)) (BREAK-CL-PPCRE::EXPECT # " " (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))| # # # # ...) 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] From randall at randallsquared.com Sun Apr 18 16:27:22 2004 From: randall at randallsquared.com (Randall Randall) Date: Sun, 18 Apr 2004 12:27:22 -0400 Subject: [cl-ppcre-devel] (no subject) Message-ID: <45342DB7-9155-11D8-A28E-000A95A0F1E8@randallsquared.com> 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 '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 at hotmail.com From randall at randallsquared.com Sun Apr 18 17:08:16 2004 From: randall at randallsquared.com (Randall Randall) Date: Sun, 18 Apr 2004 13:08:16 -0400 Subject: [cl-ppcre-devel] startup problem? In-Reply-To: <45342DB7-9155-11D8-A28E-000A95A0F1E8@randallsquared.com> References: <45342DB7-9155-11D8-A28E-000A95A0F1E8@randallsquared.com> Message-ID: On Apr 18, 2004, at 12:27 PM, Randall Randall wrote: > 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? Actually, I notice I don't have this issue at all on a Gentoo x86 system which will be my production box. So this is really a completely idle question. :) -- Randall Randall '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 at hotmail.com From edi at agharta.de Sun Apr 18 18:04:04 2004 From: edi at agharta.de (Edi Weitz) Date: Sun, 18 Apr 2004 20:04:04 +0200 Subject: [cl-ppcre-devel] (no subject) In-Reply-To: <45342DB7-9155-11D8-A28E-000A95A0F1E8@randallsquared.com> (Randall Randall's message of "Sun, 18 Apr 2004 12:27:22 -0400") References: <45342DB7-9155-11D8-A28E-000A95A0F1E8@randallsquared.com> Message-ID: Hi! On Sun, 18 Apr 2004 12:27:22 -0400, Randall Randall wrote: > I'm new to lisp and new to cl-ppcre. Welcome! I hope you'll have fun. > After building cl-ppcre, every time I start lisp, even if I don't > explicitly load cl-ppcre.ppcf, What's 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? No. > 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? Might be. But before I can say anything I need more details. Which version of CL-PPCRE? Which Lisp? (From the messages above I'd guess it's CMUCL or SBCL but who knows...) Which version of the compiler? Which operating system? How did you obtain and build CL-PPCRE? Manually? Using ASDF-INSTALL? Or did you use tools provided by your OS distribution like apt-get on Debian or the Ports system on FreeBSD? Cheers, Edi. From randall at randallsquared.com Mon Apr 19 00:35:47 2004 From: randall at randallsquared.com (Randall Randall) Date: Sun, 18 Apr 2004 20:35:47 -0400 Subject: [cl-ppcre-devel] (no subject) In-Reply-To: References: <45342DB7-9155-11D8-A28E-000A95A0F1E8@randallsquared.com> Message-ID: <8001113E-9199-11D8-BD2C-000A95A0F1E8@randallsquared.com> On Apr 18, 2004, at 2:04 PM, Edi Weitz wrote: > On Sun, 18 Apr 2004 12:27:22 -0400, Randall Randall > wrote: > >> I'm new to lisp and new to cl-ppcre. > > Welcome! I hope you'll have fun. Thank you! >> After building cl-ppcre, every time I start lisp, even if I don't >> explicitly load cl-ppcre.ppcf, > > What's cl-ppcre.ppcf? The compiled cl-ppcre library, if I understand correctly. I'm on Mac; otherwise it might be cl-ppcre.x86f . >> 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? > > Might be. But before I can say anything I need more details. Which > version of CL-PPCRE? Which Lisp? (From the messages above I'd guess > it's CMUCL or SBCL but who knows...) Which version of the compiler? > Which operating system? How did you obtain and build CL-PPCRE? > Manually? Using ASDF-INSTALL? Or did you use tools provided by your OS > distribution like apt-get on Debian or the Ports system on FreeBSD? Okay, I'm on OSX Panther (10.3), on a Powerbook. I'm using CMUCL for OSX, and in spite of various warnings about how it might cook and eat my cat, I haven't had that problem yet. I downloaded cl-ppcre-0.7.4 and followed the manual installation instructions in the doc/index.html included with it, since at that time I didn't have asdf or the other defsystem thing installed. After compilation, that file says one can simply concatenate the compiled files together (if one is using the Python compiler (and I'm using CMUCL, remember)), into a single file, cl-ppcre.x86f. Of course, I'm using ppc, not x86, so I assumed I knew what I was doing and changed it. In any case, I put in my .cmucl-init.lisp this line: (load "/Users/randall/Development/lisp/libraries/cl-ppcre-0.7.4/cl- ppcre.ppcf") which includes the path to that file. When starting lisp, I then got another compilation which resulted in the 150 or so lines mentioned earlier. This happens every time I start lisp. The library, in a cursory check, appears to work correctly using snippets copied from the documentation. The weird thing, though, is that I now find I don't need the load statement I just mentioned in my .cmucl-init.lisp file to get the laborious compile on startup. That makes me wonder if something's wrong. I also have an x86 Gentoo machine on which I used the system tools (emerge) to install cl-ppcre, and that went flawlessly, and doesn't do this. It also works correctly so far as I can tell. Thanks for your help! -- Randall Randall '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 at hotmail.com From randall at randallsquared.com Mon Apr 19 01:28:28 2004 From: randall at randallsquared.com (Randall Randall) Date: Sun, 18 Apr 2004 21:28:28 -0400 Subject: [cl-ppcre-devel] Startup issues [fixed] Message-ID: 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 '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 at hotmail.com From download at hpc.unm.edu Mon Apr 19 02:50:49 2004 From: download at hpc.unm.edu (Jim Prewett) Date: Sun, 18 Apr 2004 20:50:49 -0600 (MDT) Subject: [cl-ppcre-devel] Startup issues [fixed] In-Reply-To: Message-ID: no problem :) Jim On Sun, 18 Apr 2004, Randall Randall wrote: > 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 > '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 at hotmail.com > > > _______________________________________________ > cl-ppcre-devel site list > cl-ppcre-devel at common-lisp.net > http://common-lisp.net/mailman/listinfo/cl-ppcre-devel > -- James E. Prewett "everything that is, that was, was not enough" Systems Team Leader 505.277.8210 Designated Security Officer download at hpc.unm.edu Jim at Prewett.org HPC Systems Engineer III @ HPC at UNM OpenPGP key: pub 1024D/31816D93 From DKICK1 at motorola.com Mon Apr 19 18:40:29 2004 From: DKICK1 at motorola.com (Kick Damien-DKICK1) Date: Mon, 19 Apr 2004 13:40:29 -0500 Subject: [cl-ppcre-devel] Problems with a regexp using CL-PPCRE 0.7.4 Message-ID: <8E4E38BF6D087F4488E80ABAACA2F3F4B29F4E@il27exm02.cig.mot.com> Edi, Can you reproduce this behavior on your GNU/Linux setup? -----Original Message----- From: cl-ppcre-devel-bounces at common-lisp.net [mailto:cl-ppcre-devel-bounces at common-lisp.net] On Behalf Of Kick Damien-DKICK1 Sent: Sunday, 18 April, 2004 03:38 To: edi at agharta.de Cc: cl-ppcre-devel at common-lisp.net Subject: RE: [cl-ppcre-devel] Problems with a regexp using CL-PPCRE 0.7.4 Edi Weitz [edi at 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 # " kick Password:" (FUNCTION (T T T) (VALUES (OR NULL FIXNUM) &OPTIONAL T SIMPLE-VECTOR SIMPLE-VECTOR)) (BASE-STRING 1)) (BREAK-CL-PPCRE::EXPECT # " " (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))| # # # # ...) 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 at common-lisp.net http://common-lisp.net/mailman/listinfo/cl-ppcre-devel From edi at agharta.de Mon Apr 19 20:15:48 2004 From: edi at agharta.de (Edi Weitz) Date: Mon, 19 Apr 2004 22:15:48 +0200 Subject: [cl-ppcre-devel] New release 0.7.4 Message-ID: Hi! A new release is available from . 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. From edi at agharta.de Mon Apr 19 20:24:03 2004 From: edi at agharta.de (Edi Weitz) Date: Mon, 19 Apr 2004 22:24:03 +0200 Subject: [cl-ppcre-devel] It's 0.7.5!! (Was: New release 0.7.4) In-Reply-To: (Edi Weitz's message of "Mon, 19 Apr 2004 22:15:48 +0200") References: Message-ID: Subject says it all. That's the result if you just copy and paste... :) From edi at agharta.de Mon Apr 19 23:10:36 2004 From: edi at agharta.de (Edi Weitz) Date: Tue, 20 Apr 2004 01:10:36 +0200 Subject: [cl-ppcre-devel] Problems with a regexp using CL-PPCRE 0.7.4 In-Reply-To: <8E4E38BF6D087F4488E80ABAACA2F3F4B29F4E@il27exm02.cig.mot.com> (Kick Damien-DKICK's message of "Mon, 19 Apr 2004 13:40:29 -0500") References: <8E4E38BF6D087F4488E80ABAACA2F3F4B29F4E@il27exm02.cig.mot.com> Message-ID: On Mon, 19 Apr 2004 13:40:29 -0500, Kick Damien-DKICK1 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. Anyway, please try if you still get your bug with this version: Thanks, Edi. From DKICK1 at motorola.com Mon Apr 19 23:22:45 2004 From: DKICK1 at motorola.com (Kick Damien-DKICK1) Date: Mon, 19 Apr 2004 18:22:45 -0500 Subject: [cl-ppcre-devel] Problems with a regexp using CL-PPCRE 0.7.4 Message-ID: <8E4E38BF6D087F4488E80ABAACA2F3F4B29F53@il27exm02.cig.mot.com> Edi Weitz [edi at agharta.de] wrote: > On Mon, 19 Apr 2004 13:40:29 -0500, Kick Damien-DKICK1 > 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. [...] 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. From DKICK1 at motorola.com Tue Apr 20 03:55:59 2004 From: DKICK1 at motorola.com (Kick Damien-DKICK1) Date: Mon, 19 Apr 2004 22:55:59 -0500 Subject: [cl-ppcre-devel] Problems with a regexp using CL-PPCRE 0.7.4 Message-ID: <8E4E38BF6D087F4488E80ABAACA2F3F4B29F54@il27exm02.cig.mot.com> Edi Weitz [edi at 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. From edi at agharta.de Tue Apr 20 11:33:14 2004 From: edi at agharta.de (Edi Weitz) Date: Tue, 20 Apr 2004 13:33:14 +0200 Subject: [cl-ppcre-devel] Problems with a regexp using CL-PPCRE 0.7.4 In-Reply-To: <8E4E38BF6D087F4488E80ABAACA2F3F4B29F54@il27exm02.cig.mot.com> (Kick Damien-DKICK's message of "Mon, 19 Apr 2004 22:55:59 -0500") References: <8E4E38BF6D087F4488E80ABAACA2F3F4B29F54@il27exm02.cig.mot.com> Message-ID: On Mon, 19 Apr 2004 22:55:59 -0500, Kick Damien-DKICK1 wrote: > 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. Cool, I'll make a new release then. Thanks, Edi. From edi at agharta.de Tue Apr 20 11:43:32 2004 From: edi at agharta.de (Edi Weitz) Date: Tue, 20 Apr 2004 13:43:32 +0200 Subject: [cl-ppcre-devel] New release 0.7.6 Message-ID: Hi! A new release is available from . 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.