Re: Re: cvs: php4 /ext/standard basic_functions.c incomplete_class.c php_incomplete_class.h var.c /ext/wddx wddx.c

From: Date: Mon, 06 Aug 2001 04:10:06 +0000
Subject: Re: Re: cvs: php4 /ext/standard basic_functions.c incomplete_class.c php_incomplete_class.h var.c /ext/wddx wddx.c
References: 1  Groups: php.dev 
Request: Send a blank email to php-dev+get-62302@lists.php.net to get a copy of this message 
On Mon, 6 Aug 2001, Zeev Suraski wrote:

> At 06:30 06/08/2001, Sterling Hughes wrote:
> >On Mon, 6 Aug 2001, Andrei Zmievski wrote:
> >
> > > On Mon, 06 Aug 2001, Zeev Suraski wrote:
> > > > How so?  I can understand that people get used to it, but it's really
> > > > bad.  extensions should be loaded in the php.ini file.  There's really no
> > > > good reason for using dl() over the php.ini method.
> > >
> > > Of course there is. One example is using the same PHP binary to run
> > > scripts that use different extensions that wouldn't necessarily want to
> > > load all the time through php.ini.
> > >
> >
> >     Also, just to mention, right now it might not be that big a deal to
> >     load them all in php.ini (well something as big PHP-GTK would be,
> >     but...), however, as PHP gets more and more extensions written in C,
> >     there needs to be this functionality.
>
> Why?  Whatever extension you use on your box, put them in the
> php.ini.  dl() is never a better option.
>

    What if you use 50 different shared extensions, for different
    scripts on the same box? Should you load them all in each time?
    I don't think so...

    -Sterling

Thread (52 messages)

« previous php.dev (#62302) next »