>Surely we can put some thought behind the issue so that we can
>achieve any new desired results without removing support or
>performance for older JDks?
I have no intent on acting on this unilaterally. I just
wanted to record a reminder somewhere, although the reminder makes
an incorrect mention of CharStringPointer. My personal bias is
against reintroducing stream matching, based on reasons well documented
in the ACM paper, but now that every other package out there has caught
up with what used to be a unique/distinguishing feature of OROMatcher,
we might lose users, so the issue will need to be studied (run Perl5Matcher
thgouh a profiler, etc.). I wouldn't put it at the to of the priority
list though, which is why I jotted down a reminder.
>I'm sure we can do it in an eloquent manner as well.
Well, you have a lot more confidence than I do :)
daniel
