Raise C++ to C++17 for 5.0.0

[Egor Pugin]

Any objections?

Reasons:

- Today it's almost 2019 H2.

- C++20 approaching.

- Compilers are able to build C++17 for 2+ years already.

- 5.0.0 still won't be released tomorrow, but some time in the future.

Pros:

- Not oudated codebase .

- More cleanups.

- More possible internal impovements, std algorithms, maybe std fs.

- etc.

[Zdenko Podobny]

Yes, I have objections:

1. In recent days there was request to build teseract with VS2015 ;-) which is still common compiler in corporate environment. Also I was in contact with developers that wanted to speedup training with CUDA. When I tried to install CUDA on one of my linux computer, it was quite difficult as it requires specific compiler version (not recent ;-) ) etc...

2. We made first touch with c++17 and it is "just" causing troubles (e.g. [1] ) - problem is that some compilers report support for c++17 (e.g gcc), even they support it only partly... GCC's (which is IMO major compiler of linux distribution) declares that C++17 support is experimental[1]. Require tesseract users to upgrade gcc to the latest version is not wise (I tried it several years ago and it successfully broke my installation heavily, so decided not to touch gcc provided by distribution)

3. I made my try last week[3] enjoin c++17 directory_iterator, any I finished with dirent/opendir on linux. Also I remember there is/was code committed by Stefan, that it worked on linux, but not on windows&clang...

So IMO moving to C++17 is not user friendly move and we should focus more on fixing existing problem instead of inviting new...

[1] https://github.com/tesseract-ocr/tesseract/issues/2496  or  https://github.com/tesseract-ocr/tesseract/pull/2476  
[2] https://gcc.gnu.org/projects/cxx-status.html
[3]  https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/tesseract-ocr/E-LURyGiqUw/TZt-CZYLBQAJ

Zdenko

ne 23. 6. 2019 o 10:32 Egor Pugin <egor....@gmail.com> napísal(a):

--
You received this message because you are subscribed to the Google Groups "tesseract-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tesseract-de...@googlegroups.com.
To post to this group, send email to tesser...@googlegroups.com.
Visit this group at https://groups.google.com/group/tesseract-dev.
To view this discussion on the web visit https://groups.google.com/d/msgid/tesseract-dev/58cefda3-9f47-475c-8f51-33702a304076%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Egor Pugin]

I see. Ok, let's wait more.

On Sunday, June 23, 2019 at 8:45:49 PM UTC+3, Zdenko Podobný wrote:

Yes, I have objections:

1. In recent days there was request to build teseract with VS2015 ;-) which is still common compiler in corporate environment. Also I was in contact with developers that wanted to speedup training with CUDA. When I tried to install CUDA on one of my linux computer, it was quite difficult as it requires specific compiler version (not recent ;-) ) etc...

2. We made first touch with c++17 and it is "just" causing troubles (e.g. [1] ) - problem is that some compilers report support for c++17 (e.g gcc), even they support it only partly... GCC's (which is IMO major compiler of linux distribution) declares that C++17 support is experimental[1]. Require tesseract users to upgrade gcc to the latest version is not wise (I tried it several years ago and it successfully broke my installation heavily, so decided not to touch gcc provided by distribution)

3. I made my try last week[3] enjoin c++17 directory_iterator, any I finished with dirent/opendir on linux. Also I remember there is/was code committed by Stefan, that it worked on linux, but not on windows&clang...

So IMO moving to C++17 is not user friendly move and we should focus more on fixing existing problem instead of inviting new...

[1] https://github.com/tesseract-ocr/tesseract/issues/2496  or  https://github.com/tesseract-ocr/tesseract/pull/2476  
[2] https://gcc.gnu.org/projects/cxx-status.html
[3]  https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/tesseract-ocr/E-LURyGiqUw/TZt-CZYLBQAJ

Zdenko

ne 23. 6. 2019 o 10:32 Egor Pugin <egor...@gmail.com> napísal(a):

Any objections?

Reasons:

- Today it's almost 2019 H2.

- C++20 approaching.

- Compilers are able to build C++17 for 2+ years already.

- 5.0.0 still won't be released tomorrow, but some time in the future.

Pros:

- Not oudated codebase .

- More cleanups.

- More possible internal impovements, std algorithms, maybe std fs.

- etc.

--
You received this message because you are subscribed to the Google Groups "tesseract-dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email to tesser...@googlegroups.com.

[Zdenko Podobny]

Just to be clear: I am fan of implementing c++17 step by step (at least to see were are problems/ testing compiler support), just do not cut support for user that needs to use older version system.

Zdenko

ne 23. 6. 2019 o 21:50 Egor Pugin <egor....@gmail.com> napísal(a):

To unsubscribe from this group and stop receiving emails from it, send an email to tesseract-de...@googlegroups.com.

To post to this group, send email to tesser...@googlegroups.com.
Visit this group at https://groups.google.com/group/tesseract-dev.

To view this discussion on the web visit https://groups.google.com/d/msgid/tesseract-dev/d19396b6-aa1a-4690-aa36-38d419f3fa1d%40googlegroups.com.