Re: A Fortran book for returning to Fortran?

On 10/25/2011 10:59 PM, John Harper wrote:
Daniel Carrera wrote:

Ok. That's not how I was using the term. I treated "obsolete" as a
synonym to "obsolescent" and not at all like "deleted". My understanding
is that these are features that you should not use, and compilers should
complain about.

Many compilers still let you use deleted features such as Hollerith strings,
though the standard does not require that. All standard-conforming compilers
must let you use obsolescent features such as statement functions, but some
complain only if you invoke a suitable compile-time option.

Yes, that's what I had in mind. If you use "--std=2008" in (say) GFortran, then GFortran should allow but complain about features marked as obsolete in F2008, and if instead you use "--std=90", it will only complain about features that were already marked obsolete in F90.

This is in general what I would expect. Without compliance flags, I know that compilers will often be soft on compliance requirements. For instance, I believe that GCC used to let you use C++ comments in C.

Cheers,
Daniel.
.

Relevant Pages

  • Re: GCC
    ... Code written for advanced compilers will be incompatible ... > it looks like it's finally getting better now that the standard is ... features and requiring us to change existing code to adapt ... many portability issues to deal with. ...
    (Debian-User)
  • Re: Does Fortran support function and subroutine overloading (based on parameter signatures)?
    ... side of that being good practice in my opinion. ... But for the module procedure statement, the standard doesn't allow ... I pointedly do *NOT* like cherry-picking features ... standard specified (as compilers tend to support multiple versions). ...
    (comp.lang.fortran)
  • Re: Program Fails When Parameter Fixed Constants are Changed (F77) ??
    ... feature first into the standard and then into compilers. ... It was omitted from f95 because, in spite of people working quite a bit ... and well before there were many f77 compilers. ... was not comfortable using those features in my fortran codes because ...
    (comp.lang.fortran)
  • Re: J3s workings
    ... If those features are adopted by several compilers, ... But how can we test out new features before standardizing them? ... I've no big problem with extensions for this purpose. ... be a big problem if the standard is different. ...
    (comp.lang.fortran)
  • Re: J3s workings
    ... If those features are adopted by several compilers, ... compilers developers into doing as extensions. ... be a big problem if the standard is different. ...
    (comp.lang.fortran)