Fortran newsletter: March 2021#
Welcome to the March 2021 edition of the monthly Fortran newsletter. The newsletter comes out at the beginning of every month and details Fortran news from the previous month.
This month we’ve had several updates to the website:
#191: Fix author/maintainer output in fpm registry
#193: Rename all instances of fortran-lang.github.io to fortran-lang.org
#196: Update package index
#199: Fix broken link for LLVM flang
#205: Add more electronic structure and atomistic simulation packages
#206: Add books to learning section
#208: Fix package information
#201 (WIP): Internationalization for fortran-lang
#207 (WIP): Correct subtitle of setting up your os
Let us know if you have any suggestions for the website and its content. We welcome any new contributors to the website and the tutorials page in particular - see the contributor guide for how to get started.
Fortran Standard Library#
Here’s what’s new in
#271: Probability Distribution and Statistical Functions–PRNG Module
#304: Add supported compilers MinGW 8, 9, 10
stdlib_asciimodule for handling character variables
#324: Install setuptools for MinGW builds
Work in progress:
#189 (WIP): Initial implementation of sparse matrices.
#311 (WIP): Implementation of a module for handling lists of strings
#320 (WIP): Implement non-fancy functional string type
#313 (WIP): Legendre polynomials and Gaussian quadrature
Please help improve stdlib by testing and reviewing these pull requests!
The candidate for file system operations to be included in stdlib is being developed by @MarDiehl and @arjenmarkus in this repository. Please try it out and let us know how it works, if there are any issues, or if the API can be improved.
Fortran Package Manager#
Here’s what’s new in
#316: Update subcommand “new” to reflect the addition of support for the example/ directory
#345: Fpm backend with dynamic openmp scheduling
#346: Include root dir in path to default example setup
#349: Suggest to move the fpm version in the boostrapping process
#372: Unify release mode calling convention
Work in progress:
First beta release (WIP): First feature-complete release of the Fortran implementation.
#352 (WIP): Hacky fix for the help test
#357 (WIP): Install script for Fortran fpm
#364 (WIP): Plugin alpha version
#369 (WIP): Separate build targets from model structure
#370 (WIP): Update run subcommand
fpm is still in early development and we need as much help as we can get.
Here’s how you can help today:
Use it and let us know what you think! Read the fpm packaging guide to learn how to build your package with fpm, and the manifest reference to learn what are all the things that you can specify in the fpm.toml file.
Browse existing fpm packages on the fortran-lang website
Browse the open issues and see if you can help implement any fixes or features.
Adapt your Fortran package for fpm and submit it to the Registry.
Improve the documentation.
The short-term goal of fpm is to make development and installation of Fortran packages with dependencies easier. Its long term goal is to build a rich and decentralized ecosystem of Fortran packages and create a healthy environment in which new open source Fortran projects are created and published with ease.
The LFortran team is excited to announce that LFortran is now a NumFOCUS sponsored project. Please consider donating to LFortran to accelerate its development.
Recent Merge Requests highlights:
!648: Implement –show-stacktrace
!666: Refactor ImplicitCast nodes handling
!665: Fixed floating point printing
We had our 9th Fortran Monthly call on February 25. You can watch the recording below:
This year Fortran-lang applied as a mentor organization for Google Summer of Code. Accepted mentor organizations will be announced on March 9. If you’re a student, or know students who are eligible to participate, and you’d like to help build the Fortran ecosystem please reach out and let us know.
The 223rd meeting of the US Fortran Standards Committee is held virtually from February 22 to March 2 (Monday and Tuesday only). Main topics of dicussion are the planned changes for the Fortran 202X revision of the Standard:
If you have ideas for new improvements to the language, please propose them here.
We thank everybody who contributed to fortran-lang in the past month by commenting in any of these repositories: