[prev in list] [next in list] [prev in thread] [next in thread] 

List:       php-internals
Subject:    Re: [PHP-DEV] New INIs, Round Two.
From:       Eric Stewart <ericleestewart () gmail ! com>
Date:       2009-02-19 5:19:05
Message-ID: ce6b011c0902182119j41196806gddddecb00b7a0c5e () mail ! gmail ! com
[Download RAW message or body]


Christopher,
I looked into the addition of the use of variables in the INI files and I
wasn't able to find much documentation on it. Also, I haven't been able to
play with them and see exactly how they work. For now I don't feel confident
in adding my own comments about it. If you want to write up the comments
about it, I'll be happy to include those.

Eric

On Tue, Feb 17, 2009 at 1:53 PM, Christopher Jones <
christopher.jones@oracle.com> wrote:

>
> Eric,
>
> Should uncommented parameters that seem to have the default value be
> commented out?  For example "asp_tags" and "precision".  If the
> parameters don't always have the same default value everywhere, should
> they be documented in Quick Reference section as having a different
> value to the default?
>
> Eric Stewart wrote:
> > 4. I mistakenly had the development and production values of
> > allow_call_time_pass_reference reversed. This error has been
> > corrected.
>
> I really think this should be Off in both cases to discourage use.
> The doc http://www.php.net/ini.core says "This method is deprecated
> and is likely to be unsupported in future versions of PHP/Zend."
>
> > 10. The production value of error_reporting has been changed to E_ALL |
> > ~E_DEPRECATED.
>
> This should use '&', as Dave already pointed out on the list.
>
> > 12. The oci8.events and oci8.old_oci_close_semantics example values now
> use
> > the boolean constants.
>
> Thanks.
>
> > 13. Many people have asked why the links to the online documentation for
> > each directive are specifically to the English version.
>
> Regardless of the language issue, can the URLs consistently use "www"
> instead of "us2"?  At the moment both occur.
>
> Can the generic case in this come first:?
>
>  ; 6. Windows directory (C:\windows or C:\winnt), or
> --with-config-file-path
>  ; compile time option.
>
> i.e change it to
>
>  ; 6. The directory from the --with-config-file-path compile time
>  ; option, or the Windows directory (C:\windows or C:\winnt)
>
> The general documentation could mention the use of variables as seen
> in ext/standard/tests/general_functions/parse_ini_basic.{phpt,data}:
>
>  basicval = bar
>  var1 = ${basicval}
>
> The general documentation could mention that absolute paths to
> extensions are (now) supported:
>
>  extension=/path/to/extension.so
>
> This should use "its" not "it's":
>
>  ; PHP attempts to find and load this configuration from a number of
> locations.
>  ; The following is a summary of it's search order:
>
> The first "it's" below should be "its":
>
>  ; php.ini-development is very similar to it's production variant, except
> it's
>  ; much more verbose when it comes to errors.
>
> This should be "its" in:
>
>  ; php.ini-production contains settings which hold security, performance
> and
>  ; best practices at it's core.
>
> Ditto in:
>
>  ; Turning on this setting and managing it's maximum buffer size can yield
> some
>
> Ditto in:
>
>  ;   Integer = Enables the buffer and sets it's maximum size in bytes.
>
> Ditto in:
>
>  ; this to 1 will cause PHP CGI to fix it's paths to conform to the spec.
>  A setting
>
> There's an (existing) typo in this description, I guess "ignore
> libjpeg warnings" was the intention:
>
>  ; Tell the jpeg decode to libjpeg warnings and try to create
>  ; a gd image.
>
> Chris
>
> --
> Email: christopher.jones@oracle.com  Tel: +1 650 506 8630
> Twitter:  http://twitter.com/ghrd    Free PHP Book:
> http://tinyurl.com/UGPOM
>


[prev in list] [next in list] [prev in thread] [next in thread]