cl-ppcre-devel

cl-ppcre-devel@common-lisp.net

182 discussions

[cl-ppcre-devel] benchmarking cl-ppcre?
by Jim Prewett 30 Dec '05

30 Dec '05

Hi, I'd like to compare cl-ppcre's performance on different systems. It seemed to me that the benchmarks (under #performance on the webpage) are more focused on comparing Perl to CL-PPCRE. Is that true? Anyone have thoughts on how to benchmark different systems in this way? Thanks, Jim James E. Prewett Jim(a)Prewett.org download(a)hpc.unm.edu Systems Team Leader LoGS: http://www.hpc.unm.edu/~download/LoGS/ Designated Security Officer OpenPGP key: pub 1024D/31816D93 HPC Systems Engineer III UNM HPC 505.277.8210

2 1

[cl-ppcre-devel] problem (bug?) with do-register-groups
by tichy 06 Dec '05

06 Dec '05

#| Hi. I think there is a bug in cl-ppcre (do-register-groups). I wrote two almost identical versions of function 'dtd-attributes-to-sexp'. One with 'do-register-groups' hangs, another which uses 'scan' works. example: (dtd-attributes-to-sexp "attr-foo (foo | bar) \"foo\" attr-bar CDATA #FIXED 'zonk' attr-baz NMTOKEN #REQUIRED") result without 'read-dtd-parens': (("attr-foo" "(foo | bar)" "foo") ("attr-bar" :CDATA (:FIXED "zonk")) ("attr-baz" :NMTOKEN :REQUIRED)) result with 'read-dtd-parens': (("attr-foo" (:ALTERNATION 1 "foo" "bar") "foo") ("attr-bar" :CDATA (:FIXED "zonk")) ("attr-baz" :NMTOKEN :REQUIRED)) |# (use-package :cl-ppcre) (defparameter *dtd-attribute-name-regex* "([a-zA-z0-9._\\-:]+)") (defparameter *dtd-attribute-type-regex* "(?:(\$.*?\$)|(CDATA)|(ID)|(IDREF)|(IDREFS)|(NMTOKEN)|(NMTOKENS)|(ENTITY)|(ENTITIES)|(NOTATION)|(xml:\\w+))") (defparameter *dtd-attribute-default-value-regex* "(?:('[^<>\"']*')|(\"[^<>\"]*\")|(#REQUIRED)|(#IMPLIED)|(?:#FIXED\\s+(?:('[^<>\"']*')|(\"[^<>\"]*\"))))") ;;; ---------- buggy 'dtd-attributes-to-sexp' ---------- ;; Version with 'do-register-groups' macro. It works only without call ;; to 'read-dtd-parens' (which 'read-dtd...' uses 'cl-ppcre:scan'). ;; 'read-dtd-parens' itself seems to be ok. ;; I think 'do-register-groups' has a bug. ;; (defun dtd-attributes-to-sexp (target &aux result) (do-register-groups (a b1 b2 b3 b4 b5 b6 b7 b8 b9 b10 b11 c1 c2 c3 c4 c5.1 c5.2) ((format nil "\\s*~A\\s+~A\\s+~A\\s*" ; no load-time-value beause it's an example. *dtd-attribute-name-regex* *dtd-attribute-type-regex* *dtd-attribute-default-value-regex*) target (nreverse result)) (push (list a (cond (b1 (read-dtd-parens b1)) #| *** !!!!!! *** |# (b2 :cdata) (b3 :id) (b4 :idref) (b5 :idrefs) (b6 :nmtoken) (b7 :nmtokens) (b8 :entity) (b9 :entities) (b10 :notation) (b11 b11)) (cond (c1 (subseq c1 1 (1- (length c1)))) (c2 (subseq c2 1 (1- (length c2)))) (c3 :required) (c4 :implied) (c5.1 (list :fixed (subseq c5.1 1 (1- (length c5.1))))) (c5.2 (list :fixed (subseq c5.2 1 (1- (length c5.2))))))) result))) ;;; ---------- 'dtd-attributes-to-sexp' that works ---------- ;; Version without 'do-register-groups', i used 'scan' instead of it. ;; It works as intended. ;; (defun dtd-attributes-to-sexp (string &aux result (start 0)) (loop (multiple-value-bind (m-start m-end r-start r-end) (scan (format nil "\\s*~A\\s+~A\\s+~A\\s*" ; no load-time-value beause it's an example. *dtd-attribute-name-regex* *dtd-attribute-type-regex* *dtd-attribute-default-value-regex*) string :start start) (declare (ignore m-start)) (push (list (subseq string (svref r-start 0) (svref r-end 0)) (case (position-if #'identity r-start :start 1) (1 (read-dtd-parens (subseq string (svref r-start 1) (svref r-end 1)))) (2 :cdata) (3 :id) (4 :idref) (5 :idrefs) (6 :nmtoken) (7 :nmtokens) (8 :entity) (9 :entities) (10 :notation) (11 (subseq string (svref r-start 11) (svref r-end 11)))) (case (position-if #'identity r-start :start 12) (12 (subseq string (1+ (svref r-start 12)) (1- (svref r-end 12)))) (13 (subseq string (1+ (svref r-start 13)) (1- (svref r-end 13)))) (14 :required) (15 :implied) (16 (list :fixed (subseq string (1+ (svref r-start 16)) (1- (svref r-end 16))))) (17 (list :fixed (subseq string (1+ (svref r-start 17)) (1- (svref r-end 17))))))) result) (when (eql m-end (length string)) (return (nreverse result))) (setq start m-end)))) ;; This function is meant to be a pareser to fragments of dtd's ;; 'element' and "attribute' tags. ;; for example: ;; ;; (read-dtd-parens "(e | f)") ;; ;; ===> (:ALTERNATION 1 "e" "f") ;; ;; or ;; ;; (read-dtd-parens "((script|style|meta|link|object)*, ((title, (script|style|meta|link|object)*, (base, (script|style|meta|link|object)*)?) | (base, (script|style|meta|link|object)*, (title, (script|style|meta|link|object)*))))") ;; ;; ===> big sexp :) ;; (defun read-dtd-parens (string &optional (start 0) &aux match-begin match-end result reg type stuff (index (1+ start))) (loop (cond ((char= #$ (char string index)) (multiple-value-setq (stuff index) (read-dtd-parens string index)) (push stuff result)) ((multiple-value-setq (match-begin match-end) (scan (load-time-value (create-scanner "^\\w+") t) string :start index)) (setq index match-end) (if (find (char string match-end) "+*?") (progn (push (list (intern (string (char string match-end))) (subseq string match-begin match-end)) result) (incf index)) (push (subseq string match-begin match-end) result))) ((multiple-value-setq (match-begin match-end reg) (scan (case type (:alternation (load-time-value (create-scanner "^\\s*\\|\\s*") t)) (:sequence (load-time-value (create-scanner "^\\s*,\\s*") t)) ('nil (load-time-value (create-scanner "^\\s*(?:(\\|)|(,))\\s*") t))) string :start index)) (unless type (setq type (if (svref reg 0) :alternation :sequence))) (setq index match-end)) ((char= #$ (char string index)) (setq result (nreverse result)) (return (case (if (array-in-bounds-p string (1+ index)) (char string (1+ index))) (#\* (values (cons type (cons '* result)) (+ 2 index))) (#\? (values (cons type (cons '? result)) (+ 2 index))) (#\+ (values (cons type (cons '+ result)) (+ 2 index))) (t (values (cons type (cons '1 result)) (+ 1 index))))))))) ;;; ---------- END.

2 1

[cl-ppcre-devel] Re: does CL-PPCRE have a stream interface?
by Edi Weitz 25 Nov '05

25 Nov '05

[Cc to mailing list.] No. This won't be easy because of all the backtracking involved, and I have no plans to add that. There's a modified version of CL-PPCRE which handles arbitrary sequences but I guess this won't help you very much: <http://comments.gmane.org/gmane.lisp.climacs.devel/160> Cheers, Edi.

1 0

[cl-ppcre-devel] recursive parsing
by Igor Plekhov 18 Nov '05

18 Nov '05

How can be done recursive parsing with CL-PPCRE? For example infix arithmetic expressions with parentheses.. -- Registered Linux User #124759

2 1

[cl-ppcre-devel] New version 1.2.12
by Edi Weitz 01 Nov '05

01 Nov '05

ChangeLog: Version 1.2.12 2005-11-01 REGEX-APROPOS-AUX now also uses :INHERITED Fixed typo in parser.lisp (thanks to Derek Peschel) Fixed value of *REGEX-CHAR-CODE-LIMIT* in docs and test (thanks to Christophe Rhodes) Download: <http://weitz.de/files/cl-ppcre.tar.gz> Cheers, Edi.

1 0

[cl-ppcre-devel] define-parse-tree-synonym
by Igor Plekhov 12 Oct '05

12 Oct '05

Small file (aa.lisp) with examples from the cl-ppcre documentation: (defpackage :aa (:use :common-lisp :cl-ppcre)) (in-package :aa) (define-parse-tree-synonym a-z (:char-class (:range #\a #\z) (:range #\a #\z))) (define-parse-tree-synonym a-z* (:greedy-repetition 0 nil a-z)) (defun ascii-char-tester (string) (scan '(:sequence :start-anchor a-z* :end-anchor) string)) If I just load this file than all is ok. If I compile it first and then load aa.x86f (I use CMUCL) than it stops with error: Unknown token A-Z* in parse-tree [Condition of type PPCRE-SYNTAX-ERROR] Restarts: 0: [CONTINUE] Return NIL from load of "aa.x86f". 1: [ABORT ] Return to Top-Level. Debug (type H for help) (CL-PPCRE::CONVERT-AUX #<unavailable-arg>) Why does it not work? -- Registered Linux User #124759

2 5

[cl-ppcre-devel] Loading of the package takes a long time...
by Andrew Stebakov 06 Oct '05

06 Oct '05

Hi, I just installed the package. The funcionality looks great but what really concerns me is the load time. It takes up to 15 sec to load it when I issue (asdf:oos 'asdf:load-op 'cl-ppcre) command. (I use Clisp on Win2K CPU PIII @ 600MHz, not much I know :). I am wondering if I create a stand-alone binary or use it as a shell script will it load that long every time the script will be executed? Is there a way to shorten the loading time (maybe select not all files? May be there is some "light" version of the package?) Thank you, Andrei __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com

3 3

[cl-ppcre-devel] Re: [cl-pdf-devel] Unicode/ISO-8859-2
by Marc Battyani 26 Sep '05

26 Sep '05

"Levente Mészáros" <levente.meszaros(a)mailbox.hu> wrote: > I found out that Ohungarumlaut and Odblacute (and similarily for the others) > are interchangeable for acrobat reader, but not for gsview. Perhaps they > just changed the name. > > Also tried two shareware pdf viewers, but with even worse results. In this > case I think it's clearly the viewers' fault. > > I tried with different fonts (Helvetica, Arial), but got the same results > with acrobat reader. > > Unfortunately xpdf doesn't run on windows so I've just downloaded the newest > gsview stuff and hungarumlaut is OK as you said when I view the pdf with it! > > But what is more interesting is that I've got good results with acrobat > reader when I use the fonts that come with the gs stuff. I don't know what > is the difference, but included a few examples for you! Cool. > I think you might be right that acrobat reader's default fonts may have some > problems. Yes. It seems unbelievable, but I don't see any other reason why the pdf works with every non default font. At least you have a working solution now ;-) Marc

1 1

Re: [cl-ppcre-devel] Roles of scanner vs. parser vs. lexer?
by Edi Weitz 04 Aug '05

04 Aug '05

[You forgot to Cc the mailing list.] On Wed, 3 Aug 2005 15:49:58 -0700, Derek Peschel <dpeschel(a)eskimo.com> wrote: > CL-PPCRE makes a start, with a grammar and a set of token types that > the lexer produces. The problem, as you know, is how to make sure > the specification is complete while stating it in a way that's not > tied to a particular implementation. All the context-sensitive > tricks (extended mode, backreference vs. octal constants, \Q and \E) > make the spec harder to check too. Definitely. I'm afraid I won't be able to help very much, though. CL-PPCRE's parser/lexer is very much an ad hoc implementation and it's the first parser I ever wrote. > Climacs's syntax highlighters work with parse trees, so CL-PPCRE's > use of them seemed to make it a good match for Climacs. I think > Climacs needs to reconstruct the original text from the parse tree, > and it parses the text incrementally, and a good syntax module will > flag errors yet allow further changes to the text. So I don't know > if the Climacs parse tree could be ready to pass to CL-PPCRE. But > that would be ideal. Without knowing anything about Climacs' internals: How about using CL-PPCRE::PARSE-STRING and feeding the result to Climacs? > Are dangling \Es legal in Perl too? Yep. edi@vmware:~$ perl -le '$a = "\Q*\E\E"; print $a' \* Cheers, Edi.

2 2

[cl-ppcre-devel] Roles of scanner vs. parser vs. lexer?
by Derek Peschel 03 Aug '05

03 Aug '05

Hi everybody, I've been reading the CL-PPCRE docs and code to get a clear specification of the syntax. Ultimately I'd like to add syntax highlighting for CL-PPCRE regexps to the Climacs text editor. But there seems to be a certain amount of defensive or sloppy programming (things being done in more than one place). The scanner knows something about skipping # comments but the lexer does too. The lexer has code to ignore \E markers but I get the impression the scanner removes them before the lexer starts. If this kind of duplication does exist, is there a useful reason for it? -- Derek

2 1

← Newer
1
...
7
8
9
10
11
12
13
...
19
Older →

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