At 08:39 14-12-2002, Moriyoshi Koizumi wrote:
> >This is a pretty well known issue indeed.
> >I should have read the archive carefully.
> >
> >Related reports:
> >http://bugs.php.net/bug.php?id=6417
> >http://bugs.php.net/bug.php?id=7412
> >http://bugs.php.net/bug.php?id=7515
> >http://bugs.php.net/bug.php?id=15025
>
> I wouldn't like to call it 'well-known'.
Misleading words? What I meant was "this turned out to be a pretty well
known issue"... hardly had I noticed this problem until I saw this report,
I found several related reports during the investigation. So I regarded it
as a kind of them.
OK - you're forgiven :)
> And I don't like the implications of 1 perfectly valid statement, impacting
> the scope of an array in a non-documented and plain wrong manner.
Is it okay to always perform separation on all the elements of passed
arrays? If so, the attached patch should work.
> IF this can't be fixed short term, we surely could detect the statement and
> issue a warning?
AFAIK possible. We'll have to trade off performance against usability.
My proposal, was based on 2 things: fix or document. I'm sure Zeev/Andi had a
good reason not to always separate, and that probably is performance.
IF this impacts overall performance very negatively, then maybe the better
choice is to document it.
I'll try the patch though.
With kind regards,
Melvyn Sopacua
<?php include("not_reflecting_employers_views.txt"); ?>
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, visit: http://www.php.net/unsub.php
