Re: GoPHP5

just to clearify:

(for me) dropping support for PHP <= 5.2 does not mean rewriting the whole
code base, but more important making it more easier adopt new features
without taking care of old PHP versions -> this results in no completely new
code which will probably break old themes

btw. i think Smarty dev team is (currently) lacking man power to do a full
rewrite - and reducing supported PHP versions will also help the lacking man
power!


When developing on PHP 5 it would be very helpfull if major libraries like
Smarty would not flood the log with E_STRICT/NOTICEs when testing own
application


Just remembering: E_STRICT/NOTICE is used in PHP 5 to warn about possible
changes in PHP 6 too so it will help with transition to PHP 6 too.


Of course a Project like Smarty should still support a legacy version for
security fixes and possible minor bug fixes - but i think this is a low
effort task - at least for such a major app like Smarty is.


Some of the arguments mentioned here are exactly the reason for GoPHP5 ->
breaking the cycle! apps run in PHP 4 -> hosters provide PHP 4 -> lacy
developers do not fix there apps to run with PHP 5 -> hosters must provide
PHP 4 -> apps must run with PHP 4 -> hosters provide PHP 4 -> ... uh oh
thats wired!

The question is not how it helps YOUR project but how it HELPS THE
COMMUNITY! -> this resulting in helping your project!

Please read the reasons on gophp5.org carefully and linked discussions -> it
does not help discuss the same here already discussed 100 times on another
mailinglists (at least before reading through them).



btw. http://news.php.net/php.internals/30508


-- 
Sebastian Mendel

www.sebastianmendel.de

-- 
Smarty Development Mailing List (http://smarty.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php