note
Anonymous Monk
Well, you do not tell us <i>how huge</i> your "huge string" is. But, even so, in these modern times I find it very difficult to imagine how any plausible difference of approach would actually make a human-measurable difference, therefore worth losing any coding-sleep about. All that being said, yes, your existing approach could be regarded as "expensive," such that in a legitimate edge-case you could perhaps justify replacing it with a loop based on either the string-position function or the <tt>"/g"</tt> regex modifier. But this decision should be guided by ... "are you in <i>actual, measurable pain?"</i>
11108396
11108396
-10