Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:80066 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 65804 invoked from network); 1 Jan 2015 17:46:17 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 1 Jan 2015 17:46:17 -0000 Authentication-Results: pb1.pair.com header.from=mails@thomasbley.de; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=mails@thomasbley.de; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain thomasbley.de from 85.13.137.24 cause and error) X-PHP-List-Original-Sender: mails@thomasbley.de X-Host-Fingerprint: 85.13.137.24 dd15934.kasserver.com Received: from [85.13.137.24] ([85.13.137.24:44364] helo=dd15934.kasserver.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 52/B1-60454-8E785A45 for ; Thu, 01 Jan 2015 12:46:16 -0500 Received: from dd15934.kasserver.com (dd0802.kasserver.com [85.13.143.1]) by dd15934.kasserver.com (Postfix) with ESMTPSA id CE5EF260995; Thu, 1 Jan 2015 18:46:12 +0100 (CET) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-SenderIP: 95.90.235.1 User-Agent: ALL-INKL Webmail 2.11 In-Reply-To: References: <41D5BB0B-73AF-488E-968D-90B2878E3178@ajf.me> <20150101164402.EB1442605AB@dd15934.kasserver.com> To: levim@php.net Cc: ajf@ajf.me, nikita.ppv@gmail.com, internals@lists.php.net Message-ID: <20150101174612.CE5EF260995@dd15934.kasserver.com> Date: Thu, 1 Jan 2015 18:46:12 +0100 (CET) Subject: Re: [PHP-DEV] [RFC] Scalar Type Hints From: mails@thomasbley.de ("Thomas Bley") when looking into phpdoc, e.g. http://de.php.net/substr we have string and int everywhere in function definitions, do you want to change the whole documentation? Regards Thomas Levi Morrison wrote on 01.01.2015 18:19: > On Thu, Jan 1, 2015 at 9:44 AM, Thomas Bley wrote: >> I think it is no problem to add strict parameter type hints with another rfc >> (if this rfc gets accepted), e.g. function foobar(string! $str, int! $str){} >> or any other syntax. >> > > I would rather have it the other way around. `string $str` is strict > and some other syntax (notably `(string) $str` or `@string $str`) can > be loose. >