Skip to content

Conversation

@firewave
Copy link
Collaborator

No description provided.

@firewave
Copy link
Collaborator Author

Might make sense to be able to specify the type via a rule file as well. That would also allow to mix and match the engines depending on required performance/features. Or maybe even only allow it via a file so to not add another CLI option and not having to deal with the left-to-right issues.

@sonarqubecloud
Copy link

@firewave
Copy link
Collaborator Author

This will only add the additional engine. I will also do some performance tests.

The follow-up steps are:

  • implement PCRE2 as an additional engine and make it optional via a new build flag
  • make std::regex the default and deprecate HAVE_RULES and PCRE1 so the feature works without any build dependencies
  • remove HAVE_RULES and PCRE1 shortly after (most distros have already dropped the dependency since the library has long been EOL)

@danmar
Copy link
Owner

danmar commented Oct 17, 2025

thanks for working on this. 👍

@firewave
Copy link
Collaborator Author

Might make sense to be able to specify the type via a rule file as well. That would also allow to mix and match the engines depending on required performance/features. Or maybe even only allow it via a file so to not add another CLI option and not having to deal with the left-to-right issues.

@danmar any comment on this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants