@mucephie
I have just created a repository with experimental #Fortran interfaces for #libadwaita and #libsoup :
https://github.com/vmagnin/experimental_interfaces

More explanations are in the README.md file.

@mucephie
You may be interested by joining the Fortran-lang community:
https://fortran-lang.org/community/
You will find there both big and small projects in modern #Fortran.
https://fortran-lang.discourse.group/

@alexanderm @QuControlBerlin
Welcome Alexander!

Concerning #Fortran, you could be interested by the work of the Fortran-lang community:
https://fortran-lang.org/

and join its Discourse:
https://fortran-lang.discourse.group/
(1138 registered users today)

@Calixthe@bostonsocial.online @cody

You might be interested by the #Python #Fortran Rosetta Stone tutorial:
https://fortran-lang.org/learn/rosetta_stone/

The #Fortran Package Manager #fpm 0.9.0 was released a few days ago:
https://fpm.fortran-lang.org/en/news/2023/06-02-fpm-version-0.9.0.html

Two small #fpm projects using #cairo #fortran bindings to explore two #recursive algorithms and see what #SVG vector drawing can bring:

- The first one draws a von #Koch #snowflake, using the classical recursive algorithm: https://github.com/vmagnin/von_koch_snowflake

- The second one draws a #Penrose tiling (aperiodic tiling of the plane with two tiles): https://github.com/vmagnin/penrose_tiling
The algorithm is interesting as it uses two interlaced recursive procedures: A calls A & A & B, and B calls A & B.

This repository contains #Fortran bindings for the #Cairo vector graphics library:
https://github.com/vmagnin/cairo-fortran

It is used by:
https://github.com/vmagnin/hat_polykite
which generates a SVG file including a batch of hat polykites. On March 20, 2023, David Smith and mathematicians Joseph Samuel Myers, Craig S. Kaplan and Chaim Goodman-Strauss posted a preprint on ArXiv describing that monotile with 13 sides that, used with its reflected version, admits #aperiodic tilings of the plane:
http://arxiv.org/abs/2303.10798

@neilernst
There is of course a lot of debate in the #Fortran community to get rid of that. No one would of course use implicit typing in modern code, but legacy codes are still running in many libraries...
But implicit typing is still officially the default, and IMPLICIT NONE must be used in every code.

Compilers are also of course offering options like -fimplicit-none in #GFortran. But putting explicitly IMPLICIT NONE in code is a better practice! :-)

@neilernst
In #FORTRAN, variables beginning by I, J, K, L, M, N were integers, others were real.
The IMPLICIT NONE statement was introduced in 1978 in the MIL-STD-1753 extension of the DOD, then integrated in the Fortran 90 standard.
So Fortran programmers must now always begin their programs and modules with IMPLICIT NONE to neutralize the ancient behavior.

And that's of course why most programmers still use the letters i, j, k as common loop counters.

gtk-fortran 4.4 released: it provides Fortran interfaces to GTK 4.10 and GLib 2.76. It has been tested on Linux Ubuntu (with GFortran and Intel ifx compilers) and Fedora, MSYS2/Windows 10, macOS and FreeBSD.

https://github.com/vmagnin/gtk-fortran/wiki

Remark: options have been added to facilitate the use of the cfwrapper Python script with other C libraries (see https://github.com/vmagnin/gtk-fortran/wiki/How-to-hack-the-cfwrapper).

#GTK #Fortran #gtkfortran #binding

A new example has been added in the gtk-fortran-extra repository (MIT license) : Peter Saville’s color code

https://github.com/vmagnin/gtk-fortran-extra/tree/main/saville_code

Manchester graphic designer Peter Saville used this code on four record sleeves, the first being the 12" Blue Monday in March 1983:

https://youtu.be/c1GxjzHm5us

#gtk #fortran #PeterSaville #BlueMonday #NewOrder

The #Fortran package manager #fpm 0.8.0 is released:

https://fpm.fortran-lang.org/en/news/2023/04-07-fpm-version-0.8.0.html

@necrosis @MartinWdd
You could also try to modernize it in modern Fortran (the latest standard is #Fortran 2018).

See:
https://fortran-lang.org/de/index
and
https://fortran-lang.discourse.group/

@jj1bdx
Yes, the #Fortran 90 standard says:
"Note that the name of this language, Fortran, differs from that in FORTRAN 77 in that only the first letter is capitalized. Both FORTRAN 77 and FORTRAN 66 used only capital letters in the official name of the language, but Fortran 90 does not continue this tradition."

In the 1950s people called FORTRAN in all caps. I guess the name was changed to #Fortran in the 1990s.

@scruss
Yes, Backus' team was aware that a good project needs a good documentation and tutorials to be adopted!

#Fortran #Documentation #Backus

@scruss

Look also at the "Programmer's Primer for FORTRAN", by Grace E. Mitchell (1957, 64 pages):
https://www.softwarepreservation.org/projects/FORTRAN/manual/IBM-704-FORTRAN-Primer-a-32-0306.pdf
#FORTRAN #documentation

https://vimeo.com/785190423?embedded=true&source=vimeo_logo&owner=186969189
#Fortran #Climate #model

@Infrapink @futurebird
In the original #Fortran compiler (1957), there were no function and no subroutine. They were introduced in FORTRAN II (1958), a huge progress!

In #C, there are only functions, but they can return void and be used like subroutines.

In #Pascal, subroutines are called procedures.

All that is just vocabulary with some subtleties...

@hpcprogrammer @jbzfn
How long? It may take a long time...

There are more than 12 #Fortran compilers maintained:
https://fortran-lang.org/en/compilers/

Sometimes a compiler is stopped, like Lahey Fortran recently.

Sometimes, new compilers are born:
Intel has developed a new LLVM ifx compiler to replace its classical ifort (ifx is now fully Fortran 2018 compliant, and is preparing for Fortran 2023). And two new other are in development: LFortran (an interactive compiler), and NVidia Flang (LLVM based).