Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:119971
MIME-Version: 1.0
References: <CAFPFaMLghRYP4ioCkfa7WKhTAz+1gWgcZ5mWYAunkb9f3g=fdA@mail.gmail.com>
 <1681231975223.2858287856.1521675056@yahoo.de>
In-Reply-To: <1681231975223.2858287856.1521675056@yahoo.de>
Date: Wed, 12 Apr 2023 16:51:58 +0100
Message-ID: <CA+kxMuSdwNOTML=jd6WQR084Cn71hCkngtVzHMOdXpToDkROnA@mail.gmail.com>
To: Hans Krentel <hanskrentel@yahoo.de>
Cc: george.banyard@gmail.com, PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] [RFC] New core autoloading mechanism with support for
 function autoloading
From: Danack@basereality.com (Dan Ackroyd)

On Tue, 11 Apr 2023 at 18:12, Hans Krentel via internals
<internals@lists.php.net> wrote:
>
> So I'd love to see some commentary on a `function_alias()`
> if now function autoloading is considered to come in

I wouldn't be opposed to it, but it should be a separate RFC.

The implementation could be copied from
https://www.php.net/manual/en/function.runkit7-function-copy and
probably wouldn't be that complicated, or conflict with this RFC.

> It was the latter which brought us `class_alias()` [0]
> and I've used it often in code migrations

Yes, in particular the changing from Twig_Template_Loader to
Twig\Template\Loader migration.

I'll add it to my list at https://phpopendocs.com/rfc_codex It would
seem a good "my first RFC" for someone.

Though, function migration could also be solved in a far more powerful
way. Check my forthcoming reply to Rowan...

cheers
Dan
Ack