January 2008 - cl-ppcre-devel@common-lisp.net

[cl-ppcre-devel] "(?x)rewith#" differs from "rewith#" :extended-mode t
by terrence.x.brannon＠jpmchase.com 16 Jan '08

16 Jan '08

In Perl, the same results are returned for both means of extended mode processing: $a = 'aba#'; $b = $a; $a =~ s!aba#!!x; $b =~ s!(?x)aba#!!; warn $a; warn $b; In cl-ppcre, the results differ: (setf a "aba#") (setf b "aba#") (regex-replace "aba#" a "" :extended-mode t) (regex-replace "(?x)aba#" b "") -- Terrence Brannon - SID W049945 614-213-2475 (office) 614-213-3426 (fax) 818-359-0893 (cell) ----------------------------------------- This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates. This transmission may contain information that is privileged, confidential, legally privileged, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMorgan Chase & Co., its subsidiaries and affiliates, as applicable, for any loss or damage arising in any way from its use. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures relating to UK legal entities.

3 2

[cl-ppcre-devel] more readable archive of this list?
by terrence.x.brannon＠jpmchase.com 15 Jan '08

15 Jan '08

Hi, Could we create a google group archive of this list? The current archive - http://common-lisp.net/mailman/listinfo/cl-ppcre-devel - is not very browseable or searchable. -- Terrence Brannon - SID W049945 614-213-2475 (office) 614-213-3426 (fax) 818-359-0893 (cell) ----------------------------------------- This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates. This transmission may contain information that is privileged, confidential, legally privileged, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMorgan Chase & Co., its subsidiaries and affiliates, as applicable, for any loss or damage arising in any way from its use. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures relating to UK legal entities.

2 3

[cl-ppcre-devel] cl-ppcre::parse-string - does anyone else want it to take the mode flags?
by terrence.x.brannon＠jpmchase.com 15 Jan '08

15 Jan '08

I ran across that misfeature with "#" because I could not pass :extended mode t to the parse-string function, which I use for debugging my regexps. So, I was forced to prepend "(?x)" to my regexps. I wonder if anyone else had a need for passing flags to parse-string: (defun myre (inre &key (dbg nil)) (let ((re (concatenate 'string "(?ix)" inre))) (if dbg (cl-ppcre::parse-string re) (create-scanner re)))) -- Terrence Brannon - SID W049945 614-213-2475 (office) 614-213-3426 (fax) 818-359-0893 (cell) ----------------------------------------- This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates. This transmission may contain information that is privileged, confidential, legally privileged, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMorgan Chase & Co., its subsidiaries and affiliates, as applicable, for any loss or damage arising in any way from its use. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures relating to UK legal entities.

2 1

[cl-ppcre-devel] using cl-ppcre functions without package prefixes
by terrence.x.brannon＠jpmchase.com 10 Jan '08

10 Jan '08

Hello, I know this is more of just a pure Lisp question, but i cannot figure out how to get my Lisp program to use cl-ppcre without having to prefix the function calls with 'cl-ppcre' My application is using ASDF to define and load itself: (asdf:defsystem bank-match :description "Approximate bank matching" :author "Terrence M. Brannon" :maintainer "Terrence M. Brannon" :licence "Artistic" :version "1.0" :serial t :depends-on ("cl-ppcre") :components ( (:file "clean") ) ) (in-package :bank-match) (defun crude-hacks (s) "crude hacks :)" (cl-ppcre:regex-replace "head\\s*office" (cl-ppcre:regex-replace "due\\s*from" (cl-ppcre:regex-replace "hapoalim\\s*branch" s "hapoalim bank") " ") " ") ) -- Terrence Brannon - SID W049945 614-213-2475 (office) 614-213-3426 (fax) 818-359-0893 (cell) ----------------------------------------- This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates. This transmission may contain information that is privileged, confidential, legally privileged, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMorgan Chase & Co., its subsidiaries and affiliates, as applicable, for any loss or damage arising in any way from its use. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures relating to UK legal entities.

4 6

[cl-ppcre-devel] Potential bug in 1.0.13: LDB prompth when using CL-PPCRE.
by Victor Kryukov 06 Jan '08

06 Jan '08

Hi SBCL developers, The following program brings LDB> prompt for me. sbcl-bug.lisp ----- (require 'asdf) (asdf:oos 'asdf:load-op 'cl-ppcre) (funcall (cl-ppcre:create-scanner "test") "This is a test") --- victor@esculap:~/src/sbcl-1.0.13$ sbcl --no-userinit --no-sysinit --load ../lisp/sbcl-bug.lisp This is SBCL 1.0.13, an implementation of ANSI Common Lisp. More information about SBCL is available at <http://www.sbcl.org/>. SBCL is free software, provided as is, with absolutely no warranty. It is mostly in the public domain; some portions are provided under BSD-style licenses. See the CREDITS and COPYING files in the distribution for more information. ; loading system definition from /home/victor/.sbcl/systems/cl-ppcre.asd into ; #<PACKAGE "ASDF0"> ; registering #<SYSTEM :CL-PPCRE {10024BF111}> as CL-PPCRE fatal error encountered in SBCL pid 20308(tid 47999199878832): no scavenge function for object 0x00f670fc (widetag 0x0) Welcome to LDB, a low-level debugger for the Lisp runtime environment. ldb> I'm using Ubuntu 7.10 on x86-64: victor@esculap:~$ uname -a Linux esculap 2.6.22-14-generic #1 SMP Tue Dec 18 05:28:27 UTC 2007 x86_64 GNU/Linux SBCL is 1.0.13 manually compiled from sources with :SB-THREAD enabled. CL-PPCRE is Edi Weitz's library, version 1.3.2 (ASDF-installable, http://weitz.de) I'd be happy to provide more info if needed. -- Yours Sincerely, Victor Kryukov

2 3