| Type | Note | Status | dismissed | Date | 22-Jun-2009 15:05 |
|---|---|---|---|---|---|
| Version | alpha 58 | Category | n/a | Submitted by | meijeru |
| Platform | All | Severity | not a bug | Priority | normal |
| Summary | time-zone in dates has no limitations |
|---|---|
| Description | a valid time-zone in a DATE! value must be an integer multiple of 30 minutes (positive or negative); no further restrictions appear to apply, although -12:00 to +12:00 would seem sensible |
| Example code |
| Assigned to | n/a | Fixed in | - | Last Update | 23-Jun-2009 22:24 |
|---|
| Comments | |
|---|---|
|
(0001019)
Carl 22-Jun-2009 22:09 |
We usually don't restrict values in that way, as long as the effect is not in error. For example, you can write 0:120 for 2 hours, and REBOL will do what is expected. If the user wants to take advantage of the built-in modulo for zones, it seems reasonable not to restrict it.
|
|
(0001029)
BrianH 23-Jun-2009 14:08 |
Plus, those restrictions wouldn't work: There are time zones on the :15 mark, and greater than +12. Any set of rules we do would likely be subject to change in the future, without any notification to us. It's best to just not restrict. |
|
(0001035)
meijeru 23-Jun-2009 22:24 |
Try setting the /zone component of a date to 0:15 -- it won't work, R3 DOES have a restriction to half hours, I checked. Shall I raise a ticket to get rid of this restriction or will you do it? |
| Date | User | Field | Action | Change |
|---|---|---|---|---|
| 23-Jun-2009 22:24 | meijeru | Comment : 0001035 | Added | - |
| 23-Jun-2009 14:08 | BrianH | Comment : 0001029 | Added | - |
| 22-Jun-2009 22:09 | carl | Severity | Modified | trivial => not a bug |
| 22-Jun-2009 22:09 | carl | Status | Modified | reviewed => dismissed |
| 22-Jun-2009 22:09 | carl | Comment : 0001019 | Added | - |
| 22-Jun-2009 22:06 | carl | Severity | Modified | minor => trivial |
| 22-Jun-2009 22:06 | carl | Status | Modified | submitted => reviewed |
| 22-Jun-2009 15:05 | meijeru | Ticket | Added | - |