Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:78939
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 82.113.146.227 as permitted sender)
Date: Tue, 18 Nov 2014 12:23:08 +0000 (GMT)
To: Stanislav Malyshev <smalyshev@gmail.com>
cc: PHP Internals <internals@lists.php.net>
In-Reply-To: <546B0F62.1090705@gmail.com>
Message-ID: <alpine.DEB.2.11.1411181221100.13538@whisky.home.derickrethans.nl>
References: <546B0F62.1090705@gmail.com>
User-Agent: Alpine 2.11 (DEB 23 2013-08-11)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: Re: [PHP-DEV] [RFC] Default constructors
From: derick@php.net (Derick Rethans)

On Tue, 18 Nov 2014, Stanislav Malyshev wrote:

> Hi!
> 
> I'd like to propose the following RFC, which in short would allow any
> method to call parent ctor (and some other methods) even if such is not
> explicitly defined:
> 
> https://wiki.php.net/rfc/default_ctor
> 
> The reasons are outlined in detail in the RFC and here:
> http://php100.wordpress.com/2014/11/04/default-constructors/
> 
> The patch is not finished yet but seems to be working fine, I'll add it
> to the RFC this week as soon as I finish it. I'd like to put idea out
> there in the meantime and hear what everybody thinks about it.

You write:

>  Also, this can lead to more subtle BC breaks. Consider this code: 

And then further on:

> No backward incompatible changes, sin...

that can not be both right.

cheers,
Derick