By the way, if it's really important, we can look into supporting it. The
way it was before - it worked in most cases (assuming you never tried to
use a class before you dl() the corresponding extension), but could result
in crashes in other cases.
I don't think it's very important, though. dl() should most probably be
deprecated from the language, as it's not supported in thread safe mode,
it's slow and insecure. It also creates a host of interesting bugs/buglets
that are difficult to hunt and fix. Other than that - it's great :)
Zeev
At 17:22 06/08/2001, Thies C. Arntzen wrote:
>On Mon, Aug 06, 2001 at 09:08:05AM -0500, Andrei Zmievski wrote:
> > On Mon, 06 Aug 2001, Thies C. Arntzen wrote:
> > > thies Mon Aug 6 09:36:09 2001 EDT
> > >
> > > Modified files:
> > > /php4/ext/standard basic_functions.c incomplete_class.c
> > > php_incomplete_class.h var.c
> > > /php4/ext/wddx wddx.c
> > > Log:
> > > we can no longer register internal-classes once the script is started.
> > > therefore the "incomplete class" is now registered at MINIT time.
> >
> > How it's not possible all of a sudden?
>
> i don't think this is crucial for the gtk stuff as this
> problem only arises once the request ends _and_ a new request
> starts. the shutdown in the engine has been changed to only
> destruct classes (from the end of the list) until the 1st
> internal class is found. so:
>
> <?
> class tubu {
> }
> dl("php-gtk");
> class hallo {
> }
> ?>
>
> would (now) destruct class hallo but not tubu. zeev assured me that
> dl()'ing modules that created classes never "really" worked
> (it would always have request shutdown-trouble as the
> c-module would get unloaded but the class table would still
> point into the unloiaded module). i kinda don't like it, but
> i take zeevs word that it never worked properly.
>
> tc
--
Zeev Suraski <[EMAIL PROTECTED]>
CTO & co-founder, Zend Technologies Ltd. http://www.zend.com/
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]