Re: GoPHP5

Mark Rogers <[email protected]> Fri, 06 Jul 2007 15:56:13 +0100
Newsgroups gmane.comp.php.smarty.devel
Organization More Solutions Ltd
Message-ID <[email protected]>
Sebastian Mendel wrote:
> at least for phpMyAdmin, what i was talking about in last post, this is not
> correct, as we not just anymore "take PHP<5.2 compatibility into account"
> but actively remove code that was used to implement/simulate behavior from
> PHP 5 and introduce OO functionality not supported by PHP 4
>   

Oh OK, I misread it. Even so I agree that removing PHP4 workarounds is a
good thing if there's a reason to do so (eg if PHP5 gives a better
performing way to do something or a way which is otherwise more robust).
Changing something that works for something that "should" be the same,
for no other reason that to break PHP4 compatibility, would seem like a
bad idea, as (unlike phpMyAdmin) Smarty does need to retain
compatibility with templates written previously (whether for older
versions or not, perhaps except where that compatibility is broken
purely because of a PHP version issue). Ie if I have a site which works
now on PHP5 and after the Smarty upgrade to the PHP5 version no longer
works because something obscure is now done differently, then that *is*
an issue, and changing things that work just to break PHP4 compatibility
would be prone to breaking things in this way.

-- 
Mark Rogers // More Solutions Ltd (Peterborough Office) // 0845 45 89 555
Registered in England (0456 0902) at 13 Clarke Rd, Milton Keynes, MK1 1LG 

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