Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:91472
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.44 as permitted sender)
To: Dan Ackroyd <danack@basereality.com>,
 "internals@lists.php.net" <internals@lists.php.net>
References: <CA+kxMuTHbsYAXe+J+jrFz+ZeguacEyUxCUpFJE8jMee_5+u_5g@mail.gmail.com>
Message-ID: <56D685FA.8040900@gmail.com>
Date: Tue, 1 Mar 2016 22:19:38 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0)
 Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <CA+kxMuTHbsYAXe+J+jrFz+ZeguacEyUxCUpFJE8jMee_5+u_5g@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] Callable constructors
From: smalyshev@gmail.com (Stanislav Malyshev)

Hi!

> If constructors had always been callable in PHP, this would be a
> standard thing to do and not controversial imo. It's only due to
> reasons lost in the mists of time, that object instantiation can only
> be invoked via 'new' that it's not possible currently, and so needs an
> RFC to change.

Constructors have always been callable in PHP and still are. They are
functions like any other. What you need is a factory method, not a
constructor - constructor is called to initialize object, not create it.
But you can create factory methods at will, you just don't have to call
it __construct.

-- 
Stas Malyshev
smalyshev@gmail.com