Re: Re: protected abstract static function ... E_STRICT
| From: | Lester Caine | Date: | Thu, 12 Mar 2015 09:24:59 +0000 |
| Subject: | Re: Re: protected abstract static function ... E_STRICT | ||
| References: | 1 2 3 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-324633@lists.php.net to get a copy of this message | ||
On 12/03/15 09:05, Johannes Ott wrote:
> The constructor is doing somethings more, which I didn't write in the
> example, so I don't want to reimplement in each subclass. A dynamic
> method isValid() might be a solution but I have to think about this,
> because maybe the isValid should become a public static function in
> future for some needs.
One of the problems I found when addressing the E_STRICT issue is that
the base classes were the whole problem and one ended up tidying and
even duplicating functions and isValid is one of those functions where
if $this-> is set you want one path, otherwise you want another. So one
ends up with a static safe isValid and an internal isLoaded. In any case
even third party libraries needed a little work to ensure E_STRICT
compliance and I still hit problems even today althoguh it's been a rule
on my systems for the 5+ years.
--
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
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk