Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

Change to C++17?

(1/3) > >>

Miguel Gimenez:
There is an updated version of astyle library (3.6.18) that fixes some issues (see ticket 1643, but it uses the stupid C++17-only std::string_view and we currently are using C++11.

There is also some C++17-only code, like [fallthrough] in clangd_client, generating warnings.

Should we change to C++17?

LETARTARE:
Have you tried to compile the full version with C++17 (Win-xx, Linux-xx) ?
If so, what warnings have you obtained ?

LETARTARE:
Leap-15.6-64bits, wx-3.2.8;gtk3-u, gc-15.2
'r14003.cbp' ( no 'contrib' )
Here is the compilation log with 'C++17' :

Miguel Gimenez:

--- Quote ---Have you tried to compile the full version with C++17
--- End quote ---

I have not tried, developers must agree on the change beforehand. Changing the CBP is easy, the problem may come later from autotools.

Errors in Squirrel can be fixed, but it uses tricky memory accesses that may be a headache.

gd_on:
Just to inform you that with my CodeBlocks_Windows.workspace, and setting my global variable cb_build.cpp_std to gnu++20, codeblocks compiles correctly as far as I have tested. Of course, this does not cover all build methods.

Navigation

[0] Message Index

[#] Next page