Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:105511 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 14576 invoked from network); 29 Apr 2019 18:59:38 -0000 Received: from unknown (HELO mail-qt1-f179.google.com) (209.85.160.179) by pb1.pair.com with SMTP; 29 Apr 2019 18:59:38 -0000 Received: by mail-qt1-f179.google.com with SMTP id s10so12480272qtc.11 for ; Mon, 29 Apr 2019 09:01:33 -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=YhSMfbvqNhbf4rwoUfbuQ3ocnm18vUTNOLwXZs3ojQs=; b=hotc1HHmrlqr/YcrbvPkcGl3we2ZZBmXDJ4sq2pygmrJ2nuvTbQclZDkKrdpH/uonT EgR7hDRCK4wqcBF6te1sdbXZjJE9Y13fr5nDDztj+Pk9RcvHkCj7yuiCR/hSdSvxcuHH Pxh7y3dLdcKDMSRP1IEtm9P9fl5xxSTEw4qO9JTcPwA3NVX+byixGDDEjXCGPA+bN+yK waG/ifsO4lhSiBs8ujgYiW7+u/uDXzScE5UnU4oqhtKD6r3vSN6HgtWepBxoiG37EpOg EXEpnDEKXj7/peyWf/mfaj6KjRgBogvSEYD3eNvUFU+C/5xaoA3kRQtr+VX8Y+g+afsW duEw== X-Gm-Message-State: APjAAAUgk1JPBUtETA4QkXdvMjjcukY8hFNanNv2IyQoxfmcpUfmuK41 msG8jwyZDhN1S68b/JWSSXH84+m+hGpFoB8W30qwHA== X-Google-Smtp-Source: APXvYqydyR8aALSQEBSjHDVB3bl7EcVrIcik9iXLkc9KIt1Zugm8B1FxSfqjsdFKCARcr64Glg0JSNOnfHbdBI/+ICc= X-Received: by 2002:a0c:d2d2:: with SMTP id x18mr2164748qvh.18.1556553693462; Mon, 29 Apr 2019 09:01:33 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Mon, 29 Apr 2019 11:01:22 -0500 Message-ID: To: Nikita Popov Cc: Gabriel Caruso , PHP Internals Content-Type: multipart/alternative; boundary="000000000000f914ed0587ad6581" Subject: Re: [PHP-DEV] Don't silence chr function arguments error From: pollita@php.net (Sara Golemon) --000000000000f914ed0587ad6581 Content-Type: text/plain; charset="UTF-8" On Mon, Apr 29, 2019 at 2:37 AM Nikita Popov wrote: > > The idea is to merge in PHP-7.4, but if there's a consensus that this >> > should go into PHP 8 only, so it is :) >> > >> > Technically a BC break, so 8.0 would be the preferred branch IMO. >> > > As this would be a TypeError on 8.0, I think it might make sense to > introduce it in 7.4 where this is still a warning (and should keep the > current "\0" return value in that case -- just make it throw a warning). > > Sounds good to me. --000000000000f914ed0587ad6581--