Re: [PHP-DEV] spl_autoload vs __autoload

Pierre wrote: On a related note: Imo for users the real problems are different extensions, which we won't enable by default (due to their dependency on external stuff) and which might be available on some host or different php.ini settings. For instance I was once annoyed by zlib not being availa

Re: [PHP-DEV] mail() logging for PHP

Hi, Ilia Alshanetsky wrote: I am going to finalize the patch and add it to 5.2.2 in the coming weeks. Ilia There is no trace of such patch in PHP 5.2.2 changelog. Any news on it? Thanks. Mathieu -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.ne

Re: [PHP-DEV] mail() logging for PHP

Hi, Thanks for the update! Much appreciated. Is there any chances to get this patch for PHP 4.x too? Mathieu On 2007-02-08 10:50, Ilia Alshanetsky wrote: I am going to finalize the patch and add it to 5.2.2 in the coming weeks. Ilia On 8-Feb-07, at 10:44 AM, Mathieu Gagné wrote: Hi, Any

Re: [PHP-DEV] mail() logging for PHP

Hi, Any news about it? This would be very interesting having this feature. As Richard Lynch said, ISPs would love it. Mathieu On 2006-12-14 15:50, Ilia Alshanetsky wrote: The full path is only for the log files, the header only contains the script name. As far as requests to include the domain

Re: [PHP-DEV] mail() logging for PHP

Hi, Any news about it? This would be very interesting having this feature. As Richard Lynch said, ISPs would love it. Mathieu On 2006-12-14 15:50, Ilia Alshanetsky wrote: The full path is only for the log files, the header only contains the script name. As far as requests to include the domain

Re: [PHP-DEV] [RFC] E_DEPRECATED

oad on it, daily logrotations were not enough to limit the overgrow of logs files. Just putting my 2 cents as this is problems I had to fixed as a sysadmin. FYI, every domains have different error_log and access_log files. -- Mathieu Gagné -- PHP Internals - PHP Runtime Development Mailing List To un

Re: [PHP-DEV] [RFC] E_DEPRECATED

Hi, > I personally also don't see a good reason to disable E_WARNING and > E_NOTICE (and possibly also E_DEPRECATED) in a production environment - > you may still want to log such errors. As long as display_errors is > off, it's not a problem except for the performance hit which should be > low