| Type | Bug | Status | tested | Date | 23-Jul-2010 17:03 |
|---|---|---|---|---|---|
| Version | alpha 99 | Category | Native | Submitted by | meijeru |
| Platform | All | Severity | minor | Priority | normal |
| Summary | NOW/DATE still (or again) has /TIME component set |
|---|---|
| Description |
In #994, Carl stated: The behaviour is now defined as >> d: now/date == 27-Jun-2009 >> d/time == none >> d/zone == none The bug has apparently come back: see code. |
| Example code |
>> d: make date! [23 7 2010] == 23-Jul-2010 >> d/time == none >> d: now/date == 23-Jul-2010 >> d/time == 0:00 >> d: d/date == 23-Jul-2010 >> d/time == none |
| Assigned to | n/a | Fixed in | alpha 104 | Last Update | 23-Sep-2010 10:01 |
|---|
| Comments | |
|---|---|
|
(0002473)
Carl 24-Aug-2010 23:52 |
The problem was that the ZONE was still kept, but what is a ZONE if no time is specified? Thus, this is a bug, and it has been fixed. |
| Date | User | Field | Action | Change |
|---|---|---|---|---|
| 23-Sep-2010 10:01 | BrianH | Status | Modified | built => tested |
| 24-Aug-2010 23:52 | carl | Comment : 0002473 | Added | - |
| 24-Aug-2010 23:51 | carl | Fixedin | Modified | => alpha 104 |
| 24-Aug-2010 23:51 | carl | Status | Modified | reviewed => built |
| 31-Jul-2010 23:30 | BrianH | Description | Modified | - |
| 31-Jul-2010 23:30 | BrianH | Code | Modified | - |
| 31-Jul-2010 23:30 | BrianH | Status | Modified | submitted => reviewed |
| 23-Jul-2010 17:03 | meijeru | Ticket | Added | - |