Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:107192 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 32818 invoked from network); 17 Sep 2019 16:48:33 -0000 Received: from unknown (HELO php-smtp3.php.net) (208.43.231.12) by pb1.pair.com with SMTP; 17 Sep 2019 16:48:33 -0000 Received: from php-smtp3.php.net (localhost [127.0.0.1]) by php-smtp3.php.net (Postfix) with ESMTP id EE3762CFDDF for ; Tue, 17 Sep 2019 07:25:43 -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=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: X-Spam-Virus: No Received: from mail-lj1-x236.google.com (mail-lj1-x236.google.com [IPv6:2a00:1450:4864:20::236]) (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 ; Tue, 17 Sep 2019 07:25:43 -0700 (PDT) Received: by mail-lj1-x236.google.com with SMTP id s19so3730835lji.6 for ; Tue, 17 Sep 2019 07:25:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=fsYlIb5Z1x2d1HQtgfooRTQ04zyClolNIRbUSmhOptc=; b=rdMtxMsX5+dreO+o8S2xhnSdM3nq1uqJ0NJ64fcgMbpjENviOhmTt4NPxv+u+kPEiO yGKX4Mg8OM7SZjFNkEGqCy+PK4n7JEdTSRaEpgJzUS4RcKbirXkMujdT6c3n/Iu8PO23 TiWk1kq3LA0rMBmoCDRZ2JJLHt1O8FIE6vrYqYoStDXUoMedbflhzRtVQUA3Gr91Oe9m +zM9grzntECzoWd0CtQaqabz7PQutgBB8LYKuY3E0T8NMjEmiybe8Q5CgZNYOXYXVsEj vGBtHXUwdv9mGhSlKyv0y431tSQoilz9kMPShl7cEsFewOVHhr9DL1X1ajy7xp5C/UIu P+dg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=fsYlIb5Z1x2d1HQtgfooRTQ04zyClolNIRbUSmhOptc=; b=lq6O1HjrP9Q1CyzKVnu7Dwav3yW3/vBPx8yg2JLan7+FwaZY0LSCamFL9DtF9OMbm9 mxYW9kS/H2/Cu55AhQLunkajh1Vi7S27mk/zE+g/vRTEzYEh2cXtHnsBQN+qxZjQ1jBc iO/REpkP+Ftz7Sjt+8nQpp7amxsSTRpexKeiuf/ddOMF4On9ARfw4A43cJDaHcl07pCO ROB81GkqCX4v8yD6c3Dj8lalYWV0XEZQvoesLW4EbLvEuh8UPgQUwrTdfO+3jKWlN2Xm cUjXe+IX49QfJXTghNhidmzcvGTffhfhu11p+SQyCfy0ME+lUYBXsXpcqTnVQDZlcxBb l6QA== X-Gm-Message-State: APjAAAWnp/bNil3QH1IAPtgbinRHk4YnrGFWRj9NSTd1qdDPk7KLFlPU llusu9DJEu9mXvRlau1ve08ThB4h95cC7xk32SoEcjaF X-Google-Smtp-Source: APXvYqyb3U/BE9jfOCJPhAnOvp90QLVzMZZrYESm3ISaVGQx4v1eKzl3iRG1qXuQ51PN4zbMlXb6xCqlaJGUeUwEKb4= X-Received: by 2002:a2e:309:: with SMTP id 9mr2034745ljd.171.1568730341614; Tue, 17 Sep 2019 07:25:41 -0700 (PDT) MIME-Version: 1.0 Date: Tue, 17 Sep 2019 16:25:25 +0200 Message-ID: To: PHP internals Content-Type: multipart/alternative; boundary="000000000000c2aa850592c07e09" X-Envelope-From: Subject: State of mhash? From: nikita.ppv@gmail.com (Nikita Popov) --000000000000c2aa850592c07e09 Content-Type: text/plain; charset="UTF-8" Hi, I just noticed that the hash extension has a default-disabled --with-mhash option, that enables a couple of additional mhash_* functions. From what I was able to gather, mhash was an old extension that was superseded by hash, and hash provides a compatibility layer for mhash. Should these functions be deprecated? Should this compatibility layer be kept indefinitely? Regards, Nikita --000000000000c2aa850592c07e09--