Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:79336
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: softfail (pb1.pair.com: domain jp7.com.br does not designate 209.85.192.46 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <5478FE5B.8050803@gmail.com>
References: <CAAV2-jiGuU2PK-sL5HUHe+iggNx_aRKyMPiQgVEZ4UKynQvLjw@mail.gmail.com>
 <5478FE5B.8050803@gmail.com>
Date: Mon, 1 Dec 2014 10:26:29 -0200
Message-ID: <CAAV2-jiBzynXW1HJwf2doLoYzPBAXjOD4pmbi3FikTudL9W-8A@mail.gmail.com>
To: Stanislav Malyshev <smalyshev@gmail.com>
Cc: internals@lists.php.net
Content-Type: multipart/alternative; boundary=001a11348d8888b7b7050926b977
Subject: Re: [PHP-DEV] Static functions Vs Nonstatic functions
From: carlos@jp7.com.br (Carlos Rodrigues)

--001a11348d8888b7b7050926b977
Content-Type: text/plain; charset=UTF-8

Hi Stanislav.

Thank you for replying. I agree that PHP can be different from other
languages, but i think you agree that a code like this just feels wrong:

class Cube {
 function weird() {
   echo Duck::foo();
 }

}

class Duck {
 public function foo() {
     echo 'My class is: ' . get_class($this);
 }
}

$rubik = new Cube;
$rubik->weird(); // Output:  My class is: Cube


One would never guess that $this inside a method of Duck could be an
instance of Cube. It might look silly as an example. But in the real world
someone could think a method is static when its not, and call it,
introducing a bug on the application.

I don't see any case where this behavior is useful. And even it there was
one, it could be achieved using magic methods __call() and __callStatic().


Thank you all,

*Carlos Rodrigues*
carlos@jp7.com.br

2014-11-28 20:59 GMT-02:00 Stanislav Malyshev <smalyshev@gmail.com>:

> Hi!
>
> > It confuses programmers that came from other languages, prevent APIs from
> > having meaningful names on static methods and have no other benefit than
> > supporting PHP 4 code.
>
> I think this notion of "confuses programmers" sometimes goes too far,
> and this is one of the examples. PHP prides itself about having low
> barrier to entry, but that doesn't mean you can refuse to learn anything
> at all about it and PHP should change to match that.
>
> There's nothing wrong in having static and non-static functions in the
> same namespace, and many languages do the same. Some do not, so you
> should just remember PHP is the one which does.
> --
> Stas Malyshev
> smalyshev@gmail.com
>

--001a11348d8888b7b7050926b977--