cl-ppcre-devel

Download

cl-ppcre-devel@common-lisp.net

April 2015

4 participants
2 discussions

Only strings as names for :named-registers?
by Philipp Marek 08 Apr '15

08 Apr '15

Hi, I wondered why :named-register only allows to use strings as name. I'd like to use a symbol, or, for macro-generated forms, gensyms, because that would be easier for macro-generated forms to associate with the resulting capture index. Sadly symbols don't work currently because of COPY-SEQ in METHOD CONVERT-COMPOUND-PARSE-TREE ((EQL :NAMED-REGISTER) T) Even more, the COPY-SEQ destroys EQuality, so I cannot give some string and look for it later on. What's the reason for the string-requirement? Could we allow symbols, too? Thanks for all answers. Regards, Phil

2 1

Extending regexps to other kinds of sequences
by Ron Garret 08 Apr '15

08 Apr '15

The theory of regular expressions can be applied to any kind of sequence, not just strings. This would be potentially useful for pattern-matching applications, where current approaches make it very cumbersome to say things like, “Match a list containing between three and five integers”. This sort of thing is easy to express in CL-PPCRE tree-like notation as, e.g. (:repetition (:type integer) 3 5) My question is: how hard would be it be to adapt the CL-PPCRE code to handle things like this? Is there a sequence-type-agnostic core in CL-PPCRE that could be easily re-used for this purpose, or is the assumption that regexps only apply to strings woven deeply into the code? Thanks, rg

4 4