| 7 | | and the (private) macro, `YAT_HAVE_CXX11__` is only `#defines`, if user `#defines` `YAT_WITH_CXX11`. Internally, yat `#defines` `YAT_WITH_CXX11` (in config.h), so the libyat is in this case built with cxx11 features (meaning both speedups and such as well as API extensions are implemented in the lib). When external code is compiled against yat, cxx11 features are only available if the user `#defines` `YAT_WITH_CXX11`. I suggest we modify this requirement, so the default behaviour is that cxx11 features are available if they've been found during configure (but configure does not turn on switches such as -std=c++11). |
| | 7 | and the (private) macro, `YAT_HAVE_CXX11__` is only `#defined`, if user `#defines` `YAT_WITH_CXX11`. Internally, yat `#defines` `YAT_WITH_CXX11` (in config.h), so the libyat is in this case built with cxx11 features (meaning both speedups and such as well as API extensions are implemented in the lib). When external code is compiled against yat, cxx11 features are only available if the user `#defines` `YAT_WITH_CXX11`. I suggest we modify this requirement, so the default behaviour is that cxx11 features are available if they've been found during configure (but configure does not turn on switches such as -std=c++11). |
