Checks for odd class declarations

[cpriest]

There are some cases which are not presently checked for which could lead to some odd class declarations, I'm opening this issue as a point of discussion to decide what to do:

class TimePeriod {
    private $Hours = 5;

    public $Hours {
        get { return 1; }
    }   
}

$o = new TimePeriod();
echo $o->Hours;    // Prints 1

Here we have defined a property and a property accessor of the same name, in v1.2 the accessor will shadow the property so this isn't a problem per say, but should we allow it or should it throw a compile error?

Also see Issue #10

[nikic]

I think this one should be a compile error. (This will probably be automatically solved when propery_info and accessor_info are merged.)

[cpriest]

I would agree

[cpriest]

This has been fixed by b04e5b0