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

[cl-ppcre-devel] CL-PPCRE 2.0.0, CL-INTERPOL 0.2.0, CL-UNICODE 0.1.0
by Edi Weitz 23 Jul '08

23 Jul '08

This is a joint announcement for two significant updates and one brand-new library which are all somehow related. See the changelogs for all the details. http://weitz.de/cl-ppcre/ http://weitz.de/cl-unicode/ http://weitz.de/cl-interpol/ Edi.

1 0

[cl-ppcre-devel] slow matching
by Carlos Konstanski 23 Jul '08

23 Jul '08

I was not on the list at the time that Edi posted the message "1.4.0/1 performance" which is why I am posting a new one instead of replying. I am using threaded SBCL 1.0.18 on gentoo amd64. On my platform, matching has slowed to a crawl. It takes 1.5 to 2 seconds to perform the following match: (cl-ppcre:all-matches-as-strings "^\\d\\d\\d\\d-\\d\\d-\\d\\d\\d\\d:\\d\\d:\\d\\d\.0$" <anystring>) I'm sure I could write this regex better. Nevertheless it runs hundreds of times slower than it did previously. I'll test on the same setup with x86 and give a report. Carlos Konstanski

2 3

[cl-ppcre-devel] Using scan
by Dave Pawson 07 Jul '08

07 Jul '08

file:///files/lisp/email/cl-ppcre/doc/index.html#scan On success returns four values and 2 arrays. But not in a list? How to access these values please? TIA -- Dave Pawson XSLT XSL-FO FAQ. http://www.dpawson.co.uk

3 7

[cl-ppcre-devel] Bug?
by Dave Pawson 07 Jul '08

07 Jul '08

Input text * Representatives from <Sun> & <Novell> versions) & <Symphony>, <KOffice>, <Google> Docs & Spreadsheets and Microsoft Office. code (defun msg(message) (format t "~%~A~%" message) ) (defun cleanup (line) "Replace < and & with entities" (msg (cl-ppcre:regex-replace-all "&" line "&")) (msg (cl-ppcre:regex-replace-all "<" line "<")) ) The first message replaces & The second shows that & has been changed back to & * Representatives from <Sun> & <Novell> versions) & <Symphony>, <KOffice>, <Google> Docs & Spreadsheets and Microsoft Office. * Representatives from <Sun> & <Novell> versions) & <Symphony>, <KOffice>, <Google> Docs & Spreadsheets and Microsoft Office. regards -- Dave Pawson XSLT XSL-FO FAQ. http://www.dpawson.co.uk

2 2

[cl-ppcre-devel] 1.4.0/1 performance
by Edi Weitz 03 Jul '08

03 Jul '08

Hi, The recent 1.4.x release which replaced hash tables with a "charset" implementation by Nikodemus was meant to make scanner creation cheaper while not sacrificing matching performance (ideally increasing it). I have to admit I haven't tested this a lot before releasing it (except for correctness), but there seems to be some evidence that scanners are significantly slower now for some Lisps. I'd be interested in your experiences on different platforms. This change should only affect regular expressions with character classes and it should only make a difference for large values of *REGEX-CHAR-CODE-LIMIT*. If you see significant changes in that area, good or bad, please let me know, including your Lisp and OS. If the majority sees a degradation, I might just revoke this change. Thanks, Edi.

1 0

[cl-ppcre-devel] New release 1.4.0
by Edi Weitz 03 Jul '08

03 Jul '08

ChangeLog: Version 1.4.0 2008-07-03 Replaced hash tables with charsets (by Nikodemus Siivola) Get rid of duplicates in REGEX-APROPOS(-LIST) Download: http://weitz.de/cl-ppcre.tar.gz Edi.

1 1

[cl-ppcre-devel] New release 1.4.1
by Edi Weitz 03 Jul '08

03 Jul '08

ChangeLog: Version 1.4.1 2008-07-03 Skip non-characters in CREATE-RANGES-FROM-SET Download: http://weitz.de/files/cl-ppcre.tar.gz Edi.

1 0

[cl-ppcre-devel] New release 1.3.3
by Edi Weitz 25 Jun '08

25 Jun '08

ChangeLog: Version 1.3.3 2008-06-25 Let the Lisp decide how it wants to enlarge its hash tables Fixed anchors for special variables in docs Fixed typo in docs (thanks to Jason S. Cornez) Download: http://weitz.de/files/cl-ppcre.tar.gz

1 0

[cl-ppcre-devel] alternative to parse-string
by Andy Chambers 28 Feb '08

28 Feb '08

Hi Edi, I'm trying to write a lexer where one can use previously defined classes in subsequent regular expressions. For example you'd be able to do something like this.... (deflexer my-lexer (ws "[ \t\n]") (letter "[a-zA-Z]") (word (:greedy-repetition 0 nil letter))) To make this work, the deflexer macro substitutes letter for the parse-tree resulting from (parse-string "[a-zA-Z]"). I wrote this before realizing that parse-string was not exported. Is there another (more future-proof) way to get at the parse-tree for a regex in a way that it can be combined with other trees? Cheers, Andy

2 1

[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