fortran90.org webpage

Hi,

I wanted to publicly announce a modern Fortran webpage that I have
been working on for some time:

http://fortran90.org/

I am new to this group and I only started to use modern Fortran
on a daily basis about 1.5 years ago (previously I was
using C/C++ and Python). When I was learning Fortran,
I was missing some authoritative online resource telling
me what the modern way of doing things is, preferably
shown on examples (possibly also compared to
let's say Python/NumPy). The page is opensource:

https://github.com/certik/fortran90.org

I'll be happy to incorporate any suggestions that you might have.

Would you please let me know if there is something on the page that
should be reformulated? I don't want to do Fortran a disservice.
In particular, here I tried to collect the most frequently asked
questions (at least that I had):

http://fortran90.org/src/faq.html

For example just the first one (why would I prefer Fortran
to C/C++) was my first question and also probably the
most frequently asked/discussed question of many of
my colleagues and friends (a lot of whom use C/C++).
I tried to answer all these as best as I could, but
maybe some of you have some useful suggestions
how to improve it.

Thanks,
Ondrej Certik
http://ondrejcertik.com/
.

Relevant Pages

  • Re: call tree
    ... generation for any large program written in modern Fortran. ... I don't see why modern Fortran should be any different than modern ... This in effect requires "points-to" analysis. ... Uh, even the compiler guys? ...
    (comp.lang.fortran)
  • Re: which way is better...
    ... translate some Fortran 77 program to Fortran 90/95. ... more modern Fortran just because one thinks one should. ... maintainability - converting COMMON to modules, ...
    (comp.lang.fortran)
  • Re: which way is better...
    ... translate some Fortran 77 program to Fortran 90/95. ... If you are enhancing this program and want to introduce modern Fortran features, that's fine, but any attempt to rewrite the code can result in subtle errors. ... Groups of related routines which share some global variables that are not shared with the whole program might best be collected into a module with contained procedures. ... If you are writing pure Fortran, my advice is that you should never have INTERFACE blocks for Fortran procedures and should put procedures in modules or make them contained instead. ...
    (comp.lang.fortran)
  • Re: which way is better...
    ... translate some Fortran 77 program to Fortran 90/95. ... more modern Fortran just because one thinks one should. ... What I generally recommend when cleaning up old code is ...
    (comp.lang.fortran)
  • Re: Should anyone be using modern Fortran any more?
    ... the quantum chemistry field where large programs have developed over ... actually been taken up in these Fortran programs. ... Until recently that was strictly f77 ... field and he has moved on to modern Fortran. ...
    (comp.lang.fortran)