Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:96873 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 86050 invoked from network); 13 Nov 2016 11:25:22 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 13 Nov 2016 11:25:22 -0000 Authentication-Results: pb1.pair.com smtp.mail=nikita.ppv@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=nikita.ppv@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.50 as permitted sender) X-PHP-List-Original-Sender: nikita.ppv@gmail.com X-Host-Fingerprint: 74.125.82.50 mail-wm0-f50.google.com Received: from [74.125.82.50] ([74.125.82.50:37364] helo=mail-wm0-f50.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 46/26-31581-1AD48285 for ; Sun, 13 Nov 2016 06:25:22 -0500 Received: by mail-wm0-f50.google.com with SMTP id t79so52246241wmt.0 for ; Sun, 13 Nov 2016 03:25:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=gbVNWLHTHHTOUD7wCL3eigLD1LonROWYWZVIbK/MfAA=; b=Qq2ucXgl/mFW9MfAxqmXF8wUU9ZS9ilF83RDovrD9GLktmQCTV388wtCz5XDi1i1gm lbsAkCKWx+PCOuDMBNPYtm/KV4qpMyb8UcrdBPUlIC+sMhUiJfmxecl64d3k/u6kDc0d s50jXPbX5PDNwi43itkSGl8NTnkVSruGxfO1kzuoyEjmKw0onAD0nXBKH59b2RNYV0Tu U81nsPY+JHlGTLJMtxWARmHfuKCmSxqci6IGMyssQxd+Po4+5LkRd/2bYu5ves+S1RKN Hq7ys0cLG/lpua1wmS92DDcwTljIjWEoSawN2niRvdxHe6Kj2yOguvyEyXdZze4Fy4Pn 0x8w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=gbVNWLHTHHTOUD7wCL3eigLD1LonROWYWZVIbK/MfAA=; b=dpISWgtmYxXyuO/5nCyNZplA21RBVJD64qKhBo9JzSG2siYY2j2+aFOP8yrLkxMfKI JV6wVfllsg0J98921FHtBGT8Hp/oMGdjw2dSVnTOum9CEXEB3XzR29sF9n6ztqs0JGXp AiW2cWbq8ntQiEo2FWglnXNTXIcdx85RCYOsSMa6h2qW2vxStz/iClgdh7VkDvN3dWAN ERWqPRilqUEaW4YnyXWOLUVUPruiEQuNLQhXGXmWbfEmB/NO7X25lR9uDNJ7j6IPtzF8 MFsm1n1jmsa01znyQnw0hox9u1cv4j5yNLMrA0xfacLUkyRdI/joYjHZK/u1On6cZ0cb Ws6w== X-Gm-Message-State: ABUngvcF07qWeAR1c4DMdtpnq8zvQ0awYVYN4rQUvos1+vDSrDHow5Vf1Xmr3boOa+EfdqR0wZeGcjOTe4H/zg== X-Received: by 10.194.174.229 with SMTP id bv5mr2459614wjc.21.1479036318283; Sun, 13 Nov 2016 03:25:18 -0800 (PST) MIME-Version: 1.0 Received: by 10.80.170.79 with HTTP; Sun, 13 Nov 2016 03:25:17 -0800 (PST) In-Reply-To: References: Date: Sun, 13 Nov 2016 12:25:17 +0100 Message-ID: To: Leigh Cc: PHP internals Content-Type: multipart/alternative; boundary=089e0141aa245c7e9905412cfa29 Subject: Re: [PHP-DEV] Strict types indicator in backtraces From: nikita.ppv@gmail.com (Nikita Popov) --089e0141aa245c7e9905412cfa29 Content-Type: text/plain; charset=UTF-8 On Wed, Oct 26, 2016 at 8:00 PM, Leigh wrote: > Hi all, > > I've written a small patch to add a "strict_types" key to the backtrace > information for functions. > > https://github.com/php/php-src/pull/2177 > > The idea here is to be able to see more easily whether a parameter may have > had it's type changed or not during a trace. > > Thoughts and opinions? > I'm not sure I understand what the intended use case here is. Can you maybe show an example of where this would be useful / how it would be used? Note that the parameter type may change even with strict_types (int->float). Further note that parameter values may change in the body of the function, so you don't have a guarantee that it's the original value in any case. Thanks, Nikita --089e0141aa245c7e9905412cfa29--