Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:109381 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 32028 invoked from network); 28 Mar 2020 12:58:45 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 28 Mar 2020 12:58:45 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 0F4C31804DD for ; Sat, 28 Mar 2020 04:24:10 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,HTML_MESSAGE, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS15169 209.85.128.0/17 X-Spam-Virus: No X-Envelope-From: Received: from mail-lf1-f50.google.com (mail-lf1-f50.google.com [209.85.167.50]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Sat, 28 Mar 2020 04:24:08 -0700 (PDT) Received: by mail-lf1-f50.google.com with SMTP id c5so10010868lfp.5 for ; Sat, 28 Mar 2020 04:24:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=jH/DRvIAGFU3tsbHrgfop/AZEGs0tgqtG3nmVYHkt2I=; b=ukr3jkeSo9yW8jSomPBizCToZQh+bMX86syulE+xSAkjlPGsA/hnXaz7RkSu3J2xAE 8oml1thE0Msio3f0zZD+6499FnmnJc5kBF3y9UXyq1ldpwJftDNZEXkirdQYGPyl1ZCn yhR7hZG80IQDRhcN/3t6dmowT9ncVg4EEql2C61kUIlRFpbLAhdZR4OscCmdoDGIzXwG jrC5gkfcSG3vONHlVSE0EqJV5a0U2sT7xDW75liTJ5zLt3+eiE+gTF0WHOJm2xUMv5bp qE//zIuWJImeEVL3+Zrd1qP6uhYsAH58j/pKvEWZwe4UqfxLUUSl93s5Xqu36v9NY4VD sSyA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=jH/DRvIAGFU3tsbHrgfop/AZEGs0tgqtG3nmVYHkt2I=; b=NTv5tBDgZC05gYHVqK5YqkSa4lzL7PiCVaeaEXclXf2BPcs6QHtTBbObxpQqNOev7p 0qWQ4JXi7al0OtmhXxuf9aemP9EePYYWtrJa+5iondHXGaxu5gazVVk7+vLr4qXUjxCd 0YHpqeW/6vxXBn6cQN+8MuIfxFslbRGNnkhDs4DQpIavXw5KohG7SYokI4Jv1hQiI69Y v8NqJ0TdAWHSAlM/R+b48ONlv6+G2LGUseVB1OkSl55IClHJWRaXz7cKtwgetih3VNrk eOWHzO8aRsR8AS1f59yDn5U+2HHQtl9dCCpPQ284d81M4xlwNgmOt0cxqIn2TO4Ok1a4 N9TQ== X-Gm-Message-State: AGi0PuZ/j8HtZwR6lM0HWvPyOy34d90mpHwfvQ8MyZ0XabNbaa58rERj LbQ0Rr72qmTdAVoRIadBhjiFFCyYix5BisvwNEQ= X-Google-Smtp-Source: APiQypJs+doyYzB3T/0FzGdECIBf9JjuZhvr61tXnQpMy3umt9TCuTqvtvcBTSUiySl45oxWMEPxqywB3DsdQYTbTgo= X-Received: by 2002:a19:c1c5:: with SMTP id r188mr2427281lff.191.1585394644156; Sat, 28 Mar 2020 04:24:04 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Sat, 28 Mar 2020 12:23:47 +0100 Message-ID: To: =?UTF-8?Q?Terje_Sletteb=C3=B8?= Cc: PHP internals Content-Type: multipart/alternative; boundary="00000000000098046705a1e87434" Subject: Re: [PHP-DEV] Function and operator overloading From: nikita.ppv@gmail.com (Nikita Popov) --00000000000098046705a1e87434 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sat, Mar 28, 2020 at 12:10 PM Terje Sletteb=C3=B8 < terje.slettebo@sandefjordbredband.net> wrote: > Hi. > > Please excuse me if this has been discussed to death earlier. I've tried > to search for it, but I've come up empty: > https://www.php.net/results.php? > q=3Dfunction+overloading&l=3Den&p=3Dall > Yes, this has already been discussed to death. The search on php.net does not extend to the mailing list archives. You may find https://externals.io/ or https://markmail.org/search/?q=3Dlist%3Anet.php.lists.internals more useful for that purpose. https://github.com/Danack/RfcCodex/blob/master/method_overloading.md provides a very high level summary on the topic. There's very little I'm sure about when it comes to the future of PHP, but one of the things I can state with some degree of conviction is that we will never introduce type-based method overloading. Regards, Nikita --00000000000098046705a1e87434--