Howdy, Joel:
> Notice that now the result block has only TWO elements!
> Since the first test (the thru {.^/} part) can succeed by
> grabbing text all the way to the end of the SECOND
> paragraph, >it does so, putting the first two paragraphs
> into the first >output string. I assumed that this is NOT
> what you wanted, >but rather you wanted to copy through
> either {.^/} or {."^} >WHICHEVER COMES NEXT. (Natural
> language text munching is a >real pain, speaking from
> personal experience! ;-)
Sure. In the interests of advancing its popularity, I
offered up a simplistic example of PARSE. :-)
Paragraphs can end in a variety of punctuation ("!?.-;:),
with different quantities (as Russ pointed out), no?
-jeff
- [REBOL] Bug report (was: parse or) Re: joel . neely
- [REBOL] parse or Re:(3) rryost
- [REBOL] parse or Re:(2) RChristiansen
- [REBOL] parse or Re:(3) jeff
- [REBOL] parse or Re:(4) rryost
- [REBOL] parse or Re:(4) joel . neely
- [REBOL] parse or Re:(5) RChristiansen
- [REBOL] parse or Re:(6) joel . neely
- [REBOL] parse or Re:(7) RChristiansen
- [REBOL] parse or Re:(8) joel . neely
- [REBOL] parse or Re:(6) jeff
- [REBOL] parse or Re:(6) joel . neely
- [REBOL] parse or Re:(7) brett
- [REBOL] parse or Re:(3) rryost
- [REBOL] parse or Re:(4) norsepower
- [REBOL] parse or Re:(5) rryost
- [REBOL] parse or Re:(6) joel . neely
- [REBOL] parse or Re:(7) norsepower
- [REBOL] parse or Re:(7) rryost
- [REBOL] parse or Re:(8) joel . neely
- [REBOL] parse or Re:(6) norsepower
