<br><div class="gmail_quote">On Mon, Dec 6, 2010 at 11:49 PM, Eli Barzilay <span dir="ltr"><<a href="mailto:eli@barzilay.org">eli@barzilay.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> <div class="im"><br> </div>Well, that would be an obvious issue... It might be possible to do<br> this if they're extended to get an output port too, something like:<br> <br> (regexp-replace* #rx"foo" inp "bar" outp)<br> <br> doing the same thing as the loop that I wrote.</blockquote><div><br></div><div>So sounds like it can be done then? This will be a nice addition and make the regexp lib interface more uniform when someone gets around to it. </div> <div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">> But since the string & bytes variants all generate new output, that<br> > will seem to be the same for input-port source anyways.<br> <br> </div>(I didn't follow that.)</blockquote><div><br></div><div>I just mean that (regexp-replace* #rx"foo" in "bar") can return bytes or string or an input-port, instead of having to take in an output-port, if we do not want to add a fourth param as you showed above. But I like what you have shown above as well.</div> <div><br></div><div>Thanks,</div><div>yc</div><div><br></div></div>