On Tue, Oct 12, 2010 at 2:00 PM, Antony Dovgal wrote:
> On 10/11/2010 10:35 PM, Michael Felt wrote:
> > As to 5.3 - personally, I have some oldish PHP code that does not like
> > some of the new defaults in 5.3 (as least when I tried when it first
> > came out). However, I shall soon do 5.2.14.
>
Hi!
3) The use case for this function required the existing behavior
(i.e. can you safely call property $x from the current scope with no
warning?), and that *ignored* when the behavior was changed. We
already have Reflection classes for inquiring protected/private
properties of a class from any
I think this is a great case study that could lead to some improvements in the
process of fixing bugs in PHP:
http://bugs.php.net/bug.php?id=45743
A potential bug was reported on property_exists() that it won't report
inaccessible properties in the scope.
The problem is this was, in fact, the i
On 10/11/2010 10:35 PM, Michael Felt wrote:
> As to 5.3 - personally, I have some oldish PHP code that does not like
> some of the new defaults in 5.3 (as least when I tried when it first
> came out). However, I shall soon do 5.2.14.
I'd still recommend at least _to try_ 5.3 just to make sure it r
