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

[Rik]

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

I know with MACOS libraries we have had problems with just slightly different
values for certain trig calculations.  By using an expression like
"4.0*atan(1.0)" you get a value that is at least self-consistent with the
libraries being used.  It also gets around cross-compilation issues where M_PI
on the build system might be different than M_PI on the host system.  But,
that would be a really bad idea if build and host were different to begin
with.

In any case, I think we can just get rid of it if we can guarantee that M_PI
is defined.

@markus: According to our guidelines, "octave-config.h" should always be the
first header file included.  Next come C and C++ header files, then liboctave
header files, then libinterp header files.

    _______________________________________________________

Reply to this item at:

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

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