On Mon, 2003-06-23 at 11:59, Zeev Suraski wrote:
> At 18:39 23/06/2003, Rasmus Lerdorf wrote:
> >On Mon, 23 Jun 2003, Zeev Suraski wrote:
> > > Maybe we can go for a compromise - enable it with ZEND_INI_PERDIR and
> > > ZEND_INI_UUSE. That way it will be possible to use it with httpd.conf /
> > > .htaccess / ini_set(), but not with php.ini, so people will at least have
> > > to make a slightly more informed decision to enable it. Just a suggestion,
> > > I'm not sure I like it myself :)
> >
> >That'd be a bit weird and people would ask us why it doesn't work in the
> >php.ini file.
>
> I agree.
>
> >I think you can get close to the same effect by simply not
> >listing it in the default php.ini file so they would actually have to read
> >about it in the docs along with its implications before they knew how to
> >set it.
>
> Not sure, I'm not even sure whether it should be missing from php.ini or
> just have a BIG warning about it, saying it should not be used for shared
> hosts...
>
I think it should just be a function then. Most PHP projects have one
file that every other file includes. Why can't they just add that
function call to this file?
If you put this option in a place that can be globally settable, you
automatically require, warning or not, that people put a ::
ini_set('ze2.implicit_clone', false);
at the top of their scripts.
I think we have to make it unsettable in php.ini. I don't care what we
do outside of that.
-Sterling
PS: Remember, not all shared hosts allow you to set options in a
.htaccess file.
> Zeev
--
"I can't give you a brain, so I'll give you a diploma"
- The Great Oz, The Wizard of Oz
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
