String Pick incompatible with block Pick

[Siskin-Bot]

Submitted by: Ladislav

pick string 0 and pick block 0 behave differently

>> pick at [1 2 3 4 5] 3 0
== 2

>> pick at "12345" 3 0
== none

---

^{Imported from: CureCode [ Version: alpha 54 Type: Bug Platform: All Category: Unspecified Reproduce: Always Fixed-in:alpha 55 ]
Imported from: metaeducation#857}

Comments:

Rebolbot commented on May 25, 2009:

Submitted by: BrianH

This is the same as bug #608.

---

Rebolbot commented on May 27, 2009:

Submitted by: Carl

Which behavior do you prefer?

---

Rebolbot commented on May 27, 2009:

Submitted by: Ladislav

the former:

>> pick at [1 2 3 4 5] 3 0
== 2

---

Rebolbot commented on Nov 23, 2010:

Submitted by: Ladislav

in the core-tests suite

---

Rebolbot added on Jan 12, 2016

---

Oldes commented on Jun 13, 2018:

I decided to prefer the old Rebol2 version which seems to be more logical when addressing from series' tail:

>> pick at [1 2 3 4 5] 3 0
== none

>> pick tail [1 2 3 4 5] -1
== 5

>> pick tail "12345" -1
== #"5"

Red is using the Rebol2 behaviour too.

---

Oldes added a commit to Oldes/Rebol3 that referenced this issue on Jun 13, 2018:
FEAT/FIX: Picking the right PICK

---

Oldes mentioned this pullrequest on Jun 13, 2018:
FEAT/FIX: Picking the right PICK

---

Hostilefork added a commit to metaeducation/ren-c that referenced this issue on Jun 14, 2018:
Restore Rebol2-era PICKing/PATHing of negative/zero indices

---

Hostilefork mentioned this pullrequest on Jun 14, 2018:
Restore Rebol2-era PICKing/PATHing of negative/zero indices

---