Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:114384 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 50619 invoked from network); 11 May 2021 14:18:21 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 11 May 2021 14:18:21 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 7CA4F1804F4 for ; Tue, 11 May 2021 07:26:09 -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.8 required=5.0 tests=BAYES_05, HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_SOFTFAIL autolearn=no autolearn_force=no version=3.4.2 X-Spam-Virus: No X-Envelope-From: Received: from mail-lj1-f177.google.com (mail-lj1-f177.google.com [209.85.208.177]) (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 ; Tue, 11 May 2021 07:26:09 -0700 (PDT) Received: by mail-lj1-f177.google.com with SMTP id o16so25373776ljp.3 for ; Tue, 11 May 2021 07:26:09 -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=vqbAC35+Q6GH1fhWEuwJ0pPxXAxFMtywWE7eEciRtD0=; b=TGu71lAT4Wvv7RykqyE+4TNm3juVE5kPEAJKifrxGVndAJ8kFzHJNgFtppHMLfIZXM gP4JJzpT5a5ZMKkw+0jB1FpezbkmfmHv9pDre9kWyCl1mIThK6IStmfkHHpP2xpmnU2h 4o+NVUr58UZLEhg+HiUnD55HaiBpSqJ0HYKYb1IfAvIH1NqkfjfF6yuihSya6QwS5bRD MOFINDQmjO7lrd5iYwPPQUg6sjFZG1tblM4DEoloBT3fNjNsJV4huzstwMuBNtF3TA3r owPrMDUvN/vZl1PW0dJGc3tpONNjZHBbuRdZ6X1tslpywUnBX+bvO59e9uh89Fladu5T FkhQ== X-Gm-Message-State: AOAM5335eU/OKJAaz5ZRnUnJOnms/5A0PKb5abkwOAyW+BBrwuvXozRA Km4TRcYTVIGu38svK42FMkmOP83hJrPLvje+mnpEplz7YKM6OQ== X-Google-Smtp-Source: ABdhPJyFylNN5h/erIx/ezOn3JPXuBkc9f5HUffn1hk96dcujHCPZk5+lJSW7rBGvFuM7SYUQbxZbbzr0iVae+t0SCM= X-Received: by 2002:a2e:7f16:: with SMTP id a22mr12224579ljd.360.1620743166193; Tue, 11 May 2021 07:26:06 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Tue, 11 May 2021 09:25:55 -0500 Message-ID: To: Nikita Popov Cc: PHP internals Content-Type: multipart/alternative; boundary="000000000000b1835805c20eacc0" Subject: Re: [PHP-DEV] [RFC] Deprecate ticks From: pollita@php.net (Sara Golemon) --000000000000b1835805c20eacc0 Content-Type: text/plain; charset="UTF-8" On Tue, May 11, 2021 at 3:53 AM Nikita Popov wrote: > I'd like to propose the depreciation of the ticks mechanism: > https://wiki.php.net/rfc/deprecate_ticks > > I'm submitting this separately from the PHP 8.1 deprecations RFC, as this > is a language change, even if not a particularly important one... > > I came here to plea for the poor, disrespected ticks function. Then I went to github and asked who was using it... In the 10,000 results which came up for that string in actual PHP code, I paged through the first 20% (2000) cases. They were ALL either a phpt test file, or an auto-generated proxy function (which appears to not actually have any uses). So yeah. Pour one out for ol' ticks. May it rest in peace (following a suitable deprecation period leading up to PHP 9.0). -Sara --000000000000b1835805c20eacc0--