Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:107209 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 1219 invoked from network); 18 Sep 2019 17:40:37 -0000 Received: from unknown (HELO php-smtp3.php.net) (208.43.231.12) by pb1.pair.com with SMTP; 18 Sep 2019 17:40:37 -0000 Received: from php-smtp3.php.net (localhost [127.0.0.1]) by php-smtp3.php.net (Postfix) with ESMTP id 37D752C6CD1 for ; Wed, 18 Sep 2019 08:18:02 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp3.php.net X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,HTML_MESSAGE, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS15169 209.85.128.0/17 X-Spam-Virus: No Received: from mail-qt1-f176.google.com (mail-qt1-f176.google.com [209.85.160.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by php-smtp3.php.net (Postfix) with ESMTPS for ; Wed, 18 Sep 2019 08:18:01 -0700 (PDT) Received: by mail-qt1-f176.google.com with SMTP id j1so223367qth.1 for ; Wed, 18 Sep 2019 08:18:01 -0700 (PDT) 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=agyYsC5d9falWsXNQkoOvG8ubwIJ1w0S77sw0lQvUVs=; b=bhQIP7Uz09e5KYHCJOQOe+NBwbK11Gi4JR0bgw5OSoSJxtYQTOnBUimobFsuntSg4C 2VZrWhmuFQkUw0A6b2qJ/G+7np/bkyhYPcf+nf7QuJ69tjBif72ShXoC+TaSNbDEnDpr z3Egka+/WRd2bmYRcQPWoSwAFfW6oc2KLCCCnQQeP1S8mTvNLLqU3y4kXMV6YQpjr7+5 bEfWjzviSL0m+Xcqf8w8JDxTYoJnQtk8yykmC9oV0Kp6HqjzSBcZOc4XhPzsvq8DxF4f CAUOoRZ3I+bDlzVFsWOD+u7fG9D+NFY7HM7Ly8pP2OAOrqfSud83ZOfSHiyEJMnGtK12 o5WQ== X-Gm-Message-State: APjAAAUFl5x8gVnwzIxEZyl0tSMUSSuLWg5Ia+CHUHU/utkuKR1BSVH8 JsTTcVPk84MLSALFMhgmhXmnc3hYHQYzr+gbtBkxIQ== X-Google-Smtp-Source: APXvYqwKWVIEkisYDLd83fKCINX/Xf8ifuEtdT1BQ8L7+yagcsG+0ZlDxryJQIoRD3sXt7ACKDCtzb9jnaocZ8QGHg4= X-Received: by 2002:aed:2a3b:: with SMTP id c56mr4819463qtd.343.1568819881062; Wed, 18 Sep 2019 08:18:01 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Wed, 18 Sep 2019 10:17:50 -0500 Message-ID: To: "Christoph M. Becker" Cc: Nikita Popov , PHP internals Content-Type: multipart/alternative; boundary="000000000000ba64800592d557ca" X-Envelope-From: Subject: Re: [PHP-DEV] Re: State of mhash? From: pollita@php.net (Sara Golemon) --000000000000ba64800592d557ca Content-Type: text/plain; charset="UTF-8" On Wed, Sep 18, 2019 at 6:39 AM Christoph M. Becker wrote: > > On 17.09.2019 at 16:25, Nikita Popov wrote: > > Should these functions be deprecated? Should this compatibility layer be > > kept indefinitely? > > The documentation[1] states for more than ten years now: > > | This extension is obsoleted by Hash. > > So I think actually deprecating these functions for PHP 8 is appropriate. > Given that the mhash compatability shim is literally just "map this function and args to that function and args", this one feels like a no-brainer. Anyone who can't upgrade because of /this/ change can literally just drop a single (short) PHP script into their program to polyfill those APIs. It would be a kindness for someone to provide that, and if nobody else does I may just drop a package on composer in the new few months. +1 -Sara --000000000000ba64800592d557ca--