Hi all, On Sun, Jan 11, 2015 at 9:34 AM, Stanislav Malyshev <smalys...@gmail.com> wrote:
> I'd like to initiate a vote on this RFC: > https://wiki.php.net/rfc/default_ctor > > TLDR: this RFC would make a call to parent::__construct() succeed (as in > "not produce a fatal error") even if the parent class does not define a > ctor. Same for __destruct and __clone. The motivation for it is in the > RFC and here: > https://php100.wordpress.com/2014/11/04/default-constructors/ > > I've chosen the simplest way of implementing it, as suggested by Dmitry, > in https://github.com/php/php-src/pull/990. There are other > alternatives, but I think the simpler the better. > > Previous discussion is at: http://marc.info/?t=141630266000001&r=2&w=2 > It seems -1 vote are increasing. Therefore, I would like to mention benefits of this RFC again. This RFC is great for rapid app development/prototyping. There are many cases that base class constructors calls are needed or not. This RFC allow us to just call parent constructor, then add implementation later if it is needed. It makes code maintenance easier for production code also. I can understand the reason why people vote -1 (non existent method/function calls should not be able to be called and raise), but benefits override. IMHO. PHP is for easier/faster development, isn't it? Regards, -- Yasuo Ohgaki yohg...@ohgaki.net
