Quoting Brad LaFountain <[EMAIL PROTECTED]>:
> Should be fixed. I swear there better not be anything else wrong with
> that code chage :) I know alot more how the engine handles arrays now :)
Confirming that things seem to work as expected now.
-chuck
--
Charles Hagenbuch, <[EMAIL PROTECTE
Should be fixed. I swear there better not be anything else wrong with that
code chage :) I know alot more how the engine handles arrays now :)
- brad
--- Dan Kalowsky <[EMAIL PROTECTED]> wrote:
> Correction an update from a few mins ago results in the same output as
> Chuck's original.
>
> O
Correction an update from a few mins ago results in the same output as
Chuck's original.
On Fri, 2 Aug 2002, Chuck Hagenbuch wrote:
> With latest CVS (HEAD branch, checked out 10 or so minutes ago), the
> following script:
>
>
> error_reporting(E_ALL);
> $text = "Before delim.\n--\nAfter delim"
My output looks a lot different than yours and I'm not receiving the
notices you are. Same script only on OSX debug from the CLI.
array(3) {
[0]=>
string(10) "
--
"
[1]=>
string(6) ""
[2]=>
string(11) "After delim"
}
End of script
CVS HEAD from earlier this morning (arond 9 am
With latest CVS (HEAD branch, checked out 10 or so minutes ago), the
following script:
\n--\nAfter delim";
$parts = preg_split('|(\n--\s*()?\n)|', $text, 2, PREG_SPLIT_DELIM_CAPTURE);
$text = array_shift($parts);
if (count($parts)) {
echo ''; var_dump($parts);
$text .= $parts[0];
$te
