Thanks for the precious info @Araq. > Well in the end you have to benchmark but strscans doesn't do anything that > would be "obviously slow". It should be just fine.
Then I'll go for it, for I like its syntax. My app being presently an alpha prototype, it should be fine to start with this library. Once it's stable I might try some benchmark comparison with PCRE and other regex libraries (including Oniguruma, which would be nice to create a wrapper for) and see if there is space for speed improvement. But right now I just want to switch language and keep the code simple. Also, I like the **strscans** approach. > nre is a controversial library and was scheduled for deprecation I see. Although I read about some of the bugs (which I though were solved) it looked interesting, its approach seemed simple and flexible. > There is also > [https://github.com/nitely/nim-regex](https://github.com/nitely/nim-regex) > which is a pure Nim implementation without the PCRE dependency. Ah, I didn't realize that, I thought it relied on the **pcre** wrapper. Interesting, I'll have a look at it thenPCRE.
