Type | Bug | Status | tested | Date | 8-May-2010 12:18 |
---|---|---|---|---|---|
Version | alpha 99 | Category | Datatype | Submitted by | meijeru |
Platform | All | Severity | minor | Priority | normal |
Summary | DATE! value with integer for timezone gives odd results |
---|---|
Description |
In #1411, it was stated that a time-zone of +200 is intended to mean +2:00. This example does work now (since which version I cannot tell). I tried it for all integer values (say i), and the result is: i > 1500 gives an error i <= 1500 gives a number of hours equal to (to-integer i / 100), and a number of minutes equal to 0, unless (15 = mod i 100), in which case the minutes are equal to 15. I do not think this was completely intended. I maintain my suggestion from #1411 to abolish this feature. |
Example code |
;; to see for yourself >> repeat i 1501 [print [i to-date join "1-Jan-2010/10:00+" i]] |
Assigned to | n/a | Fixed in | alpha 108 | Last Update | 20-Oct-2010 03:45 |
---|
Comments | |
---|---|
(0002515)
Carl 21-Sep-2010 21:36 |
Now supported. Improper minutes (> 59) do not generate an error, but will be added. |
Date | User | Field | Action | Change |
---|---|---|---|---|
20-Oct-2010 03:45 | BrianH | Status | Modified | built => tested |
21-Sep-2010 21:36 | carl | Fixedin | Modified | => alpha 108 |
21-Sep-2010 21:36 | carl | Status | Modified | reviewed => built |
21-Sep-2010 21:36 | carl | Comment : 0002515 | Added | - |
13-May-2010 15:40 | carl | Description | Modified | - |
13-May-2010 15:40 | carl | Code | Modified | - |
13-May-2010 15:40 | carl | Status | Modified | submitted => reviewed |
8-May-2010 12:18 | meijeru | Ticket | Added | - |