Bug 39473

GemStone/S 64 Bit

2.3, 2.2.5.4, 2.2.5.3, 2.2.5.2, 2.2.5.1, 2.2.5, 2.2.4, 2.2.3, 2.2.2, 2.2.x, 2.1.4, 2.1.x, 2.0.4, 2.0.x, 1.2.5, 1.2.4, 1.1.14, 1.x

All

2.3.1

findString:startingAt: incorrect for empty string argument

When CharacterCollection >> findString:startingAt: is called with a search argument that is an empty string '', it returns 1, rather than 0.

Other Smalltalk implementations of findString:startingAt:, and GemStone's method SequenableCollection >> indexOfSubCollection:startingAt: return 0 for this case.


Last updated: 4/10/09