Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:96208 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 17213 invoked from network); 4 Oct 2016 07:19:49 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Oct 2016 07:19:49 -0000 Authentication-Results: pb1.pair.com smtp.mail=me@kelunik.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=me@kelunik.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain kelunik.com from 81.169.146.219 cause and error) X-PHP-List-Original-Sender: me@kelunik.com X-Host-Fingerprint: 81.169.146.219 mo4-p00-ob.smtp.rzone.de Received: from [81.169.146.219] ([81.169.146.219:15134] helo=mo4-p00-ob.smtp.rzone.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 41/5C-06241-31853F75 for ; Tue, 04 Oct 2016 03:19:47 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1475565584; l=3136; s=domk; d=kelunik.com; h=Content-Type:Cc:To:Subject:Date:From:In-Reply-To:References: MIME-Version; bh=rAB2uLyzi/yCxyL5rQZFThzOUWewQmKe/7n/obncQE8=; b=I/fbq5WidsgHbURAqFF7sO1Mdv6lqT8zFXcxRfNO7dDGSdRQkgH9IrWlBBjhWd/ewfn 3nB7TIFsC93SBroi9LgtUaY4Aj0N8glc8CBWBpFAptRiY3K8XpG/qKwqG4V2Ytf5Y4ggd GI6TghAXdKyKbd002aI/69GeCPOvn6JKpH0= X-RZG-AUTH: :IWkkfkWkbvHsXQGmRYmUo9mls2vWuiu+7SLGvomb4bl9EfHtO3A6 X-RZG-CLASS-ID: mo00 Received: from mail-wm0-f43.google.com ([74.125.82.43]) by smtp.strato.de (RZmta 39.5 AUTH) with ESMTPSA id f07fe2s947JiWcU (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (curve secp384r1 with 384 ECDH bits, eq. 7680 bits RSA)) (Client did not present a certificate) for ; Tue, 4 Oct 2016 09:19:44 +0200 (CEST) Received: by mail-wm0-f43.google.com with SMTP id b201so125766593wmb.0 for ; Tue, 04 Oct 2016 00:19:44 -0700 (PDT) X-Gm-Message-State: AA6/9RlGjS0me6S2TWE/yfetcZU6YiEDAFLMKBand9TfGYRqmvcnW3/Q7mBRWKpIaJfzbnDPptbdRCaC7yX/vQ== X-Received: by 10.28.142.14 with SMTP id q14mr12470563wmd.87.1475565584121; Tue, 04 Oct 2016 00:19:44 -0700 (PDT) MIME-Version: 1.0 References: <12ecd7d8-2c72-d835-a1af-20698ee9885c@gmail.com> In-Reply-To: Date: Tue, 04 Oct 2016 07:19:33 +0000 X-Gmail-Original-Message-ID: Message-ID: To: Yasuo Ohgaki , Stanislav Malyshev Cc: PHP Internals Content-Type: multipart/alternative; boundary=001a114436c87c0b19053e04e2e4 Subject: Re: [PHP-DEV] wordwrap with negative width From: me@kelunik.com (Niklas Keller) --001a114436c87c0b19053e04e2e4 Content-Type: text/plain; charset=UTF-8 Yasuo Ohgaki schrieb am Di., 4. Okt. 2016, 04:43: > On Tue, Oct 4, 2016 at 11:20 AM, Stanislav Malyshev > wrote: > > I've just discovered that wordwrap() (http://php.net/wordwrap) accepts > > negative width parameter and treats it as if it was 0. It looks like a > > bug, never documented and works in code only by accident as far as I can > > see. So, my question is - would it be OK to drop support for negative > > width in wordwrap? > What does drop mean? Return false and issue a warning? Keep current behavior and issue a warning? Regards, Niklas It should be a user script bug. > +1 > > -- > Yasuo Ohgaki > yohgaki@ohgaki.net > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > --001a114436c87c0b19053e04e2e4--