Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:48410 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 40948 invoked from network); 23 May 2010 12:51:36 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 May 2010 12:51:36 -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 188.40.37.16 cause and error) X-PHP-List-Original-Sender: mls@pooteeweet.org X-Host-Fingerprint: 188.40.37.16 hq1.backendmedia.com Linux 2.6 Received: from [188.40.37.16] ([188.40.37.16:54617] helo=hq1.backendmedia.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id B3/CB-54147-6D429FB4 for ; Sun, 23 May 2010 08:51:35 -0400 Received: from localhost (unknown [127.0.0.1]) by hq1.backendmedia.com (Postfix) with ESMTP id AAB18200C18D; Sun, 23 May 2010 12:51:36 +0000 (UTC) X-Virus-Scanned: amavisd-new at backendmedia.com Received: from hq1.backendmedia.com ([127.0.0.1]) by localhost (hq1.backendmedia.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HgXLijuHKNcu; Sun, 23 May 2010 14:51:36 +0200 (CEST) Received: from soitgoes.lan (g225150217.adsl.alicedsl.de [92.225.150.217]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: mls@pooteeweet.org) by hq1.backendmedia.com (Postfix) with ESMTPSA id 2599E200C187; Sun, 23 May 2010 14:51:36 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v1078) Content-Type: text/plain; charset=us-ascii In-Reply-To: Date: Sun, 23 May 2010 14:51:30 +0200 Cc: internals@lists.php.net Content-Transfer-Encoding: quoted-printable Message-ID: <0F9B2086-BEF9-4621-8518-73DA64B1008D@pooteeweet.org> References: <7.0.1.0.2.20100522175819.0a601c68@zend.com> <93EFAEF4-26F3-44A1-85ED-5E71E665B966@pooteeweet.org> <698DE66518E7CA45812BD18E807866CE0427ED12@us-ex1.zend.net> To: Sebastian Bergmann X-Mailer: Apple Mail (2.1078) Subject: Re: [PHP-DEV] Type hinting From: mls@pooteeweet.org (Lukas Kahwe Smith) On 23.05.2010, at 14:44, Sebastian Bergmann wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 >=20 > On 05/23/2010 01:08 AM, Ilia Alshanetsky wrote: >> any mistmatch results in an error >=20 > An error that is recoverable. So not only is the "strict typing" > optional, but "type mismatches" can be caught and handled. again .. are you saying that a recoverable error is more than a way to = display a nice error message instead of a white screen? anyway, the fundamental question at hand is where the "burden" of = correct typing should be placed, on the API consumer or on the API = provider. this also ties in with the question if API consumers are = likely to have "properly" typed (aka typed in the way the _various_ API = he consumes expect) by default or not. i think this is the key question = to answer when deciding to go with enabling type hinting or full out = strict typing. regards, Lukas Kahwe Smith mls@pooteeweet.org