Well, that far south, and with that amount of open water, there's probably a mosquito problem. They don't come out in the rain here, and even when they do, they are the tiny species that irritate, rather than big ones carrying potentially fatal diseases like malaria, haemorrhagic dengue fever, Zika, encephalitis (of various kinds, including 'St Louis') etc! Plus there are no poisonous snakes, marsupials, spiders etc as suffered by John Campbell.
Besides, the rain here means I don't have to water the lawn. And if it upsets you that it rains in Yateley, then never, ever, research Salford's weather to see what Paul endures ...
My surprise was that while in reply mode, Mike's details such as location aren't visible. They become visible once the message is posted. Interesting, that is. Hence I've offered several times to help people who turn out to be half a world away. I wouldn't mind the frequent flyer points, if someone else pays the fare.
For a very long time, printers could be accessed via an OPEN statement with the target something like LPT: or PRN: The printers in question would respond properly to Fortran output. Windows-only printers don't respond in the same way to Fortran output, and the Fortran output needs to go through a Windows printer driver.
Oddly enough, direct output to a printer is helpful in many cases. The Clearwin+ solution takes one line, just like an OPEN statement, and once coded, can be cut and pasted anywhere in your programs, happily ever after in a fairytale ending. After that, you can format output as described in any Fortran book. Otherwise, you need to read the FTN95.chm helpfile: many times. Printing from a file is useful, but requires more user steps. Imagine that a receipt in a shop was printed to a file, then printed out from the file in a separate program. It is nowhere near as simple to do Fortran output to a page in Windows graphics mode all lined up in columns when the font is proportionally spaced - indeed, it requires much more knowledge and many more lines of code.
As for modernity, IMPLICIT NONE leaves me without an important key as to what type variables are, free format robs me of the 'outdent' that helps me work out loops, lowercase looks somehow wrong for FORTRAN, and it takes me a lot of effort to reformat someone else's code before I can work on it. If modern Fortran suits you, then use it, I have no objection to that, but don't expect me to. They are new tricks, and sadly, I am an old dog (of the toothless, sad-looking, plodding variety, but which can still, sometimes, get a blind man safely across the road).
John Campbell's 'print a matrix' is fine, but the point of the code isn't the actual printing, rather it is the convoluted, bizarre-looking, WINIO@ stuff which substitutes for the OPEN statement that has been around for decades in various forms. Everything else in the sample code can be done in multiple different ways and probably better.
Eddie