Re: [racket-dev] `regexp-explode' etc + poll

2012-03-13 Thread Eli Barzilay
(I should have mentioned that it's not exactly the same...) A few minutes ago, Matthew Flatt wrote: > I'm sorry that I missed this before, but I have a couple of minor > suggestions: > > At Tue, 13 Mar 2012 10:57:51 -0400, Eli Barzilay wrote: > > On January 1st, Eli Barzilay wrote: > > > > > >

Re: [racket-dev] `regexp-explode' etc + poll

2012-03-13 Thread Matthew Flatt
I'm sorry that I missed this before, but I have a couple of minor suggestions: At Tue, 13 Mar 2012 10:57:51 -0400, Eli Barzilay wrote: > On January 1st, Eli Barzilay wrote: > > I've implemented a new `regexp-explode' function. It accepts the same > > arguments as `regexp-match*' and `regexp-split

Re: [racket-dev] `regexp-explode' etc + poll

2012-03-13 Thread Eli Barzilay
This is now pushed: `regexp-match*' has `#:match-select' and `#:gap-select' keyword arguments; and `regexp-match-positions*' and `regexp-match-peek-positions*' have `#:match-select'. On January 1st, Eli Barzilay wrote: > I've implemented a new `regexp-explode' function. It accepts the same > arg

[racket-dev] `regexp-explode' etc + poll

2012-01-01 Thread Eli Barzilay
I've implemented a new `regexp-explode' function. It accepts the same arguments as `regexp-match*' and `regexp-split', but with two additional keyword arguments: * #:select-match If this is #t (the default) then the result includes the lists of results from the sub-matches. It can als