Ferenc Kovacs wrote:
Did you managed to read the whole thread?
I'm asking because there were lot of confusion about the actual impact of
this problem, and Lester particularly seemed confused.
"There is nothing really wrong with the current code except that the sub
keys have yet to be populated."
that isn't true, if the array or some sub elements are empty("yet to be
populated"), you won't bump into this change. See my previous mail for the
exact details.
My genealogical data site is not working on PHP5.4 ... the arrays of information
are not being populated ... WHEN I get some time I will go through things with a
fine tooth comb, but for the time being 5.4 is unusable for that site. The same
phpgedview code is used by many sites, and while it may simply be my port to
Firebird that has the problem, I suspect other sites will be affected. I've
tested PHP5.4 ... and it does not work for me ... in much the same way 5.3
didn't and needed a lot of work to get things ported over. Looks to me like
EXACTLY the same agro for many users this time as well :( All right the code may
be at fault, but much of it originated in PHP4 days and tracking these sorts of
black holes is not simple ... otherwise I would know why my site does not work now!
Other people have flagged a problem, although it would seem that showing where
the problems are is not being followed up, so can people sign off on this change
that it will NOT affect production sites? More important if it does affect a
site how does one find the problem code? If it worked but gave warnings that
would at least be a little better ...
--
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk//
Firebird - http://www.firebirdsql.org/index.php
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php