Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:96610 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 55911 invoked from network); 25 Oct 2016 18:42:04 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 25 Oct 2016 18:42:04 -0000 Authentication-Results: pb1.pair.com header.from=php@duncanc.co.uk; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=php@duncanc.co.uk; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain duncanc.co.uk from 209.85.215.53 cause and error) X-PHP-List-Original-Sender: php@duncanc.co.uk X-Host-Fingerprint: 209.85.215.53 mail-lf0-f53.google.com Received: from [209.85.215.53] ([209.85.215.53:37932] helo=mail-lf0-f53.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 91/D4-24108-B77AF085 for ; Tue, 25 Oct 2016 14:42:04 -0400 Received: by mail-lf0-f53.google.com with SMTP id d20so19617732lfj.5 for ; Tue, 25 Oct 2016 11:42:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=duncanc-co-uk.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=jqnhnDHfBU5nKwGvJ6RkHsD5avwa7YNxeO/O7XECso8=; b=JzP9NArjOZhfTXegBU0gkRx5XR/uSmasD12pv4i/UzO05ubHwD1N6t1vS/CZyoZqA5 saYbrDoZ/JxTh2c4zOGgZ0d0Zp+SE5EAt0dNL2LXTT052cd4A3WKi5k8r6KuTDwp48mM b//84ANHtY9ngzlXtwQ3c0oSfpKEAAfIZNvfIWjLfarkicFHwzE0Hgiv3di78HSn8Zr1 yeqbjFsexMvijUrqoot8tp89e0XhTc6PkdT3W4QC0d3yxBllvHIWZr2qWXfE42g5X/cD aDQzYP3Ma0CEeG0dS4ZFsN0u0vBVCFURjIHM5+O2zHvvnNoexBxZdNU0S5S2vWHzVrTb pncw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=jqnhnDHfBU5nKwGvJ6RkHsD5avwa7YNxeO/O7XECso8=; b=BS0hfh3HLclVNbKjsGZlLIQa8wGUiV/vpB3DJKdDNBiWWwdUAh6ArjTEwIBHNV9vjU P1nO0Zq3VJ2xsVdZEdL5rg7WuraUz/ZIjTpv86AQ02EIj6EeHkgf89ChnNiFTSO1rREg aa1UR4e37lP/9lk4/Y/pMvlF1TPwLAWmS7dO1PGfXUc2NyxaQGDkUAN/wIp/MbhT5tGT +uQOgz9jRt2D2qUkuMN5Hw5dxpavHsnGjOQmWQvYRWUPViyg7/UPibLSzjKzHT+WtotA J4NEYBqNkhoUrU4cX2SgSoF8I7XosiOD2LtqBI1l54jJexXYH7OzTRWGo2ULrGadtW3n QDIg== X-Gm-Message-State: ABUngveC4QeSQ/QBTipGIp+H6gijGWaFbKpqUXPpm4TCJMOhFdvg2zlNeZaEhshk1Z8zhw== X-Received: by 10.25.24.217 with SMTP id 86mr1597506lfy.3.1477420920017; Tue, 25 Oct 2016 11:42:00 -0700 (PDT) Received: from mail-lf0-f42.google.com (mail-lf0-f42.google.com. [209.85.215.42]) by smtp.gmail.com with ESMTPSA id l20sm2494668lfl.30.2016.10.25.11.41.58 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 25 Oct 2016 11:41:58 -0700 (PDT) Received: by mail-lf0-f42.google.com with SMTP id o16so15604881lff.7 for ; Tue, 25 Oct 2016 11:41:58 -0700 (PDT) X-Received: by 10.25.211.142 with SMTP id k136mr10123069lfg.45.1477420917688; Tue, 25 Oct 2016 11:41:57 -0700 (PDT) MIME-Version: 1.0 Received: by 10.114.120.163 with HTTP; Tue, 25 Oct 2016 11:41:56 -0700 (PDT) X-Originating-IP: [31.49.123.214] In-Reply-To: References: Date: Tue, 25 Oct 2016 19:41:56 +0100 X-Gmail-Original-Message-ID: Message-ID: To: Dan Ackroyd Cc: Internals Content-Type: multipart/alternative; boundary=001a114074bcfbaa15053fb4dc84 Subject: Re: [PHP-DEV] [RFC] [VOTE] Counting of non-countable objects From: php@duncanc.co.uk (Craig Duncan) --001a114074bcfbaa15053fb4dc84 Content-Type: text/plain; charset=UTF-8 Hi Dan, On 23 October 2016 at 13:49, Dan Ackroyd wrote: > > When you update the manual, please can you explicitly what is allowed, > rather than just saying what is not allowed as per the RFC text. > > The manual already says what is allowed: *"Parameters: array_or_countable An array or Countable object."* Under the "Return Values" section there is sentence about the current implementation: *"If the parameter is not an array or not an object with implemented Countable interface, 1 will be returned. There is one exception, if array_or_countable is NULL, 0 will be returned."* I suggest we extend the "Return Values" section to say that a warning is raised, but I don't see any need to change the manual beyond that. Unless I have misunderstood you? --001a114074bcfbaa15053fb4dc84--