Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:61689 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 13384 invoked from network); 24 Jul 2012 15:16:27 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 24 Jul 2012 15:16:27 -0000 Authentication-Results: pb1.pair.com smtp.mail=rasmus@lerdorf.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=rasmus@lerdorf.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lerdorf.com from 209.85.160.170 cause and error) X-PHP-List-Original-Sender: rasmus@lerdorf.com X-Host-Fingerprint: 209.85.160.170 mail-gh0-f170.google.com Received: from [209.85.160.170] ([209.85.160.170:51338] helo=mail-gh0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 4B/0A-17533-A4CBE005 for ; Tue, 24 Jul 2012 11:16:27 -0400 Received: by mail-gh0-f170.google.com with SMTP id g2so7726209ghb.29 for ; Tue, 24 Jul 2012 08:16:26 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding:x-gm-message-state; bh=7uYIdsRz6gQrk0ieh10no8+4cewpdLNa1HPBfgHCP10=; b=fz4aEqRTMNVMQNBJ0rt3H5H3K8+6kGROPtla/+r3mSOTPvcd1ufUvzCwGfTAFTksgh l03/WG+EEe8Gbfw4r1i0x6/GzasZC3lsbh28iyQY6kOTA17VxtfRYyfNOMowPDCpf6gO 3hKmxXI+LDlwZ0jYc9JUYSV5lldbeEPz1r/zD9yT9vbAJW8b2BsCDvPaqOCAntqdfIxb PiMXOVBCWDgZ9Iar1roseSLSHDW8bbMonTXcQmrrwB3G0NuxuHOkCaNvNI1EXdOcfm/x N3rCt8UMN1kZocpyYYJUzFZ6HsB21Sud3/zRZEMY0cJdfI9+xzE9Bh1VQcXOfh+cRmvH tOtw== Received: by 10.236.193.105 with SMTP id j69mr19665313yhn.21.1343142986687; Tue, 24 Jul 2012 08:16:26 -0700 (PDT) Received: from [172.16.26.30] ([38.106.64.245]) by mx.google.com with ESMTPS id x4sm31087927yhh.2.2012.07.24.08.16.24 (version=SSLv3 cipher=OTHER); Tue, 24 Jul 2012 08:16:25 -0700 (PDT) Message-ID: <500EBC47.2080200@lerdorf.com> Date: Tue, 24 Jul 2012 08:16:23 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0 MIME-Version: 1.0 To: Nikita Popov CC: Laruence , PHP Internals References: In-Reply-To: X-Enigmail-Version: 1.5a1pre Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Gm-Message-State: ALoCoQmtsq7glW+m5IDUOeBmwkW4KwCYyxL6ddX+XpJkGO9JV79QHJEPL0prUupDOChoyK5Bx9/9 Subject: Re: [PHP-DEV] [RFC] Supports 'finally' keyword for PHP exceptions From: rasmus@lerdorf.com (Rasmus Lerdorf) On 07/24/2012 06:35 AM, Nikita Popov wrote: > On Tue, Jul 24, 2012 at 1:20 PM, Laruence wrote: >> Hi: >> As the previous threads disscussed, I make a implemention. >> >> here is the RFC: https://wiki.php.net/rfc/finally >> >> any suggestions? > > The finally clause comes with a very strong promise that the code in > the clause will run in absolutely any case (short of sigkill, maybe). No it doesn't, at least not in Java. A fatal Java error or an explicit call to System.exit() will cause the finally clause to not be executed. It is a simple exception-level construct and doesn't in any way promise to be called in a fatal error situation. And regardless of what Java does, we are free to define it and provide whatever promises we want here, but keeping it in line with Java's implementation makes sense to me. -Rasmus