Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:62802 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 80792 invoked from network); 4 Sep 2012 16:36:34 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Sep 2012 16:36:34 -0000 Authentication-Results: pb1.pair.com smtp.mail=simpleshot@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=simpleshot@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.223.170 as permitted sender) X-PHP-List-Original-Sender: simpleshot@gmail.com X-Host-Fingerprint: 209.85.223.170 mail-ie0-f170.google.com Received: from [209.85.223.170] ([209.85.223.170:33831] helo=mail-ie0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 61/16-46870-01E26405 for ; Tue, 04 Sep 2012 12:36:33 -0400 Received: by ied7 with SMTP id 7so5913720ied.29 for ; Tue, 04 Sep 2012 09:36:30 -0700 (PDT) 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 :content-type; bh=iE/vJG6ghYgVIJo5kq1onS9QPztfHebi+Y8iJ8iMWDE=; b=V1z9kZ2k4LFaKqSjQgn2lT/jH69WXdOn7l156+U1KNIq4erilOuFE+JUPQVlaVvPr/ l/X7K+vH8ky6RGnYeGkt+xdvQNywFGRAjx50sPue+oHwJSbNRgfF6u6tAdIF9nrK7RLr 0dzmkiywhwsSUf/36ez4xEd2/1DKE7x42zi6ttjX0d2EqT8HMADISASAHoxxl9IEir2f Y3Q1w/24EEZ7yxQtEOJxEXQf68j5s6m/AWVQwZHzmXnwqJJ4f+oCsYWEvjUjr1o7Js0T NX7M5GlPmJpZz7X6qP7VBcEr6tFRe3VGZOsmoSNa8SChTDnTpwuWYcD9K3rcQ9PICkXo GnpA== MIME-Version: 1.0 Received: by 10.60.13.37 with SMTP id e5mr16025102oec.98.1346776590235; Tue, 04 Sep 2012 09:36:30 -0700 (PDT) Received: by 10.60.118.167 with HTTP; Tue, 4 Sep 2012 09:36:30 -0700 (PDT) In-Reply-To: References: <5040DC47.8000305@ajf.me> <5040F4D9.80206@sugarcrm.com> <5042946A.80204@sugarcrm.com> <5042A7D6.7050001@lerdorf.com> <50452713.3020307@sugarcrm.com> <5045CAA3.6000409@lsces.co.uk> <5045E044.9080809@lsces.co.uk> <5045F939.6010806@lsces.co.uk> <5045FD98.8080306@lsces.co.uk> Date: Tue, 4 Sep 2012 12:36:30 -0400 Message-ID: To: PHP Development Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [PHP-DEV] E_STRICT 'errors' - was Are exceptions allowed in php core? From: simpleshot@gmail.com (Adam Richardson) On Tue, Sep 4, 2012 at 9:43 AM, Ferenc Kovacs wrote: > never heard of that one before. > > for example, running > for($i=0;$i<100;$i++){ > $foo="foo_".$i; > ${$foo}->bar = 123; > } > echo "done"; > > gives me 100 E_STRICT, but still executes just fine and prints "done" at > the end. > the only explanation that I can think of is that you have a custom error > handler somewhere in your code, which somehow does something unexpected > (exits the script execution or does something like an infinite recursion > which segfaults/OOMs your application. > if you still think that it isn't the case, then please open an issue on > bugs.php.net with a reproduce script, as this would be clearly a bug. I think Ferenc is correct in that this sounds like there's a custom error handler somewhere. If the custom error handler collects error info and then throws an exception (as has been detailed in various blog posts as one manner of unifying the errors), this would cause the trouble you're seeing. Adam -- Nephtali: A simple, flexible, fast, and security-focused PHP framework http://nephtaliproject.com