I agree with Nekro!

I won't have a hosting that's not upgraded enough to handle PHP5, if there's a hosting/application that has outdated software and won't provide upgrades it means their bad.

[edit]adding more...

almost forgot..for developers PHP5 means ALOT...it gives them more and better functions to work with

btw, 2.0.16 by Skalpa runs perfectly on PHP5 so it's more a module issue than core issue I think.

Quote:

I totally agree with hervet with that... is more.... i am thinking how to implement it... (is not dificult at all) ...

Another thing to implement in that way is that if the module needs any other module installed before or any editor ... like dependeces... as for example the modules of XOOPS mexico...

I will present it as a feature request in sf.net

Nothing else to say :P

Quote:

Actually no. If you try to go from php 4 to php 6 you would be asking for trouble. As in any software each major version is a stepping stone to the next.

The problem is not to know if XOOPS must go to PHP5 but when.
Starting from the fact that the PHP team will stop the support for PHP4 it's an necessity.
It's the classical scenario for software development and evolution.

From a technical point of view,when a CMS has OO in its own name, it needs to adopt the true PHP OO version
(PHP5, PHP6) !



IMHO

Quote:

It would make sense to wait for php6 then, wouldn't it?

Sorry for my bad english (i speak morefluently php5 than english )

I used XOOPS 2.0.14, 2.0.15 and 2.0.16 on PHP5 without problem on a site for 1,5 years.
I'm using lot of module :
- Protector
- newcbb
- news
- smartsection
- wfdownload
- xcgallery
- weblinks
- liaise
- xhld
- polls
- xm memberstats
...
And all of them without problem from php5.
There is some php5 module on the site. It's some module i wrote, they work fine and they herit and use some core's class, without problem.

There is a great compatibility from php4 to php5. risk of bug is very small, on the moment i think just one thing to make have bug on a php4 code to turn on php5, and there is a little risk to found it, and after little risk to make a bug.

At to day, peoples are affraid to pass on php5... I don't know why?
they think provider don't put php5 on their server... Is not the reality. I look in France, lot of provider put php5 on their server. There is option to get it.
Php5 is more secure than php4 about security hole.

And for developper, is easiest to code on php5, you don't have to think about reference or value when you have a param for function. That is for a beginner.
For a object's developper, php5 offer lot of thing you can found on object's language. You can use design pattern and anything else. You can define interface, you can put private and public attribut or method (code security). etc...
what is the sense of the two O of xoops????

And you know what?
Php6 will be arrive next year...
If XOOPS rest on php4, i think is the death of xoops, because there is a compatibility between php4 to php5 yes, but there'll be not from php4 to php6...

Just an idea :
extend the $modversion array in xoops_version.php to include :

1/ The last date of the module's modification
2/ The Php versions supported
3/ The MySQL versions supported

In 6 months, every module without this is declared, de facto, unsupported (and too old)

But it suppose to have "something" in the XOOPS modules manager.
Something like : "inspect your modules"

Just an idea.

PS : For me it's not to the persons in charge of the repository to do the modules dev's job.

Quote:
That's exactly the problem. I don't know either. Neither does any XOOPS user except by the misery of trial and error.

I suggested some time ago that the repository should:

1) Be split into 'supported' and 'unsupported' modules.

2) Force developers to state exact system requirements.

3) Be searchable by system requirements.


If this became the case, I could tell you exactly how many modules work under PHP 5. PHP 5 users could download them, I could avoid them and everyone would be happy!

Peekay,

I'm not sure that modules who are not compatibles (I mean who does not runs with Php 5) are Pro AND safe ...
(and are they still supported ?)

With this kind of talk, XOOPS will be, one more time, the last, to profit of the last gift that technology can brings to us.



Dave,

It's not so hard to be compatible with Php 4 and 5 but that's not the point.
The point is to say "we are now using some functions or possibilities which you can only find in Php 5".