Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:107521 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 65070 invoked from network); 11 Oct 2019 20:55:45 -0000 Received: from unknown (HELO php-smtp3.php.net) (208.43.231.12) by pb1.pair.com with SMTP; 11 Oct 2019 20:55:45 -0000 Received: from php-smtp3.php.net (localhost [127.0.0.1]) by php-smtp3.php.net (Postfix) with ESMTP id 195DF2D19B3 for ; Fri, 11 Oct 2019 11:38:58 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp3.php.net X-Spam-Level: X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS3215 2.6.0.0/16 X-Spam-Virus: No Received: from mail-oi1-x22f.google.com (mail-oi1-x22f.google.com [IPv6:2607:f8b0:4864:20::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by php-smtp3.php.net (Postfix) with ESMTPS for ; Fri, 11 Oct 2019 11:38:57 -0700 (PDT) Received: by mail-oi1-x22f.google.com with SMTP id k20so8850957oih.3 for ; Fri, 11 Oct 2019 11:38:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=mhFMb8o9zrAQ6ObCINoy2kS+FnBhMLFIDC3fnsowrgc=; b=lgLSKmpJuSceOgifcFc4G3HRu6/sTKU6219Vqti3Z3iicLW0sX4+FS+ILXScHhgpeG 3Jy7bLRB6Kj9D2wTDvQTReIUz3kIU7xRE5F5aF/TM47reLzsHiBvnMZkPVNrOzy9iu8P r5vnyTODtMYmtz1Kthq9h0T57Ohl+LIjeXFu81gikT4XeHBv9chE9JdpBBzgMVqE0GjH Zr5KDMN2TAtDFADulP5lyEgh/VVhnOs+7Mnk/bamqC0PoTkqVReyz0dR+tyk2g1iKHs7 cwjrEsxXjFfm5aZak2Js0NbeDKTCefr+kelm9J5V0YUC5mC0E/wwQ/CK3NjCon1qKJXI eIVw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=mhFMb8o9zrAQ6ObCINoy2kS+FnBhMLFIDC3fnsowrgc=; b=jp9lRLr8uIkRu98Ylutiexe9+aLK1YXArktJ7ZgE9KrCN9xwdXnfXN6obY4vmgEdcC 13kK74eRvLNyZZAFtXCL4UybbV/GIXInYHvBAaHoq39bvO0S+WMDBUZrkuAFtDfdktIp zeqJTGWfZxLXpiIBd7lYJAIZuErK9F4gxUHLJYoAzYih9WxMd9l9m6Na16Jj9+u8/gzy LnTGaFGUrsYoZ6Uw7RPWiQzK2PPD1iqhtgG2NA8se4QOmdioCpEbkkI2ySuvmwvKaQnG k6R08TTqkt6kS4NNpByLE/f8rrC63T5+ISbkKi1Kvdgk7FICZBKJTucSlQ4khCLZVo34 GPFA== X-Gm-Message-State: APjAAAUACtc5aX98m0YUZKtGS2A8L6N78KeiXyskg5hS+35lNMiIYPQn PnQGUGt3tCOJdAmoJTjfAMxyOkgTv55PL/x2rII= X-Google-Smtp-Source: APXvYqy/1AVExA1mEslZLUXI3fAmNVWH5aWzauSa8Fqtd7bOwME8sogEB7WC4H2WbuUMGClVlrUY5TgawkQ4G6ktsIM= X-Received: by 2002:aca:882:: with SMTP id 124mr13608970oii.54.1570819136905; Fri, 11 Oct 2019 11:38:56 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Fri, 11 Oct 2019 19:38:44 +0100 Message-ID: To: bishop@php.net Cc: Nikita Popov , PHP internals Content-Type: multipart/alternative; boundary="000000000000a9669c0594a6d43b" X-Envelope-From: Subject: Re: [PHP-DEV] exit() via exception From: oludonsexy@gmail.com (Olumide Samson) --000000000000a9669c0594a6d43b Content-Type: text/plain; charset="UTF-8" I'm thinking exit() shouldn't be catchable to maintain status quo, and it should be focused on the reason it was suggested(Unwinding stacks and cleaning up memories instead of longjmp'ing to shutdown). If there's any need to catch it's exception, that can be handled later through maybe a RFC discussion. This can be implemented directly without having any user land interaction since the throwing and catching can't be caught by any user land code(top-most hierarchy without possibility to be caught, which might result in compile time error). All the best --000000000000a9669c0594a6d43b--