GoPHP5

Is impressCMS going to follow the GoPHP5 initiative???

http://www.gophp5.org

We should register?

IMHO, yes. Given that PHP4 is EOL, I think we should only focus on PHP5 compatibility.

I think this would be a very sensible move.

Something to put on the roadmap for sure.

If I recall correctly, the XOOPS core team tentatively decided to retain PHP4 compatibility for 2.0, 2.2 and 2.3/2.4 (2.0 + 2.2 merge), and that 2.5/2.6 would be the first version to require PHP5.

If we abandon PHP4 compatibility too soon, XOOPS users whose servers don't have PHP5 will be forced to stay with XOOPS rather than upgrading to ImpressCMS.

Should we should keep ImpressCMS compatible with PHP4 at least until we gain a "critical mass" of XOOPS users? I suppose it would be helpful to know how many people are still using PHP4.

Quote:

Perhaps an addendum to the roadmap for iCMS 1.0?

Similar to our discussion about 'xoops' in the code and output, I think we should follow the same philosophy - for compatibility, we leave existing code at PHP4. For new functionality, use PHP5

i agree skenow ... another point is that PHP4 lose official PHP support at the begin of the 2008 ... soo ... i think most hosting server will migrate forced... i dont see the point or supporting a non supported PHP Version

I'm with Dave, although I now know my servers support php5, there are still some hosts which don't and maybe won't for a while.

I think at least we could phase it out slowly and include it within a road map, rather than going whole hog now.

From what I understand, there is very little code which is not php5 compatible.

I'm guessing that most is module code?

Quote:

The issue is not PHP5-compatibility. The issue is when to abandon PHP4-compatibility.

I understand what you mean now Dave ... I was getting a little confused.

My vote : from now all, in all new code we write, we can use all the power of PHP5 without caring about PHP 4 compatibility.

Let's believe in our conviction. We all know PHP 4 is dead. So why bother.

Does that mean that new code in the first release of ImpressCMS may use PHP5-only features, which will make it incompatible with PHP4?

Maybe you are right... we should give support till 2008-08-08 wich is going to be the date of support ending from PHP...

My vote we go in using PHP 5 features now if it can make a difference.

But I can live with keeping PHP 4 compatibility until 2008-08-01.

It's up to this team to decide.

Personally I think we should keep the support going at least until 2008-08-08, surely by that time all hosts would of gone php5 or they will be loosing mass quantities of customers.

I would agree with maintaining compatibility with PHP4 until 2008-08-08. From what I've seen, it's not so difficult to do. Yes, it would be nice to have new features, but as pointed out, a lot of hosts are slow to upgrade.

I also prefer to use only PHP5 as Marc stated, but i would suggeste leave the first release support PHP4 and for the next major releases focus on PHP5 i have on my servers since months only PHP5 ;)

Why not split it up?

I mean this:

the codes that build on just the current xoops 2.0.x code will have its php4 compatbility, but
the *real* impress codes (the ones that will take it away from xoops) will be php5 native.

This is what Skalpa wanted to do with XOOPS anyway: work towards a php5 native codebase. Basically, you'd have till 8.8.08 to create a superduper new php5 only system that will make the current patching xoops work obsolete.

Herko

and what about mysql5 too?

but in particular mysql5 has some functions that could be utilised (if used correctly, and that input is validated and sanitized before hand)

especially as mysql5 is able to use multiple queries in 1 session whereas mysql4 can only accept single queries at 1 time.. it could speed things up if multiple query ability is introduced.

I see someone has worked on adding mysqli support too, so even with mysqli, multiple queries can be utilised by the function mysqli_multi_query() instead of mysqli_query().

certainly something to look at tho either way.