[Octave-bug-tracker] [bug #61812] Math constants (e.g. M_PI) are not part of C/C++ standard

[Markus Mützel]

Follow-up Comment #31, bug #61812 (project octave):

If we are planning to use C++20 features, we should definitely check for
compiler switches that enable support for that. GNU's ax_cxx_compile_stdcxx
macro currently only checks for feature set versions up to C++17.
Is there something we could take for that test?

In the next step, we could manually add checks for specific features we'd like
to use. (Similarly to what we already do for C++17 polymorphic allocators.)

Preferably, that would not make the API dependent on the C++ standard version.
That means we can't rely on results during configure of Octave being valid
when our headers are included in downstream projects.
This might get tricky...

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?61812>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/