Fortran Monthly Call: June 2021

Dear all,

It’s again time to organise our next monthly call which will be in the week of June 14-18; please see the following doodle poll to mark your availability:

Doodle: Fortran Monthly Call: June 2021

The final time slot will be selected and announced on the evening (European time) of Sunday June 6, please complete the poll before then .

If there are specific topics or issues you would like to raise, even if you are unable to attend the call, please post them in the thread here.
As usual, we will record this call and make it available online.

All the best,


1 Like

A suggestion for a topic for the upcoming call, or at a later date, is gfortran and how the Community can get involved with gfortran development.


I would like to propose to discuss “maintaining packages under fortran-lang”:

Add QUADPACK to `fpm` registry · Issue #43 · fortran-lang/fpm-registry · GitHub


Don’t forget to complete the poll :wink:
Please also add items to the agenda!

Our next monthly call will be on Tuesday, June 15 at 18:00 UTC .

11:00 - 12:00 PDT (California)
19:00 - 20:00 EST (London)
20:00 - 21:00 CEST (Central Europe)

As previously, the meeting will be recorded for those who cannot attend.

Please continue to use this thread for topics you would like discussed at the meeting.
A Zoom invitation will follow soon.

Note: Anyone who is interested is welcome to join!

I found this rant

and think that there are some valid points (not about stdlib and community of course :wink: ).
It think it would be interesting to get the opinion, especially with respect to future Fortran standards.

1 Like

@MarDie, please see this thread where the author @zmi of that blog you referenced has provided some comments.

Re: “It think it would be interesting to get the opinion,” it will be useful if you can provide your input at the GitHub site for Fortran proposals, particularly toward this item:

You can also start another thread here and express your opinion if that is the approach you prefer, especially with future standard revisions that may then start a discourse with more readers chiming in.

Once enough feedback can be collected, agree it will be a good discussion topic for a monthly call.

I’ve recently come across with this, which might possibly be useful in some way for Gfortran (or other development)…

The maintainer of Dlang for GCC seems to be using that system:
Sponsor page of Iain Buclaw
A recent related forum page (announcement of new GDC release)

Btw, the latest TIOBE index seems to become 17 (from 20):
Index page
Time evolution of the index for Fortran

1 Like

Thanks @FortranFan, I have just replied there, so I am not going to repeat it here:

I’ll just say that I would like to add this to discuss at the call.

I agree with the “rant”, and I personally consider things dire, but at the same time, we are now fixing almost everything from the list, and I believe we need people to give us a chance for about 3 years from now. In 3 years I believe we might be able to convince a lot of people that Fortran has a future. Fortran in some sense has a “technical debt”, so I think people understand that it takes time to fix, as long as our plan is solid and we are making fast enough progress. I think we are.