Rename repository to symengine.f

[rikardn]

symengine.f90 signals bindings to an old fortran standard. Perhaps we could rename it to symengine.f to avoid the fortran version in the name?

[ivan-pi]

Unfortunately most active Fortran practitioners today (still) associate .f with the old-style F77 source files using fixed format, even if this is unrelated with the actual Fortran standard. I would recommend reading the blog post by Steve Lionel to learn more about the (mis)usage of Fortran file extensions (https://stevelionel.com/drfortran/2013/01/11/doctor-fortran-in-source-form-just-wants-to-be-free/). Also see fortran-lang/fpm#250 for a summary of the various file extensions recognized by compilers and how they are processed by default.

That being said, there was a long discussion about trying to reclaim .f as the default Fortran extensions in one of the fpm issues: fortran-lang/fpm#363. I believe @certik was be in favor of this. I agree symengine-dot-eff sounds more catchy than symengine-dot-eff-ninety.

[certik]

Yes, we should rename to symengine.f. As @ivan-pi correctly summarized, historically .f meant f77, but we have proposed in fortran-lang/fpm#363 to reclaim .f to just mean any Fortran (from f77 to modern Fortran, using free form by default). And in this case, we are talking about the name of the github repository, not the file extensions, so there is almost no issue.

Let me try to get some support for this at fortran-lang/fpm#363 in the Fortran community, but as far as I am concerned, symengine.f is better:

• Reclaiming .f file extension for modern Fortran (free form) fortran-lang/fpm#363 (comment)

[rikardn]

Thanks @ivan-pi and @certik for taking time to explain. I naïvely assumed that .f didn't carry any Fortran standard meaning. For the little Fortran programming I do professionally myself I mostly use .f08 to get good compiler defaults. I don't have a strong opinion on the matter myself so I'll leave the decision to you guys.