Don't use string slices when processing RexExp replace.
authorsgjesse@chromium.org <sgjesse@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Wed, 28 Oct 2009 09:11:45 +0000 (09:11 +0000)
committersgjesse@chromium.org <sgjesse@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Wed, 28 Oct 2009 09:11:45 +0000 (09:11 +0000)
commitabbc6b9147e1e56ec182420ff18da02371fb7177
tree554ee37facce2ea0b92a0c4e7f9ca4c5536cb0ae
parent64e1d3205f09d4f713e01ef91aa390982876c65b
Don't use string slices when processing RexExp replace.

String slices from RegExp replace results is now encoded in either one or two smis. Substrings are not used any more.

If the existing one smi encoding cannot hold the start/length information two smis are used the first having the negative length and the second having the start.

This is in preparation for removing string slices.
Review URL: http://codereview.chromium.org/342015

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@3153 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
src/runtime.cc
src/string.js