Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:44709 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 96213 invoked from network); 4 Jul 2009 20:08:52 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Jul 2009 20:08:52 -0000 Authentication-Results: pb1.pair.com smtp.mail=mls@pooteeweet.org; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=mls@pooteeweet.org; sender-id=unknown Received-SPF: error (pb1.pair.com: domain pooteeweet.org from 88.198.8.16 cause and error) X-PHP-List-Original-Sender: mls@pooteeweet.org X-Host-Fingerprint: 88.198.8.16 bigtime.backendmedia.com Linux 2.6 Received: from [88.198.8.16] ([88.198.8.16:34541] helo=bigtime.backendmedia.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 73/9F-06257-3D6BF4A4 for ; Sat, 04 Jul 2009 16:08:51 -0400 Received: from localhost (unknown [127.0.0.1]) by bigtime.backendmedia.com (Postfix) with ESMTP id 6FF30414405A; Sat, 4 Jul 2009 20:09:43 +0000 (UTC) X-Virus-Scanned: amavisd-new at backendmedia.com Received: from bigtime.backendmedia.com ([127.0.0.1]) by localhost (bigtime.backendmedia.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dirJlIMrOqT8; Sat, 4 Jul 2009 22:09:42 +0200 (CEST) Received: from [10.142.90.17] (gprs01.swisscom-mobile.ch [193.247.250.1]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: mls@pooteeweet.org) by bigtime.backendmedia.com (Postfix) with ESMTP id E001F414400B; Sat, 4 Jul 2009 22:09:41 +0200 (CEST) References: <5A834C9A-6D1B-49B7-88E6-FF047B084AB6@pooteeweet.org> <9B8C39B7-A5F8-4E61-BD7E-2069E584290D@pooteeweet.org> Message-ID: <5E12256D-40D0-4115-91C6-B5C35ABBF10D@pooteeweet.org> To: Paul Biggar In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable X-Mailer: iPhone Mail (7A341) Mime-Version: 1.0 (iPhone Mail 7A341) Date: Sat, 4 Jul 2009 22:08:14 +0200 Cc: PHP Internals Subject: Re: [PHP-DEV] weak and strict type checking RFC From: mls@pooteeweet.org (Lukas Kahwe Smith) On 04.07.2009, at 21:10, Paul Biggar wrote: > On Sat, Jul 4, 2009 at 7:12 PM, Lukas Kahwe =20 > Smith wrote: >>> I can't see the difference between your proposal and the =20 >>> conclusion I >>> reached yesterday? >>> >>> (which was that there is a near consensus around strict checks by >>> default, with casts allowed with some syntax). >> >> Well to me it Sounded like you wanted to Rely on Standard Type =20 >> juggling and >> what i am proposing is more strict than that. More over i am Not =20 >> convinced >> that strict should Be the Default. > > I don't know what you mean by standard type-juggling. Your proposal > really does not outline what you want very much, just what you're > against. As for strictness, if your proposal suggests that strict > typing is the default, I cannot see where. I did Not specify what doesnt Match in the RFC. I will fix that =20 omission on monday. I assumed it was clear that i tried to Provide =20 Complete examples for what will Pass. So Passung a String with =20 anything but 1 or 0 would Not Pass =C3=A0 Bool Type check. The other Thing that i wanted to make clear is that After the weak =20 Type check is that a cast should Happen afterwards. Finally i wanted to clarify my concerns about Structure typing to =20 ensure that the Short Syntax is a weak check and only with additional =20= Chars like the proposed ! Or something like that, can One get a Strict =20= Type check. Regards, Lukas=