Just after 3.2.0 was released, we merged a commit to avoid requiring -std=c++11:
https://git.dillo-browser.org/dillo/commit/?id=7a595afa37423b99f79efbbbb2241090cb56653a
We always needed one feature of C++11 which is macros with variable arguments, but most older compilers have support for it, so we can assume it is available and "claim" that we still support compilers with C++98 (i.e. GNU++98).
I would like to be sure that it won't cause problems downstream from new code that accidentally added a dependency on code that doesn't build on older compilers.
Would it be possible to test if the current dillo from git builds on the old compiler that was used to build 3.2.0 and didn't worked?
https://git.dillo-browser.org/dillo/
I could try to setup an old compiler myself if I know which one was used that failed.
Thanks!
@alarixnia
Just after 3.2.0 was released, we merged a commit to avoid requiring
-std=c++11:https://git.dillo-browser.org/dillo/commit/?id=7a595afa37423b99f79efbbbb2241090cb56653a
We always needed one feature of C++11 which is macros with variable arguments, but most older compilers have support for it, so we can assume it is available and "claim" that we still support compilers with C++98 (i.e. GNU++98).
I would like to be sure that it won't cause problems downstream from new code that accidentally added a dependency on code that doesn't build on older compilers.
Would it be possible to test if the current dillo from git builds on the old compiler that was used to build 3.2.0 and didn't worked?
https://git.dillo-browser.org/dillo/
I could try to setup an old compiler myself if I know which one was used that failed.
Thanks!
@alarixnia