Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:110834
MIME-Version: 1.0
References: <CANeKSiRe95yUeyUV5S3MU1Bzh7A_Z0OQF_WVNFK16CcbE5wYqw@mail.gmail.com>
In-Reply-To: <CANeKSiRe95yUeyUV5S3MU1Bzh7A_Z0OQF_WVNFK16CcbE5wYqw@mail.gmail.com>
Date: Fri, 3 Jul 2020 13:47:21 +0100
Message-ID: <CAJvSBVO+4dkvMv501zUpGLJCy3VG_=L15+L9UXKy9z+JvVuxGQ@mail.gmail.com>
To: Benas IML <benas.molis.iml@gmail.com>
Cc: PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000002f15f605a988efb8"
Subject: Re: [PHP-DEV] [RFC] [VOTE] Make constructors and destructors return void
From: phpmailinglists@gmail.com (Peter Bowyer)

--0000000000002f15f605a988efb8
Content-Type: text/plain; charset="UTF-8"

Hi,

I have voted in favour, but enough people I respect have voted against to
make me reconsider.

My understanding is the changes will only cause problems to people who have
returned something from __construct() or __destruct(). As people shouldn't
have done this, IMO it is a smaller BC issue than the BC break that would
have been caused if the proposed #[] attribute syntax had been chosen.

Peter

On Thu, 2 Jul 2020 at 22:12, Benas IML <benas.molis.iml@gmail.com> wrote:

> Hey internals,
>
> I have opened the voting for the RFC, let's hope everything is going
> to be smooth :). If you have any other questions, let me know!
>
> RFC: https://wiki.php.net/rfc/make_ctor_ret_void
>
> Best regards,
> Benas Seliuginas
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: https://www.php.net/unsub.php
>

--0000000000002f15f605a988efb8--