Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:53386
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.211.66 cause and error)
To: Arpad Ray <arraypad@gmail.com>
Cc: internals@lists.php.net
In-Reply-To: <BANLkTi=4fkchuWO9_zfYeEkao54X1Lo0=w@mail.gmail.com>
References: <BANLkTi=4fkchuWO9_zfYeEkao54X1Lo0=w@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Date: Mon, 20 Jun 2011 13:37:27 +0200
Message-ID: <1308569847.3172.18.camel@guybrush>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [PATCH] unregister_shutdown_function()
From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=)

On Mon, 2011-06-20 at 07:36 +0100, Arpad Ray wrote:
> This patch implements unregister_shutdown_function(), which removes a
> function already registered with register_shutdown_function().
> 
> It resolves request #53702 (according to google, not sure if it's
> still active) and I've thought it a curious absence for a while.

Why do you register a shutdown function if you want to remove it again?
Shouldn't you fix the architecture of your code instead of relying on
such functions?

> The patch (against trunk) is at:
> http://spellign.com/patches/php-trunk-unregister_shutdown_function.patch

Does register_shutdown_function() work with closures? (Didn't test it)
Then the following should work, too, which isn't the case in your code:

    $a = function() {};
    register_shutdown_function($a);
    unregister_shutdown_function($a);

I also think once that functionality is there the next request will be

    get_registered_shutdown_functions()

or something along the lines.

johannes