Interpretion of file name suffixes

From: Erik Edelmann (eedelman_at_acclab.helsinki.fi)
Date: 05/18/04

  • Next message: Richard Maine: "Re: Interpretion of file name suffixes" 
    Date: 18 May 2004 18:41:33 GMT

    While having some problems with getting the syntax coloring mode of a text
    editor to correctly recognize my free source form fortran files as such, I
    started to wonder if there are any standard for how file name suffixes
    should be interpreted, or if it is compiler dependent. (I guess that the
    official Fortran standard doesn't say much about this, but I thought that
    some kind of "de facto standard" might have emerged).

    More specifically, how should the following file name suffixes be
    interpreted?

    .f a) Fortran 77 or older (implies fixed form)
            b) Fixed source form (any standard possible)

    .f77 a) Fortran 77 (implies fixed form)
            b) Fixed source form (any standard)
            c) Not recognized

    .f90 a) Fortran 90, free or fixed form
            b) Free form (implies Fortran 90/95)

    .f95 a) Fortran 95, free or fixed form
            b) Free form (implies Fortran 90/95)
            c) Not recognized

    The three different compilers I have access to my self seems to agree on
    the interpretion b, c, b, c. What experiences/opinions do other people in
    this group have?

            Erik

  • Next message: Richard Maine: "Re: Interpretion of file name suffixes"

    Relevant Pages

    • Re: F77 vs F95
      ... I also hope that as the Fortran standard has ... >community for F77. ... Lines can be longer than 72 characters. ... form Fortran 90 which is visually just like fixed form, ...
      (comp.lang.fortran)
    • Re: Converting fixed-to-free format
      ... archaic code useful. ... If that's all Fortran is to you, ... F2003 in fixed form for changes. ... If they don't support fixed form for ...
      (comp.lang.fortran)
    • Re: fortran and columns
      ... > jakeh wrote: ... >> to columns or any other column rules other than the programming starting ... > You don't have a newer version of Fortran to avoid this old fixed form? ...
      (comp.lang.fortran)
    • Re: Interpretion of file name suffixes
      ... for and the less common .ftn usually indicate fixed format Fortran source ... >started to wonder if there are any standard for how file name suffixes ... >..f90 a) Fortran 90, free or fixed form ...
      (comp.lang.fortran)
    • Re: A few syntax questions
      ... I think putting them in the 'action-stmt' syntax rule ... If I were to redo the bnf from scratch, ... I guess that means that a standard conforming compiler is supposed to overflow. ... I am hoping that F2003 features will regain some respect for Fortran in CS departments,, and not just be coinsidered an old archaic language for old programs, but such strong support of archaic Fortran standards is a major reason why Fortran popularity continues to dwindle. ...
      (comp.lang.fortran)