Type | Bug | Status | reviewed | Date | 26-Apr-2009 19:10 |
---|---|---|---|---|---|
Version | alpha 49 | Category | Native | Submitted by | henrikmk |
Platform | All | Severity | minor | Priority | normal |
Summary | UNIQUE/SKIP is not working correctly |
---|---|
Description | It appears that when using /SKIP, only the first record is tested for uniqueness. |
Example code |
>> a: [1 2 3 4 5 6 1 2 3 4] == [1 2 3 4 5 6 1 2 3 4] >> unique/skip a 2 == [1 2 3 4 5 6 3 4] ; should be [1 2 3 4 5 6] >> a: [1 2 3 4 5 6 1 2 3 4 5 6] == [1 2 3 4 5 6 1 2 3 4 5 6] >> unique/skip a 2 == [1 2 3 4 5 6 3 4 5 6] ; should be [1 2 3 4 5 6] >> unique/skip a 3 == [1 2 3 4 5 6 4 5 6] ; should be [1 2 3 4 5 6] |
Assigned to | n/a | Fixed in | - | Last Update | 2-Mar-2013 08:15 |
---|
Comments | |
---|---|
(0002476)
henrikmk 25-Aug-2010 17:22 |
This bug appears also in R2, it seems:
http://www.rebol.net/cgi-bin/rambo.r?id=4018& |
(0003555)
BrianH 2-Mar-2013 08:15 |
This is a general problem with the functions which use /skip for dealing with series of fixed records. We're discussing the issue in #428. |
Date | User | Field | Action | Change |
---|---|---|---|---|
2-Mar-2013 08:15 | BrianH | Comment : 0003555 | Added | - |
25-Aug-2010 17:22 | henrikmk | Comment : 0002476 | Added | - |
14-Jul-2009 01:01 | BrianH | Category | Modified | Unspecified => Native |
14-Jul-2009 01:01 | BrianH | Code | Modified | - |
14-Jul-2009 01:01 | BrianH | Category | Modified | => Unspecified |
27-Apr-2009 01:59 | BrianH | Code | Modified | - |
27-Apr-2009 01:59 | BrianH | Status | Modified | submitted => reviewed |
26-Apr-2009 19:10 | henrikmk | Ticket | Added | - |