I'm ready to commit the next version of XOOPS Cube. Before commitment, we have to decide a (CVS) module name. I think that we should have two modules for each PHPs.
/XCube_PHP4
/XCube_PHP5
/Package_Legacy
XOOPS Cube is enough small, so we can manage two versions in the same time. I'm writing in PHP4. Next year, we may migrate it to PHP5 in another (CVS) module repository. That's good idea that I can keep two editions.
What do you think?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If you want to separate, I think their names might be /XCube and /XCube_PHP5.
Under /XCube programs should run under both PHP4 and PHP5 environment, like XCube Core 0.9
and /XCube_PHP5 programs run under only PHP5 environment.
But I think PHP5 trial may be developed under a special branch under /XCube.
And near future when PHP4 environment would become a minority,
PHP5 branch should be merged into HEAD.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If we will stop PHP4 version in the future, I agree nobunobu's idea. On the other hand, we may take care to the existence of PHP6. Anyway, my latest Core is PHP4 and has big difference from the current version. We may have to use a branch of one module "XCube_Core", even if we have another module "XCube_PHPx".
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
With PHP6 coming out, not sure that something 'php4' will be representative of the inovative core.
Nobunobu's idea seems good to keep /XCube for PHP4 and PHP5 and create /XCube_PHP5
But soon or later there will be discussion about PHP5 and PHP6
Meanwhile Core should go PHP5 definitively!
PHP4, PHP5 and PHP6 have big difference. So it's good idea we separates CVS modules for each version. I decided to use XCube_PHP4 for the current version. If we will get a time to have to rename it, we will do it.
And, I will make a branch "minahito_sandbox" in the meantime.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
> I decided to use XCube_PHP4 for the current version.
Why you consists the PHP4?
I think This name will cause confusion.
And many people will be worried like
"XCube_PHP4 code won't be executed under PHP5?"
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm ready to commit the next version of XOOPS Cube. Before commitment, we have to decide a (CVS) module name. I think that we should have two modules for each PHPs.
/XCube_PHP4
/XCube_PHP5
/Package_Legacy
XOOPS Cube is enough small, so we can manage two versions in the same time. I'm writing in PHP4. Next year, we may migrate it to PHP5 in another (CVS) module repository. That's good idea that I can keep two editions.
What do you think?
I agree to it.
I think that it should write XOOPS Cube with PHP5 in the future.
How do you think relations of PHP version and XCube version?
I think that the following relations are good.
"/XCube_PHP4" is XCube0.9 , 0.10 , 0.1x .
"/XCube_PHP5" is Xcube1.0 , 1.x .
How do you think?
If you want to separate, I think their names might be /XCube and /XCube_PHP5.
Under /XCube programs should run under both PHP4 and PHP5 environment, like XCube Core 0.9
and /XCube_PHP5 programs run under only PHP5 environment.
But I think PHP5 trial may be developed under a special branch under /XCube.
And near future when PHP4 environment would become a minority,
PHP5 branch should be merged into HEAD.
If we will stop PHP4 version in the future, I agree nobunobu's idea. On the other hand, we may take care to the existence of PHP6. Anyway, my latest Core is PHP4 and has big difference from the current version. We may have to use a branch of one module "XCube_Core", even if we have another module "XCube_PHPx".
With PHP6 coming out, not sure that something 'php4' will be representative of the inovative core.
Nobunobu's idea seems good to keep /XCube for PHP4 and PHP5 and create /XCube_PHP5
But soon or later there will be discussion about PHP5 and PHP6
Meanwhile Core should go PHP5 definitively!
http://www.gophp5.org/
Last summer i also post about PHP6 and what was planned to change
(affecting most xoops2 core and modules)
Suppresion:
- register globals
- magic quotes
- safe mode
- function by reference
- mode of compatibility with zend.ze1
- super-globals $HTTP_*_VARS
Changes:
+ PHP core supports UNICODE
Functions and variables, chains, regular, etc.
Extensions :
+ Fileinfo
+ XMLReader
+ XMLWriter
+ ereg moved to library PECL
+ PCRE regular expressions activated
+ Addjout int64 (by default int still 32 bits)
Since that, we can read more here:
http://wiki.pooteeweet.org/PhP60
PHP4, PHP5 and PHP6 have big difference. So it's good idea we separates CVS modules for each version. I decided to use XCube_PHP4 for the current version. If we will get a time to have to rename it, we will do it.
And, I will make a branch "minahito_sandbox" in the meantime.
> I decided to use XCube_PHP4 for the current version.
Why you consists the PHP4?
I think This name will cause confusion.
And many people will be worried like
"XCube_PHP4 code won't be executed under PHP5?"
I mistook English.
- Why you consists the PHP4?
+ Why are you insistent on using a name "PHP4"