The last I heard on this was that 3.2 is scheduled for November 2015 - see viewtopic.php?f=14&t=2302466Frank Rizzo wrote:The question then is: When will 3.2 be released?
PHP 7 will be released after PHP 5 just like Windows 10 will be released after Windows 8.1.Lumpy Burgertushie wrote:now, what happened to php6 and all of its version updates ?
It was deprecated since PHP 5.5.0 already, which was released on 2013-06-20 - so why screaming now and not back then? Same question to the developers: why not adapting code since then?Frank Rizzo wrote:preg_replace with the /e modifier, which is deprecated in PHP7
It worked.AmigoJack wrote:It was deprecated since PHP 5.5.0 already, which was released on 2013-06-20 - so why screaming now and not back then? Same question to the developers: why not adapting code since then?Frank Rizzo wrote:preg_replace with the /e modifier, which is deprecated in PHP7
Then it's not deprecated in PHP 7 but instead it's not supported anymore - that's a major difference. Why don't you quote what really happens, i.e. a notice, a warning, an error...? Edit: ah, finally: a warning about a non support.Frank Rizzo wrote:the failure does not exsit in 5.5 or 5.6. Only in version 7 does phpbb break.
preg_replace()
is the only thing that needs to be done (which is rather trivial).A lot of of shared hosters won't. Reason? All those legacy software, which is also the reason why up to today PHP 4 still exists. How can one benefit from performance boost (of the master) if the (slave) software in question won't run at all anymore?Frank Rizzo wrote:a lot of individuals will
"Trivial" is a reference to "fixingAmigoJack wrote:Show me a (PHP 7) changelog and I can tell you if fixingpreg_replace()
is the only thing that needs to be done (which is rather trivial).
preg_replace()
", not "Show me a (PHP 7) changelog".This week there was a pull request added that will address this problem (for the built-in BBCodes, custom BBCodes require further work). The fix will be merged into "develop" - the branch that is expected to become 3.2 late this year.Frank Rizzo wrote:Does anyone want to try and find a solution to this? Or shall we just sit talking semantics and be non productive all day?
A_Jelly_Doughnut wrote:This week there was a pull request added that will address this problem (for the built-in BBCodes, custom BBCodes require further work). The fix will be merged into "develop" - the branch that is expected to become 3.2 late this year.Frank Rizzo wrote:Does anyone want to try and find a solution to this? Or shall we just sit talking semantics and be non productive all day?