Nathan Rixham schreef:
> Nathan Rixham wrote:
>> Jochem Maas wrote:
>>> Olivier Doucet schreef:
>
>> mental though, part of me wishes they'd forked php at 4 to save all
>> the lame syntax and weirdness.
>>
>
> after thought.. I wish they'd forked it to OO and procedural, then us OO
> guys could h
Nathan Rixham wrote:
Jochem Maas wrote:
Olivier Doucet schreef:
mental though, part of me wishes they'd forked php at 4 to save all the
lame syntax and weirdness.
after thought.. I wish they'd forked it to OO and procedural, then us OO
guys could have phpoo and be happy, and the procedur
Jochem Maas wrote:
Olivier Doucet schreef:
Hi Jochem,
2/ (or/and) Raise a warning or an error if a non static function is
called
as a static one
develop with error_reporting set to E_ALL | E_STRICT, then you'll get a big
fat
warning about it
Yes, that's what I'm using right now. Although
Olivier Doucet schreef:
> Hi Jochem,
>
>
>>> 2/ (or/and) Raise a warning or an error if a non static function is
>> called
>>> as a static one
>> develop with error_reporting set to E_ALL | E_STRICT, then you'll get a big
>> fat
>> warning about it
>
>
> Yes, that's what I'm using right now. Al
Hi Jochem,
> > 2/ (or/and) Raise a warning or an error if a non static function is
> called
> > as a static one
>
> develop with error_reporting set to E_ALL | E_STRICT, then you'll get a big
> fat
> warning about it
Yes, that's what I'm using right now. Although, that's not the highlighted
pro
Olivier Doucet schreef:
> Hello everyone,
> I'm wondering if the following behaviour is a bug or a feature. The case is
> quite complex, so let me explain my point of view.
> here is the source :
>
>
> class MyTest {
> public function myfunc() {
> echo get_class($this);
> }
> }
>
6 matches
Mail list logo
