Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:130136
Precedence: list
MIME-Version: 1.0
References: <CAFgk54k4NkUrUkMD=HE1TkowDJb55X9B7hcCa7vxGUbAfQhv8w@mail.gmail.com>
 <1f25d77e-224b-40d6-bf19-18dfdfc9de54@rwec.co.uk> <CAFgk54knVsdNQbVxVL43qyA3vkQrMHZt=ATfuiDCD4qJa6MPVg@mail.gmail.com>
 <453bc043-b4ee-423e-9561-55510f5c20a7@rwec.co.uk> <CAFgk54nimvF4UC6KOxaGg-v5hFazt1sNTyyJ-bkqHy6Xm5nOHA@mail.gmail.com>
 <e4d2994a-ae1e-4f33-89c3-67c5df99f1d3@rwec.co.uk> <CAFgk54kmk8uYjF8RcsOGKAyvBZNn2tYEd9D1PVK2prfeU=pF5A@mail.gmail.com>
 <6412E222-9B0F-4139-A6F9-7D0C686197BF@rwec.co.uk> <CAFgk54=S1KjPwgHy_Qy7xtGbVvfHkd4SEMZ+o1WhzaVHZQ7ncw@mail.gmail.com>
 <CAEZPtU7pY1stp6WXpoUHnx-X_tBtvjK7x1Vi9vJDg6fC0soV1g@mail.gmail.com>
In-Reply-To: <CAEZPtU7pY1stp6WXpoUHnx-X_tBtvjK7x1Vi9vJDg6fC0soV1g@mail.gmail.com>
Date: Mon, 23 Feb 2026 17:00:06 +0100
Message-ID: <CAFgk54kvv4UJXak=3goF3pWRy=KK1umAOoDczBsTvY1UM2DEDQ@mail.gmail.com>
Subject: Re: [PHP-DEV] [IDEA for RFC] let the "new" operator fail when the
 __construct() function returns a value.
To: Pierre Joye <pierre.php@gmail.com>
Cc: "Rowan Tommins [IMSoP]" <imsop.php@rwec.co.uk>, PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
From: mirco.babin@gmail.com (Mirco Babin)

Hello Pierre,

Op vr 20 feb 2026 om 19:29 schreef Pierre Joye <pierre.php@gmail.com>:
>
> Hello Mirco,
>

> In a context of __construct, disallow any return value can be detected
> as well. Any return statement with anything used with it can be
> rejected (and should).
>
> It is documented as void, we could "fix" it with a bug fix.

- https://www.php.net/manual/en/language.oop5.decon.php#object.construct
  lists the __construct() function as void.
- But the implementation of __construct() is mixed.

>
> Also, about this whole discussion , that __ construct, can still be
>  called as a normal method.  Some relics of php 4-5 migration path and
> then work around serialization or hydration challenges.
>
> Most  maintained projects out there moved away from these hacks and
> rely on new  reliable solution for these challenges,  like doctrine
> or symfony serializer.

I have found https://php-legacy-docs.zend.com/manual/php4/en/migration5.
But I didn't find any specific __construct() instructions, other than
https://php-legacy-docs.zend.com/manual/php4/en/language.oop5.decon. At
that page, it is not mentioned the __construct() must not return a value.

Could you explain on serialization or hydration challenges in more
details? Perhaps with a theoretical example?
An (old) real-world example would be even better, if you can find one.

Kind regards,
Mirco Babin