Hi,
If visibility is an issue why not just use json_enode/decode for this
case then?it doesn't seem like a typical enough problem to be solved
low-level and json seems fast enough for the job ;-)
Hi,
I don't know whether it should be fixed or not, but it definitely shouldn't
have received resolution "Bogus" in the bugbase.
"Bogus" means the issue doesn't exist as described, is not caused by PHP, or
it's part of the expected, intended, documented behavior of the language. In
this case the issue is an undocumented edge case, it's counterintuitive, and
it's reproducible with the provided code. If it not feasible to fix due to
performance reason, the resolution should be "Won't Fix".
Marking a real issue as a bogus one deprives people who work on PHP from
having a handy log of issues that could be reviewed and possibly fixed at a
later point as the egine changes and a solution no longer is a BC or
performance issue. It's also insulting to the submitter, who took from his
time to file an actual problem and was basically dismissed as uninformed on
the issue.
Regards,
Stan Vassilev
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
