-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
update #2
base: master
Are you sure you want to change the base?
update #2
Conversation
This all looks good to me, the only problem is that you clearly care much about this software than I do. How about I just hand you over the PAUSE rights to it and you upload it yourself? Just tell me your PAUSE id and I'll hand it over to you. I think it also makes sense that rather than merging this pull request you just alter the distro to point to your repository as the canonical one (I can't remember if it points to it, i.e. whether I was using dzil at the time). |
That's fine for me, my PAUSE id is 'SYP'. |
From PAUSE:
It used to be on the CPAN but I removed it since it broke with >5.10. I still had the maintainership of it though, until now. |
FYI: https://metacpan.org/module/re::engine::TRE |
Sure, looks fine. One thing I'd suggest for future development is to take advantage of the other TRE features (like edit distance) through storing info in %^H which you'd compile into the regexes, e.g.:
|
Yes, fuzzy matching is exactly my primary interest in libtre :) |
Also, FWIW it can sometimes be really hard to cast whatever regex interface you're trying to wrap into the re::engine structure, sometimes it can be really nice, like with:
But other times it can be easier to have an interface like:
Or something, especially if the regex engine you have can take parameters for a complied regex at match time, the re::engine interface can only pass you parameters at regex compile time. |
drop PWP::Encoding dependency
Changes:
At least, it compiles & passes tests :)