Re: PHP 5.2
Reply #1 –
json_encode might be minimum PHP 5.2 but as WordPress discovered to their horror, it's not actually enabled by default in a surprising number of hosts even on 5.2+... They had to release a patch because of how many systems refused to run WP properly after that.
So if you're bumping to 5.2 just for json_encode, it's not really enough of a reason, because you're still going to need a fallback anyway for those hosts idiotic enough to disable it.
Are there any other reasons you want to bump to 5.2 for? See, were this discussion over bumping to 5.3, there are legitimate improvements in the core OO model - late static binding - that would likely be useful to you in your quest to refactor SMF into an Elk-OO world. But 5.2? I can't think of a single reason other than json_encode to bump for, and even then...
Related question: are you still using the ISO/UTF-8 split? json_encode no likey ISO-anything.
Re: PHP 5.2
Reply #5 –
I think we decided 5.2 is not worth at the moment.
Re: PHP 5.2
Reply #6 –
Yeah .. I think it was more of a 5.2 is a meh, so we either stay 5.1 and the next move is 5.3 (or .4?)
Re: PHP 5.2
Reply #7 –
5.2 has a lot of cool additions I use in Wedge. Mostly extra params to useful functions. I'd never go back to 5.1. As for 5.3 I'd rather wait for 5.4 and its [] definitions. Although, anonymous functions, way to go... I take that back, eheh.