Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:117091 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 81625 invoked from network); 21 Feb 2022 09:53:09 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 21 Feb 2022 09:53:09 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 0CF29180547 for ; Mon, 21 Feb 2022 03:12:21 -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=-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-oi1-f171.google.com (mail-oi1-f171.google.com [209.85.167.171]) (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 03:12:20 -0800 (PST) Received: by mail-oi1-f171.google.com with SMTP id s5so10383839oic.10 for ; Mon, 21 Feb 2022 03:12:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=bAFmeGabQSLVo+pvx03c9FmEk9N+0AQbguDYcQqVSJ8=; b=L1WfzARZO7yjIQMsev4iDYf+rQ/kFmM1qWUS1HVkT7qBvRhFa6F3Hap2cq63oQrws6 tiuMq5YMqYyKjmhRAfOvmFldk01VKmgH48HBYJqgDrBX5AXjtCUQXCmpVQpYFAqjn3og fXpX3TtVaxXQEvXgukiv0lkCo88lBUdNiekUHfblJEfX60nV886TpIfBsVENT+eQ+b2k AHYNNid+zNexXyufo0CgGC4Po4kbuZ79xAqFsvpw9KuGZI4+kIMiPCck3FLiioKEPLnR 6LoA4sVZMw74YbJq/x2vxjWMPh5QygDioWlewBsvz5Xf6FYaWxQwL/P6rIEfAjLGnKDK TrIA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=bAFmeGabQSLVo+pvx03c9FmEk9N+0AQbguDYcQqVSJ8=; b=yOQ2Z/1Ys4SJsDyZ4SOM72EAISg5Nlcafpd8wrXXqW276SV9Y881eH0962njM39UhN Uoq8yEwveFRzmXzo5k2eXGcBT4gZG767WrEA9d8r70MDbe50pvuw58E9V86MT5mQcNZA WC/SBNplWzjCd+G442copCHxQ5cHAKOChfOVhamE8APXcN4SHhgpbfaMFki8ot9Fy6JD 9u0y89XumtcGLeZWLmTESEmib9KAAuoMa4iT2V6/tD1P+rYtdLCe66Kaow4rninI3agP MOPciFopfpHDiY+qZLmJ7iRWC8HGYNsS52tIwhj5pxI7djxBV9U2tDDNkkKK3kgMhyb6 8bkw== X-Gm-Message-State: AOAM531rErJaJbTM2a3Hlr6BHjNtrCH6wQHbIdxlfqJLSO0HGUIc7TTk D8poeqSJxaGc+mSfhieNNSw3voNv7yfdzQoSLC2nexanj+I0JA== X-Google-Smtp-Source: ABdhPJyWqRXxKSlQEICxtK2FpxYXtTWcV1LXFyYaBFWzCpNWKBhgYELICbfl/2xB7/QQISJy8tQFZaboHyeYfC7ywm8= X-Received: by 2002:a05:6808:f13:b0:2d4:f8c4:8b99 with SMTP id m19-20020a0568080f1300b002d4f8c48b99mr2376824oiw.278.1645441939685; Mon, 21 Feb 2022 03:12:19 -0800 (PST) MIME-Version: 1.0 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> <40015164-ac0c-336d-c7d6-c4766d6caff8@gmail.com> In-Reply-To: Date: Mon, 21 Feb 2022 12:12:08 +0100 Message-ID: To: =?UTF-8?Q?Tim_D=C3=BCsterhus?= Cc: Stanislav Malyshev , PHP Internals List Content-Type: multipart/alternative; boundary="00000000000050439705d8854e92" Subject: Re: [PHP-DEV] RFC proposal to deprecate crypt() From: ocramius@gmail.com (Marco Pivetta) --00000000000050439705d8854e92 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, Feb 21, 2022 at 11:10 AM Tim D=C3=BCsterhus wrot= e: > Hi Marco > > On 2/21/22 10:15, Marco Pivetta wrote: > >> 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)? > >> > > > > Probably to be removed in `9.0` or `10.0`? Yes, it should be removed at > > some point. > > In contrast to other deprecations (e.g. the utf8_encode/decode currently > discussed), deprecating and ultimately removing crypt() results in an > actual loss of functionality. > ...yes? That's the point? Marco Pivetta http://twitter.com/Ocramius http://ocramius.github.io/ --00000000000050439705d8854e92--