>From the Smarty forum (I'm not a user): http://www.phpinsider.com/smarty-forum/viewtopic.php?t=5749&postdays=0&postorder=asc&start=15
"A related topic was raised on the php-internals list recently and arguably, the consensus there was that these notices are the proper means of communicating deprecations of PHP4 features -- but only when E_STRICT is enabled. As a further result of that discussion php-ini- recommended no longer suggests E_STRICT for production environments with the implication being that E_STRICT is to be used as a developer tool." Nate: "would you consider it acceptable to break strict mode in a few key (forward-compatible) areas if it meant significantly simplifying code and/or eliminating extra work you would otherwise have to do? " The raison d'etre of Cake is to do just that (simplify, reduce workload), Nate. I'm edging towards the spirit-of-the-law camp with the proviso that a keen weather eye is kept to avoid a massive sidestep in the future. But how important is backwards compatibility? How often do we update the version of Cake on a delivered/completed project? Sure a lot of components may need to be rewritten from time to time, but that is within the lifecycle of a component anyway. NOT STRICT! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
