Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:82785
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain bof.de designates 80.242.145.70 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <54E1260F.2070101@gmail.com>
References: <CAJ26g5Swk1z2W-kR6FG77M1bPJPQjVUihd13-27ngwHK7A8+cA@mail.gmail.com>
	<54E1260F.2070101@gmail.com>
Date: Mon, 16 Feb 2015 08:36:40 +0100
Message-ID: <CAJ26g5RoRNVLiYKA5g-CUrKey0CPjKvJB7tDA1JCj5K15r3uVw@mail.gmail.com>
To: Rowan Collins <rowan.collins@gmail.com>
Cc: internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11337bfca8f699050f2fa560
Subject: Re: [PHP-DEV] A modest proposal: __contructStatic
From: bof@bof.de (Patrick Schaaf)

--001a11337bfca8f699050f2fa560
Content-Type: text/plain; charset=UTF-8

Am 16.02.2015 00:05 schrieb "Rowan Collins" <rowan.collins@gmail.com>:
>
> A quick thought - if you want to stick with the "magic static call"
pattern, you can implement this much more simply by doing something similar
to Laravel's "facades" [1]:
>...
> This basically implements in userspace what you propose to add to the
language, with the only caveat being that you must separate the concerns of
adding extra functionality, and wrapping it in a static facade, into two
separate classes.

That was one of my intermediate steps before reaching the current approach,
but it irked me that when switching code from MyRedis static/singleton
usage to real instance usage I suddenly have to write a different class. In
my scheme, where I can use red_global::get() I can as well use $redis = new
red_global(); $redis->get(); without thinking about how that companion
class was named.

Sure, no big issue. But a small one... By itself, surely not enough reason
for a language change :)
It's all a question of how many other small such uses there would be.

best regards
  Patrick

--001a11337bfca8f699050f2fa560--