[NaCl SDK] nacl_io: Fix bug in Path::Range introduced in recent change.

[NaCl SDK] nacl_io: Fix bug in Path::Range introduced in recent change.

Path("foo/bar") has 2 components "foo" and "bar". It is legal when calling
Path::Range to access an invalid component (e.g. Path("foo/bar").Range(2, 2).
In this case, the previous STL-based implementation would return "", but my
non-STL implementation was incorrectly returning "foo/bar".

BUG=none
R=sbc@chromium.org

Committed: https://crrev.com/def60c001d10a9d70b7b8b4d8f8143a88bad81f5
Cr-Commit-Position: refs/heads/master@{#322035}

[Sam Clegg, 2015-03-23 20:32:34]

Are other value allowed that are completely outside the range.  (e.g. 99, 100) ?

lgtm

[binji, 2015-03-23 20:41:48]

On 2015/03/23 20:32:34, Sam Clegg wrote:
> Are other value allowed that are completely outside the range.  (e.g. 99, 100)
?

Looks like it. I added some tests for that.

> 
> lgtm

[binji, 2015-03-24 18:00:37]

The CQ bit was checked by binji@chromium.org

[binji, 2015-03-24 18:00:38]

The patchset sent to the CQ was uploaded after l-g-t-m from sbc@chromium.org
Link to the patchset: https://codereview.chromium.org/1018393007/#ps40001
(title: "add additional tests for values completely outside the range")

[commit-bot: I haz the power, 2015-03-24 18:01:16]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1018393007/40001

[commit-bot: I haz the power, 2015-03-24 18:43:39]

Committed patchset #3 (id:40001)

[commit-bot: I haz the power, 2015-03-24 18:44:42]

Patchset 3 (id:??) landed as
https://crrev.com/def60c001d10a9d70b7b8b4d8f8143a88bad81f5
Cr-Commit-Position: refs/heads/master@{#322035}