Re: Re: Bug #1683 Updated: Failing to parse/compile a *? pattern.

> No, actually, I was referring to stuff that is explained in the regex.7 > POSIX spec man page you include with php. > > Paragraph 9: > > Within a bracket expression, a collating element (a char- > acter, a multi-character sequence that collates as if it > were a single character, or a collating-sequence name for > either) enclosed in [.' and .]' stands for > the sequence > of characters of that collating element. The sequence is > a single element of the bracket expression's list. A > bracket expression containing a multi-character collating > element can thus match more than one character, e.g. if > the collating sequence includes a `ch' collating element, > then the RE `[[.ch.]]*c' matches the first five characters > of `chchcc'. > > But no matter. preg with non-greedy matching will do it, if I can ever > make preg work. In my stand alone test program, the preg regexp "/\//" is > fine and works. In the actual program I'm trying to replace an egreg with > it, it tells me "illegal escape sequence \/". I'm about to give up and let > someone else fix this Phorum bug. :) But collating elements work fine. eg. echo ereg_replace("[.ch.]+c", "bob", "chchcc tom"); this prints: "bob tom" -Rasmus