Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:81857 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 48792 invoked from network); 5 Feb 2015 02:05:00 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 5 Feb 2015 02:05:00 -0000 Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.179 as permitted sender) X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 209.85.216.179 mail-qc0-f179.google.com Received: from [209.85.216.179] ([209.85.216.179:56900] helo=mail-qc0-f179.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 3D/03-40930-5CFC2D45 for ; Wed, 04 Feb 2015 21:04:53 -0500 Received: by mail-qc0-f179.google.com with SMTP id w7so4459878qcr.10 for ; Wed, 04 Feb 2015 18:04:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=hXxWohDwbwN+VIpv9QTmM5wE/TC4X2aKb7WSu7Ekx3I=; b=ZuKjiBfP2cg+/lDQkcB5QKsYaBCJIhL6a2kFtOVZnbe0GS7F8DhqeBhsQzuy6RHYEl G85jNmgZBgUWL2bEuVJJfDn4haXiQYJ9GCtfNjUKMxCDG0ITe84H862et+Z40xldJx+7 yH7ZyD+Ri63eCoXhHv5VAOHghIKZz0owRjnBWs/Tuvz0PAIRdDKDVQtp4W3WhbjyPSjc KWRJwBCCUS0hD+DfrNWEaBolxXqCrk7bxTOv8o7nw+hli87zcUd7lMaf3IM92dazseHe QcUXck3zH3oBO/zI0tIxhvVxDnWkFOfMUJrAxutiyHIaAC8/7cT+ShglRE2r+FUROIws NPPQ== MIME-Version: 1.0 X-Received: by 10.224.89.2 with SMTP id c2mr3005415qam.75.1423101891313; Wed, 04 Feb 2015 18:04:51 -0800 (PST) Received: by 10.96.3.168 with HTTP; Wed, 4 Feb 2015 18:04:51 -0800 (PST) Received: by 10.96.3.168 with HTTP; Wed, 4 Feb 2015 18:04:51 -0800 (PST) In-Reply-To: <54D2C018.6050803@gmail.com> References: <00c101d04049$ca411ec0$5ec35c40$@tekwire.net> <54D1CA7C.8060204@php.net> <54D1E6EC.7060702@php.net> <54D2B3FA.6020900@gmail.com> <54D2C018.6050803@gmail.com> Date: Thu, 5 Feb 2015 09:04:51 +0700 Message-ID: To: Stas Malyshev Cc: Andrey Andreev , PHP internals , Sebastian Bergmann Content-Type: multipart/alternative; boundary=001a11c3c7b4b63df0050e4dba5e Subject: Re: [PHP-DEV] What do we need strict scalar type hints for? From: pierre.php@gmail.com (Pierre Joye) --001a11c3c7b4b63df0050e4dba5e Content-Type: text/plain; charset=UTF-8 On Feb 5, 2015 7:58 AM, "Stanislav Malyshev" wrote: > > Hi! > > > Adding another concept, not changing the existing ones. And really, > > it's just simplifying what is already present via is_() > > runtime checks, making our lives a little bit easier. > > There's a very big difference between allowing to check types (and then > do whatever you wish) and having functions throw fatal errors if types > do not match. Totally agree. However, to be sure everyone understands it, you, as an user of a library using strict mode, won't see it. I agree that a library using strict and release untested code may be an issue, but then it is a bug on the library itself, no biggie to fix. > -- > Stas Malyshev > smalyshev@gmail.com > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > --001a11c3c7b4b63df0050e4dba5e--