On Wed, 31 Jan 2001, Anil Madhavapeddy wrote:
> Well, given that the aim of the function is to be as perl-compatible, it
> would be nice to make this default behaviour. The breakage of any scripts
> would be pretty easy to spot, if they did use brackets wrongly, so an entry in
> NEWS ought to en
Quoting Andrei Zmievski <[EMAIL PROTECTED]>:
> I could add this functionality but I am not sure if it would break
> people's scripts because they used parentheses without expecting to
> receive captured delimiters. What does everyone think? Should it be that
> way by default or should we have ano
On Wed, 31 Jan 2001, [EMAIL PROTECTED] wrote:
> The brackets aren't captured, which makes the Scheme parsing a bit difficult :-)
>There are other ways to do this, of course, but the preg_split() would be the
>simplest and the most efficient way to do it, as far as we can see.
>
> I noticed tha
you gotta escape the escapes
$b = preg_split('/([\\(\\)])/', $a);
Greetz,
Wico
At 13:13 31-1-01 +, [EMAIL PROTECTED] wrote:
>From: [EMAIL PROTECTED]
>Operating system: OpenBSD 2.8
>PHP version: 4.0.4pl1
>PHP Bug Type: PCRE related
>Bug description: preg_split inconsi
From: [EMAIL PROTECTED]
Operating system: OpenBSD 2.8
PHP version: 4.0.4pl1
PHP Bug Type: PCRE related
Bug description: preg_split inconsistency
While trying to write a simple Scheme parser in PHP, we encountered this problem:
In perl, you can capture the delimiters passed
