Doctor Fortran Gets Explicit – Again!

Nearly 11 years ago (!) I wrote an item for the Visual Fortran Newsletter on explicit interfaces in Fortran. In recent weeks, I have had to refer quite a few customers to this article, suggesting that many Fortran programmers don’t understand the role and rules of explicit interfaces. However, when I reread the item, I realized that things had changed a bit since Fortran 95, so I figured it was time to revisit the issue.

More

Doctor Fortran in “Lest Old Acquaintance Be Forgot”

In some of my earlier posts I’ve discussed new features in the Fortran language that might be unfamiliar to some.  But this time I’m going to go the other way and describe some really old language features – so old that many newer Fortran programmers are mystified when they see them – but these features are still supported by many current compilers, including Intel Fortran.  So let’s set the Wayback Machine to the 1960s and have a look around.

More

The Real Doctors of Fortran

In this blog, I refer to myself as “Doctor Fortran”.  It’s a joke that started more than ten years ago when I decided to write an “advice column” for what was then the Digital Visual Fortran Newsletter.  Everyone liked it so much I stuck with it, but I’ve always been aware of the people who deserve that title far more than I – the members of the Fortran standards committee.  As it happens, I am an “alternate” member of the committee representing Intel, but most of the time we are represented by Stan Whitlock.  Intel Fortran developer Lorri Menard is our other alternate member.  I’ve now attended three standards meetings and thought I’d write up my experience of the most recent and give readers a feel for how the Fortran language’s evolution is guided and its cohesiveness maintained.

More

Doctor Fortran in “Think, Thank, Thunk”

One of the various responsibilities I have is for the compiler samples (both Fortran and C++).  For Intel Visual Fortran, we have a lot of samples – for the other compilers, fewer.  The Windows Fortran samples are a mixed lot; some came to us from Microsoft Fortran Powerstation (with or without extensive modification) and some were developed by us (mostly, yours truly.)

More

Doctor Fortran in “I’ve Come Here For An Argument, Side 2”

My earlier post, “I’ve Come Here For An Argument”, was very popular with my fellow support engineers, as it provided a convenient answer to questions they frequently receive.  (For me too, which in part is why I wrote it!) But some people (cough, Ron, cough) are never satisfied, and I’ve been asked to write a follow-up on what else can go wrong when you don’t understand all of Fortran’s argument-passing rules.  So, here we go…

More

Doctor Fortran in “Too Much of a Good Thing?”

A lot of Fortran programmers take the “belt and suspenders” approach to coding, with explicit declarations of every attribute they want for a symbol. In general, this is good practice, especially when combined with IMPLICIT NONE to force you to say what you mean. But some programmers take this a bit too far and it gets them into trouble. Let’s look at some cases…

More

Subscribe to Doctor Fortran

Subscribe to Doctor Fortran

Loading