Unless you are deleting thousands of files in a tight loop, the overhead involved won't make any difference for your application.
In general your application is throwing many errors, even "benign" E_STRICT or E_NOTICE you are already incurring a performance hit. On Mon, Oct 17, 2011 at 3:49 AM, Ferenc Kovacs <tyr...@gmail.com> wrote: > On Mon, Oct 17, 2011 at 8:54 AM, Stas Malyshev <smalys...@sugarcrm.com>wrote: > >> Hi! >> >> >> On 10/16/11 5:54 PM, Sebastian Bergmann wrote: >> >>> Such a performance regression sounds like an appropriate "punishment" to >>> me for deploying bad code ;-) >>> >> >> By bad code you mean not obsessively checking for stuff that is of no >> importance to them as programmers and is only required because language >> implementers decided to go B&D on their users? ;) >> >> I personally hate to see all these isset($foo['bar'])?$foo['bar']**:null. >> I think it's bad we make people do that. >> >> > and there are cases when you can't avoid triggering errors (like trying to > delete delete a while which can be deleted concurrently) so your only > option is to suppress them and handle the result based on the return value > of the statement. > > -- > Ferenc Kovács > @Tyr43l - http://tyrael.hu > -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
