Fortran-202X-Proposals
Fortran-202X-Proposals copied to clipboard
A place to collaborate on proposals for the next Fortran standard
My proposal in #12 was infeasible as @milancurcic pointed out. So far two possible options are 1. Make obsolescent variable initialization during declaration (because these variables get the implicit `save`...
As the list of issues grow here, we might consider ways to rank issues for whatever value that adds in informing the committee discussion. There could be labor-saving value in...
edit by @szaghi Discussion about Template programming started into [issue 2](https://github.com/Fortran-FOSS-Programmers/Fortran-202X-Proposals/issues/2) and continued here for the sake of clarity.
There are many, many applications where it is desirable to have a routine argument that accepts a limited set of variable kinds or types (say `integer` or `real`). Currently there...
... there are many ideas floating around for this...
Allow the definition of default value for **optional** dummy arguments: ```fortran subroutine foo(bar, baz=.false.) ! inline default value definition integer, intent(inout) :: bar logical, intent(in), optional :: baz if (baz)...
We need standard routines for manipulating the file system (change directory, create and delete directories, query information about files, etc.) See Intel's "Portability Library".
Something so we can avoid these annoying nested `select type` blocks. So if you want to check if several variables are integers: ```fortran ! if several variables are integers select...
Change > 13.8.2.21 REAL32, REAL64, and REAL128 > The values of these default integer scalar named constants shall be those of the kind type parameters that specify a REAL type...