Support for PCRE2

[elfring]

How are the chances to support the current version (≧ “10.22”) of this programming interface for Perl-compatible regular expressions?

[mmottl]

The current PCRE-bindings satisfy my needs. If you need further functionality, feel free to submit pull requests, but please make sure that the API stays backward compatible and that the library can be compiled with older PCRE versions.

[elfring]

Do you get any special software development concerns from introducing the usage of the prefix “pcre2” into the current source files?

[mmottl]

Yes, not everybody may have pcre2, there may be portability issues, etc. It's probably going to take a significant effort to support the new API. Not sure it's worth the effort.

[elfring]

• Does this kind of feedback mean that you would prefer to maintain several versions of your software library in parallel on topic branches?
• Which branch organisation will be selected?

[mmottl]

No, by this I meant that people use pcre on a large variety of platforms, some of which may not even have pcre2. If you want to make sure that they can still use the older pcre installation, you would have to add potentially non-trivial autoconfiguration code. You might also consider writing completely separate OCaml bindings for Pcre2 and leverage already existing OCaml code from the current bindings for that purpose. It might make some problems (e.g. backward compatibility) easier to solve.

[elfring]

• How many software maintenance will be needed in parallel for the discussed versions?
• Would you like to choose any further topic and development branches?

[mmottl]

It would probably be best to just start a fresh tree and copy as much as possible from the previous version. The amount of maintenance required will typically depend on the quality of the bindings (bugs) and how likely there will be portability issues.

[elfring]

I suggest to switch to the PCRE2 programming interface at a specific version of your OCaml library.
Which version number will be appropriate then?

[mmottl]

The latest release or even head of the master branch. This should make it easiest to adopt future changes.

[elfring]

Will other branch names be a bit safer for corresponding patch merges?

[mmottl]

There are currently no other branches. Feature branches are typically merged and eventually deleted.

[elfring]

I suggest to introduce a clearer separation between development branches.

[elfring]

How do you think about to use any software improvements which are mentioned in the PCRE change log?

[mmottl]

If I had a personal need for a feature, I would implement it, but the current PCRE API satisfies my needs. Feel free to contribute any patches that support unimplemented features.