Please remove ONIG_MAX_CAPTURE_NUM and ONIGERR_TOO_MANY_CAPTURES

[yurivict]

There is no need to assume that regular expressions are small and to limit something with the arbitrary number 32767.

[kkos]

The capture numbers are expressed in a bytecode as short int.

[yurivict]

Can this be expanded to 64 bit and this limit made consistent with the limit typedef?

[yurivict]

Is it typedef short int MemNumType;?

[k-takata]

I'm really curious about your usage.
What do you want to use such many capturing groups for?
Isn't it enough using non-capturing groups (?:foobar)?

[yurivict]

I use rather large regular expressions to find certain terms in texts. There are a lot of terms, lists can be arbitrarily large.

It works fine, except it hits this limit.

So I suggest you increase the limit, so that nobody has to hit it again. 16-bit vs. 32-bit field doesn't really save much performance-wise. Also please make the limit consistent with the data type.

[kkos]

I have updated develop branch.
NEW API: onig_set_capture_num_limit()
This is experimental and may put it back when my feeling changes.

Default capture number limit (32767) is not changed.
Call onig_set_capture_num_limit(0) to be unlimited.

[yurivict]

Thanks!