Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:117086 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 68803 invoked from network); 21 Feb 2022 07:47:02 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 21 Feb 2022 07:47:02 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 2A8CC180543 for ; Mon, 21 Feb 2022 01:06:13 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-0.3 required=5.0 tests=BAYES_40,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,NICE_REPLY_A, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,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-pl1-f169.google.com (mail-pl1-f169.google.com [209.85.214.169]) (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 ; Mon, 21 Feb 2022 01:06:12 -0800 (PST) Received: by mail-pl1-f169.google.com with SMTP id m11so8808687pls.5 for ; Mon, 21 Feb 2022 01:06:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=message-id:date:mime-version:user-agent:subject:content-language:to :references:from:in-reply-to:content-transfer-encoding; bh=gK7Y8+UNKq25VPDLye78n90O8IXIugZ6fXWHAs/z6HU=; b=nF9rPFGOfmV9uiPJcNiyNUBq8R942bvjCFlNQTrw5jGEKy6/o7t/4jtRluq1GBReO1 LGuI1rTm7h29KYelAFOiCUBEO4Xp2E54QtbANuPpodj4QyDKRqDLR2q8v+gXQOSk9Thu 2edLmIYVbbXeGXbciarsURLzlB6jH+w3ewZE3+kn9k6q72OgGHdA5mUuN3pnEMR0Z6L7 GwsFGX+7WGndSKV7qFFppGEhHG8B3ej2RryWZfS7PLSyMcU6E7TWU5wGutt+WcXcfa90 6lvvLRQXiATAIIWLT5yUGKpozNSgkZXIp7TbnCyIq0LcD9z1u3u29BG3rQz5Me5DYwss dXbg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:references:from:in-reply-to :content-transfer-encoding; bh=gK7Y8+UNKq25VPDLye78n90O8IXIugZ6fXWHAs/z6HU=; b=EklSkbjzikQUat/My/doyA2swRPrwv+CZEox40B8ZRTeMMl3nY++1vk0fMc6NAhgs7 nzZvVsEx2IIM/DFAhmHnVQhzwWKi/QhWF1Ttpm5m3tiUhwvTfkV8s9AsFK0Myw3hWkJk w7lSm+gM/bpO/cxYFTgZ5ONFbcHPAevMNkWNguBcrshkL8kGR5FUB0TCjkikZpzDQSlW KgpHDZZBTKd4D6UAmRvCFmWmI38tUr9gRe2HCFkLh0FGyHx8wit425Ehp9Iy589IvXVh PxPQzu7tcRcMw+cKUFn1Psbsn1RzpAQUUvaxGmfIvSYxWNvQg8pD90SyqQfsQXbhX9O/ 4ivw== X-Gm-Message-State: AOAM532olhuCrGZmR/TwhwqrCATUaTKx55W6jB9WkAZOKp6znFZewPh1 B/Fb5OCWvHbw/wMDLSPdHSVPsoMaUnJ6 X-Google-Smtp-Source: ABdhPJwfRO3th0VsNZxWHAzzV793BQa1ArFeAB6p2zUwavPTXfHspFStvFVADmYbgYdQpzv+7tnc8A== X-Received: by 2002:a17:903:32d0:b0:14a:db1b:6a57 with SMTP id i16-20020a17090332d000b0014adb1b6a57mr17585954plr.67.1645434371407; Mon, 21 Feb 2022 01:06:11 -0800 (PST) Received: from [192.168.0.15] ([65.129.192.17]) by smtp.gmail.com with ESMTPSA id t17-20020a17090b019100b001b9fbc9a0d6sm6985031pjs.41.2022.02.21.01.06.10 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 21 Feb 2022 01:06:10 -0800 (PST) Message-ID: <40015164-ac0c-336d-c7d6-c4766d6caff8@gmail.com> Date: Mon, 21 Feb 2022 02:06:15 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Firefox/91.0 Thunderbird/91.6.0 Content-Language: en-US To: PHP Internals List References: <5983302.2649742.1645319015766@email.ionos.com> <6238bf00-011e-35cc-d84b-4082b4f05099@gmail.com> <497325306.1564942.1645357444018@email.ionos.com> <3c6871ca-589d-6812-800c-a3b9ad6bb575@bastelstu.be> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] RFC proposal to deprecate crypt() From: smalyshev@gmail.com (Stanislav Malyshev) Hi! > The RFC is about deprecation, not removal. If it's not going to be removed, what's the point of annoying people with deprecation warnings (that they would patch out/silence anyway)? If we want to document which functions are recommended to be used in which case, we have the manual for that. I don't think deprecation should be used for such things. -- Stas Malyshev smalyshev@gmail.com