Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:101422 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 24396 invoked from network); 26 Dec 2017 16:08:41 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 26 Dec 2017 16:08:41 -0000 Authentication-Results: pb1.pair.com header.from=lists@rhsoft.net; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=lists@rhsoft.net; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain rhsoft.net designates 91.118.73.15 as permitted sender) X-PHP-List-Original-Sender: lists@rhsoft.net X-Host-Fingerprint: 91.118.73.15 mail.thelounge.net Received: from [91.118.73.15] ([91.118.73.15:37695] helo=mail.thelounge.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 1F/74-58518-804724A5 for ; Tue, 26 Dec 2017 11:08:41 -0500 Received: from srv-rhsoft.rhsoft.net (Authenticated sender: h.reindl@thelounge.net) by mail.thelounge.net (THELOUNGE MTA) with ESMTPSA id 3z5grj0NCrzXMP for ; Tue, 26 Dec 2017 17:08:37 +0100 (CET) To: internals@lists.php.net References: <72392123-d37b-26df-6886-218f48205f8a@fleshgrinder.com> <5171148a-3554-35a3-ab72-370e1aac4a3f@php.net> <6894aa94-0400-7a9a-f00c-47f1f556a4d0@php.net> Message-ID: Date: Tue, 26 Dec 2017 17:08:36 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <6894aa94-0400-7a9a-f00c-47f1f556a4d0@php.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: de-CH Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] [DISCUSSION] Scalar Pseudo-type From: lists@rhsoft.net ("lists@rhsoft.net") Am 26.12.2017 um 16:56 schrieb Sebastian Bergmann: > Am 26.12.2017 um 16:46 schrieb lists@rhsoft.net: >> would you mind to explain this? > > "Foo|Bar", "array|string", etc. (still) make no sense to me. > > "scalar" makes sense to me although it is but an alias for > "bool|float|int|string". honestly *that* makes no sense for me with "float|int" you would have no need for dozens of aliases, in that case "numeric" when i expect some number but not a string and not a boolean return by a strpos() or similar functions also i have function which allows "int|array" where the internal logic loops the array internally but i don't want a random boolean or string there it's all about express accepted types as strict as possible in code to find errors early and in strict_types mode even the caller which needs to be fixed in the stack-trace