Details
-
Type:
New Feature
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: Zend_Version
-
Labels:None
Description
As some of the legacy projects I work on slowly adopt ZF, we also adopt some of ZF's conventions (naming, unit testing).
One thing I find common to all projects is tracking the current version. Sometimes I make a file version.text, but I like the way ZF handles it, with the Zend_Version class.
Would it make sense to let me extend that for use in my other projects (so I don't duplicate the compareVersion method?).
I'd suggest to remove the "final class" and convert it to late static binding, just in case.
Issue Links
| This issue is related to: | ||||
| ZF-10363 | newest Version from zend.com |
|
|
|
Since ZF 1.10 still supports PHP 5.2, late static binding isn't an option. Still an option for ZF2.
Could adjust the compare to
public static function compareVersion($version, $version2 = Zend_Version::VERSION)
to allow for BC, and still use the compare version for items outside of ZF.