On Thu, 8 Sep 2005, Scott MacVicar wrote:
> Path for 5.0.6, it would seem odd to have a different behavior on the 5.0.x
> branch.
Committed.
Derick
--
Derick Rethans
http://derickrethans.nl | http://ez.no | http://xdebug.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscr
On Tue, 13 Sep 2005, Scott MacVicar wrote:
> Any chance of getting these applied to 5.0.x and 5.1?
Yes, it's on my todo list - will do that when I get back home.
Derick
--
Derick Rethans
http://derickrethans.nl | http://ez.no | http://xdebug.org
--
PHP Internals - PHP Runtime Development Mai
Any chance of getting these applied to 5.0.x and 5.1?
Scott
Scott MacVicar wrote:
Path for 5.0.6, it would seem odd to have a different behavior on the
5.0.x branch.
Scott
Derick Rethans wrote:
On Thu, 8 Sep 2005, Stanislav Malyshev wrote:
DR>>But they can still do that.. With "shutdown fu
Path for 5.0.6, it would seem odd to have a different behavior on the
5.0.x branch.
Scott
Derick Rethans wrote:
On Thu, 8 Sep 2005, Stanislav Malyshev wrote:
DR>>But they can still do that.. With "shutdown functions" I meant
DR>>functions registered with register_shutdown_function().
Ah...
On Thu, 8 Sep 2005, Stanislav Malyshev wrote:
> DR>>But they can still do that.. With "shutdown functions" I meant
> DR>>functions registered with register_shutdown_function().
>
> Ah... This is smaller problem - register_shutdown_function() ones can be
> called on "before dtors" stage.
Indeed
DR>>But they can still do that.. With "shutdown functions" I meant
DR>>functions registered with register_shutdown_function().
Ah... This is smaller problem - register_shutdown_function() ones can be
called on "before dtors" stage.
--
Stanislav Malyshev, Zend Products Engineer
[EMAIL PROTECTED
On Thu, 8 Sep 2005, Stanislav Malyshev wrote:
> EK>>I do belive that we should have kept BC here and allow use of objects
> EK>>in shutdown functions, ie. call them before calling object
> EK>>destructors.
>
> We have classical c&e problem here - if we defer dtors to after shutdowns,
> they co
EK>>> But we have that, just no extensions are using it... What I do think
Well, I guess they'd better start to use then :)
EK>>> that we need to do is to call the shutdown handlers before the dtors,
EK>>> now we do it the "wrong" way around making things less flexible. And,
I don't see how
Derick Rethans wrote:
> On Wed, 7 Sep 2005, Andi Gutmans wrote:
>
>
>>The real solution is to have a two-phased shutdown sequence in PHP 6 because
>>we're constantly "Fixing" the shutdown due to chicken&egg problem.
>
>
> But we have that, just no extensions are using it... What I do think
>
On Wed, 7 Sep 2005, Andi Gutmans wrote:
> The real solution is to have a two-phased shutdown sequence in PHP 6 because
> we're constantly "Fixing" the shutdown due to chicken&egg problem.
But we have that, just no extensions are using it... What I do think
that we need to do is to call the shut
The real solution is to have a two-phased shutdown sequence in PHP 6
because we're constantly "Fixing" the shutdown due to chicken&egg problem.
At 11:19 AM 9/6/2005, steve wrote:
I agree. Having no access MySQL(i) during shutdown has already broken
scripts I've used. Thankfully, Jani mentioned t
I agree. Having no access MySQL(i) during shutdown has already broken
scripts I've used. Thankfully, Jani mentioned the change so I no
longer felt like I was going crazy, and I was able to work around it
by creating a "shutdown object" that contained references to all the
objects it might need, and
Zeev Suraski wrote:
If there are no (ultra last) objections, I'll roll 5.0.5 tomorrow
morning (.il/Europe time) and post it in the evening.
Zeev
I'm still objecting to a patch by Jani made in April to move destructor
before shutdown functions. It was in response to the following report,
htt
Zeev Suraski wrote:
> Any outstanding things for this release beyond PEAR and XMLRPC? I'd
> like to roll RC2 as soon as possible.
PEAR is not an issue (that's what my message about finishing sync was
all about)
Greg
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit:
14 matches
Mail list logo
