Details
-
Type:
Bug
-
Status:
Resolved
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 1.9.7
-
Fix Version/s: 1.10.0
-
Component/s: Zend_Validate
-
Labels:None
Description
"The integers are formed by the natural numbers including 0 (0, 1, 2, 3, ...) together with the negatives of the non-zero natural numbers (−1, −2, −3, ...). Viewed as subset of the real numbers, they are numbers that can be written without a fractional or decimal component, and fall within the set {... −2, −1, 0, 1, 2, ...}. For example, 65, 7, and −756 are integers; 1.6 and 1½ are not integers."
http://en.wikipedia.org/wiki/Integer
Basically its just a naming issue but in some cases it can lead to confusion why floats are accepted by Zend_Validate_Int as an int does consist only of natural numbers. Maybe there is a special reason or i am confusing something big time?, but a more logic name would be Zend_Validate_Number.
require_once 'Zend/Validate/Int.php
$foo = new Zend_Validate_Int();
zend_debug::dump($foo->isValid(1));
zend_debug::dump($foo->isValid(1.2));
zend_debug::dump($foo->isValid('1,2'));
Activity
Hi Thomas, i found the culprit. The validator is dependent on the specified locale and i think that shouldnt be? 
Using following code will return true in all three cases:
<?php
date_default_timezone_set('Europe/Berlin');
setlocale(LC_ALL, 'de_DE.utf8');
require_once 'Zend/Debug.php';
require_once 'Zend/Validate/Int.php';
$foo = new Zend_Validate_Int();
zend_debug::dump($foo->isValid(1));
zend_debug::dump($foo->isValid(1.2));
zend_debug::dump($foo->isValid('1,2'));
Using following code will return true in all three cases:
<?php
date_default_timezone_set('Europe/Berlin');
setlocale(LC_ALL, 'de_DE.utf8');
require_once 'Zend/Debug.php';
require_once 'Zend/Validate/Int.php';
$foo = new Zend_Validate_Int();
zend_debug::dump($foo->isValid(1));
zend_debug::dump($foo->isValid(1.2));
zend_debug::dump($foo->isValid('1,2'));
When you say that this issue occurs with 1.9.7 then I also expect that you are using 1.9.7.
On the other hand, when I say that this issue is fixed with the next minor release (which is the upcoming 1.10) then I expect that you tested it with 1.10 when you say that the issue is still there.
Don't you think? 
Looking above at "Fix-Versions" you can see that it reads "1.10.0", which is the actual release.
7 months was the time between the fix and the next minor release. Some API changes and additional have been done. Therefor it was not possible to backport the changes to 1.9.x.
7 months was the time between the fix and the next minor release. Some API changes and additional have been done. Therefor it was not possible to backport the changes to 1.9.x.
Using your example on latest release I get:
1. true
2. false
3. false
In my eyes this is correct behaviour. I see no problems.