[Octave-bug-tracker] [bug #54390] liboctave/external incompatibilities with upcoming Fortran 2018

[Carlo de Falco]

Follow-up Comment #6, bug #54390 (project octave):

I see from the gfortran manpage


 -std=std
           Specify the standard to which the program is expected to conform,
which may be
           one of f95, f2003, f2008, gnu, or legacy.  The default value for
std is gnu,
           which specifies a superset of the Fortran 95 standard that includes
all of the
           extensions supported by GNU Fortran, although warnings will be
given for obsolete
           extensions not recommended for use in new code.  The legacy value
is equivalent
           but without the warnings for obsolete extensions, and may be useful
for old non-
           standard programs.  The f95, f2003 and f2008 values specify strict
conformance to
           the Fortran 95, Fortran 2003 and Fortran 2008 standards,
respectively; errors are
           given for all extensions beyond the relevant language standard, and
warnings are
           given for the Fortran 77 features that are permitted but
obsolescent in later
           standards. -std=f2008ts allows the Fortran 2008 standard including
the additions
           of the Technical Specification (TS) 29113 on Further
Interoperability of Fortran
           with C and TS 18508 on Additional Parallel Features in Fortran.


Isn't 


-std=legacy


the compile option we need to use? Is there something similar in other
compilers?

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?54390>

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