nbtrap

Tested on SBCL, ECL, and CLISP. The documentation says that subpattern refs were added in version 2.1.0, so you might want to change that if you don't bump the version...

Suggested changes have been made.

I can think of two reasons: 1. Perl allows you to incrementally build regexes. For example, you can do this: ``` perl $rx1 = qr/\k/ $rx2 = qr/(?.)$rx1/ ``` If...

Crap. I didn't know CL-PPCRE tries to match named backreferences against every register with a given name. This complicates things. Here are the options as I see them: 1. Extend...

Are you in a position to ask him?

To be clear, I wasn't saying named registers are unnecessary. What I am saying is that it's unnecessary to have to bind a variable to use them. Deprecating the `*ALLOW-NAMED-REGISTERS*`...

1. I don't want to remove `*ALLOW-NAMED-REGISTERS*`, I'm just suggesting allowing named registers regardless of its value. 2. Yes, deprecating `*ALLOW-NAMED-REGISTERS*` might break anomalous code that relies on `PARSE-STRING` throwing...

That said, I don't want to get carried away with the `*ALLOW-NAMED-REGISTERS*` bit. This issue is about how CL-PPCRE handles named backreferences.

I don't think that's right. The reason it works with 'c' instead of '[c]' is that the optimizer causes the scanner to fail ab initio if it sees that the...

nhabedi [email protected] writes: > Even if you had that back, you'd run into the same problem if you > replaced '[c]' with, say, '[cd]'. Yes, that's what I was trying...