|
Bugzilla – Full Text Bug Listing |
| Summary: | tointeger("blah") returns 0 | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Jiří Suchomel <jsuchome> |
| Component: | YaST2 | Assignee: | Klaus Kämpf <kkaempf> |
| Status: | RESOLVED FIXED | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Major | ||
| Priority: | P5 - None | ||
| Version: | Beta 4 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
Thats clearly a bug. nil should be returned. Will fix this after 10.0 later Could someone do it? The fix it not the problem. But how much existing code will break ? (we probably have to 'grep -r tointeger' across YaST ...) If this is the correct behaviour, I think it should be changed and we will see what relies on the incorrect one. Its even documented to return nil on illegal strings. Fixed in SVN, added testcase. |
tointeger("blah") returns 0 : should it? With this, tointeger cannot be used for checking if given string is convertible to integer.