Re: [Phplib-users] PHP 4.3.0

[nathan r. h. <na...@ds...>]

Is that a GLOBALS::delete() or an all namespcae thingy?

Oh waitaminit.. 'delete' is a reserved word, which means it's probably a
langauge construct which means no.. scope don't matter becasue it'll be
interpeted at parse time, not execution time..

God, that's dumb (well, the idea is good, the naming is perhaps not
insightful as one could hope for).  I doubt we're the only people with a
delete() function, why doesn't ZE2 call it something more intuitive like..
oh.. obj_delete()?  rm_object(), del_obj()? obj_del()?

Argh.

Other than that there seems to be a lot of nifty stuff in ZE2.  4.3.0 is
still marked as alpha and I doubt it'll be seeign a lot of light on
production servers anytime soon while the bugs get shaken out of ZE2;
however, we probably need to fix this RSN before it bites us.

Daniel, can you please file a bug on this in the SF trackers?  I will try
to get a fix in this weekend and release a 7.4.pre2 after that.

Anyone on the php-dev list know if this issue has been bandied about
before?

FWIW, delete() just drops the session from the database table.  It's not a
private API function but it's also not something you need to call if you
feel confident enough with the builtin GC of the session classes (which
also use delete() I think).

This will chnage the API by some, though in  short term we'll need to add
a boolean $ZE2 flag that when flase will present a stub delete() that maps
to the renamed function and perhaps issues a warning or soemthing.

-n
------
nathan hruby
na...@ds...
------

On Tue, 18 Jun 2002, Daniel Bondurant wrote:

> looking at the release notes for PHP 4.3.0.  There will be some trouble
> with phplib and the Zend 2.0 engine.
> http://www.php.net/ZEND_CHANGES.txt
>
> First thing I noticed was:
>     * Forced deletion of objects.
>
>       The Zend Engine 1.0 had no means to force deletion of an object
>       if there are still references to it. The newly introduced delete
>       statement calls the object's destructor and frees it even if the
>       object is referenced by some other places in the engine. Other
>       references to the deleted object become stale and trying to
>       access them results in a fatal error.
>
>       Note that if you have a user-defined function delete() in an old
>       script, this script will yield a parser error with the Zend
>       Engine 2.0, since 'delete' is now a reserved word.
>
>
> session.inc and session4.inc both have delete() functions.
> There will probably be some other problems, but I don't know the
> internals of phplib enough to hunt them all down.
>