Indeed, but JavaScript and awk also have first class loop accessible
variables to make up for the limitations in their respective regex parsers.
About linear time. Are you saying it is slower than linear time to compile
a group captured regex or that it is impossible to efficiently reuse the
compiled object in the body of a complementary UDF in the same statement?
All sorts of ad hoc parsing functions are possible and I use quite a few in
my code. However, as I pointed out in the carefully worked test case
linked below, there is presently no reliable way to share that parsed state
among functions with different names, in different columns, or of column
valued objects using the thread safe auxdata API. Those improvements in
the auxdata API alone would be valuable without the regexp capture
capability.
https://www.mail-archive.com/sqlite-users@mailinglists.sqlite.org/msg107041.html
BTW, it is not only my possibly eccentric boutique code that is running
into this problem:
https://www.mail-archive.com/sqlite-users@mailinglists.sqlite.org/msg107045.html
On Mon, Jan 1, 2018 at 10:44 AM, Richard Hipp wrote:
> On 1/1/18, petern wrote:
> > Richard. Please consider adding capturing groups during your upgrade of
> > the regexp.c matching capability.
>
> I did consider that. It seems hard to do in linear time. I also
> notice that neither JavaScript nor AWK support that capability.
>
> --
> D. Richard Hipp
> d...@sqlite.org
> ___
> sqlite-users mailing list
> sqlite-users@mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users