-
Notifications
You must be signed in to change notification settings - Fork 9.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update C/C++ API (6.0.0) #4336
Comments
Should be drop the C API in release 6? Or later? Who is still using it? |
+1 for dropping. There are some users most likely, but they can take |
https://github.com/nguyenq/tess4j/ Most likely it is used by many companies internally. |
I know from other software that it's possible to mark API functions in the header files as "deprecated", so anybody who uses them in a build process gets a warning message. So we might start adding such deprecation markers and then hopefully get more feedback. |
Previous talk about the C API: |
I still miss reasonable explanation of benefit for removing feature (C-API). |
And they should maintain it. We can mark capi as deprecated like @stweil said or unmaintained. |
We can also move out C API (two files) into separate |
I agree with removal. It's undocumented and in my limited experience, a bit of minefield for memory corruption bugs. pytesseract, tesseract-rs and ocrmypdf (my project) all use Tesseract in a subprocess. pytesseract used to have C API bindings but removed them many years ago. To mark functions deprecated:
|
Do you have an objection to move the C API out of the main tesseract repo, to a new repo 'tesseract-capI' ? |
Would this be reasonable as long as we work with major version 5? |
It is better to create v5 branch and do some fixes into both v5 and master. And declare master as future 'v6' branch and do api changes here. |
Here we can discuss API changes which are incompatible and therefore postponed for a future release 6.
The text was updated successfully, but these errors were encountered: