Type | Bug | Status | tested | Date | 14-Dec-2009 20:09 |
---|---|---|---|---|---|
Version | alpha 95 | Category | Error Handling | Submitted by | meijeru |
Platform | All | Severity | minor | Priority | normal |
Summary | Error messages when setting various date components are confusing |
---|---|
Description | There are two components of DATE! values that cannot be set: YEARDAY or JULIAN (ordinal 8) and UTC (ordinal 9). The other components must be set to appropriate values. The error messages obtained when making various mistakes are not always enlightening. |
Example code |
>> d: now >> d/yearday: 330 ** Script error: cannot access yearday in path d/yearday: ;; "access" is strange, "set" could be used like for utc below >> d/utc: 25-Dec-2009 ** Script error: cannot set utc in path d/utc: >> d/time: 12.34 ** Script error: cannot set time in path d/time: ;; here, "set" is strange -- /time can be set, but not to a decimal value |
Assigned to | n/a | Fixed in | alpha 97 | Last Update | 8-Feb-2010 01:52 |
---|
Comments | |
---|---|
(0001976)
Carl 6-Feb-2010 17:04 |
Now like this:
>> n/yearday: 330 ** Script error: cannot set yearday in path n/yearday: >> n/date: 123 ** Script error: cannot set date field to integer! datatype Note that we now allow time to be set to integer or decimal time value in seconds. |
Date | User | Field | Action | Change |
---|---|---|---|---|
8-Feb-2010 01:52 | BrianH | Status | Modified | built => tested |
6-Feb-2010 17:04 | Carl | Fixedin | Modified | => alpha 97 |
6-Feb-2010 17:04 | Carl | Status | Modified | reviewed => built |
6-Feb-2010 17:04 | Carl | Comment : 0001976 | Added | - |
23-Dec-2009 13:57 | carl | Code | Modified | - |
23-Dec-2009 13:57 | carl | Status | Modified | submitted => reviewed |
14-Dec-2009 20:09 | meijeru | Ticket | Added | - |