Repository files navigation

• Syntax highlighting (Free and Fixed forms)
• Hover support, Signature help and Auto-completion
• GoTo/Peek implementation and Find/Peek references
• Project-wide and Document symbol detection and Renaming
• Native Language Server integration withfortls
• Linting support: GNU'sgfortran, Intel'sifort,ifx, NAG'snagfor
• Interactive Debugger with UI
• Formatting withfindent orfprettify
• Code snippets (more can be defined by the usersee)

The Fortran Language Serverfortls is responsiblefor providing a lot of the higher level, IDE functionality. By default,Modern Fortran will attempt to use it for hover, autocompletion, symbols and Go to & Peeking into definitions.

Allow forfortls to be automatically installed withpip orAnaconda andif the location wherefortls is installed is not in yourPATH point VS Codeto thefortls location by setting

{"fortran.fortls.path":"/custom/path/to/fortls"}

For more about the Language Server's capabilities please refer to thedocumentation offortls.

Linting allows for compiler error and warning detection while codingwithout the user having to compile.

Using an invalid if expression

Using incorrect type and rank as function argument

Linting results can be improved by providing additional options to the compiler.

You can control the include paths to be used by the linter with thefortran.linter.includePaths option.

{"fortran.linter.includePaths": ["/usr/include/**","${workspaceFolder}/include/**"]}

More options can be passed to the linter via

{"fortran.linter.extraArgs": ["-fdefault-real-8","-fdefault-double-8","-Wunused-variable","-Wunused-dummy-argument"  ]}

Default value is-Wall (or-warn all for ifort).

By default, the linter used isgfortran, Intel'sifort and Intel's LLVM based compilerifx are also supported.One can use a different linter compiler via the option

{"fortran.linter.compiler":"ifort"|"gfortran"|"ifx"|"Disabled"}

The linter executable is assumed to be found in thePATH.In order to use a different executable or if the executable can't be found in thePATHyou can point the extension to another linter with thefortran.linter.compilerPath option.

{"fortran.linter.compilerPath":"/opt/oneapi/compiler/2022.0.2/linux/bin/intel64/ifort"}

The extension uses the debugger from Microsoft'sC/C++ extensionfor Visual Studio Code. This allows this extension to use the full functionalityof the C/C++ extension for debugging applications:(un)conditional breaking points, expression evaluation, multithreaded debugging,call stack, stepping, watch window.

A minimallaunch.json script, responsible for controlling the debugger, isprovided below. However, Visual Studio Code is also capable of autogeneratingalaunch.json file and the configurations inside the file.

More details about how to set up the debugger can be found in Microsoft's website:

• General information about debugging in VS Code:https://code.visualstudio.com/docs/editor/debugging
• C/C++ extension debugger information:https://code.visualstudio.com/docs/cpp/cpp-debug
• Build tasks for easy compiling:https://code.visualstudio.com/docs/editor/tasks

{// Use IntelliSense to learn about possible attributes.// Hover to view descriptions of existing attributes.// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387"version":"0.2.0","configurations": [    {"name":"(gdb) Fortran","type":"cppdbg","request":"launch","program":"${workspaceFolder}/a.out","args": [],// Possible input args for a.out"stopAtEntry":false,"cwd":"${workspaceFolder}","environment": [],"externalConsole":false,"MIMode":"gdb","setupCommands": [        {"description":"Enable pretty-printing for gdb","text":"-enable-pretty-printing","ignoreFailures":true,        },      ],    },  ],}

Two formatters are supportedfindentandfprettify. Both of them can beinstalled withpip automatically through the extension.

Demo: formatters in action

findent	fprettify

The formatter is controlled by the user option

{"fortran.formatting.formatter":"findent"|"fprettify"|"Disabled"}

Additional arguments to the formatter can be input using

{"fortran.formatting.findentArgs": ["-Cn","-Rr"],"fortran.formatting.fprettifyArgs": ["--whitespace-comma","--enable-decl"]}

To check all available arguments to formatters tryfindent -h orfprettify -hin a terminal.

If the formatter is not present in thePATH its location can be input with

{"fortran.formatting.path":"./custom/path/venv/bin"}

Autocompletion and options validation forfpm.toml files are provided by theinstalling theEven Better TOML Visual Studio Code extension.

Snippets are included by bothfortls Language Server and the Modern Fortran VS Code extension.Some available snippets can be seen below. Users can define their own snippetsby following these VS Codeinstructions.

If you think a snippet should be shipped by with the extension feel free tosubmit afeature request

To show the symbols in the file outline enableprovide.symbols. Symbols can beserved by the fortls, the built-in, both or none. By defaultfortls is used.

{"fortran.provide.symbols":"fortls"|"Built-in"|"Both"|"Disable"}

You can also configure the case for fortran intrinsics auto-complete by using

{"fortran.preferredCase":"lowercase"|"uppercase"}

For debugging you need to have one of the following debuggers installed:

• Linux: GDB
• macOS: GDB or LLDB
• Windows: GDB or Visual Studio Windows Debugger

• Guidelines
• Code of conduct: Contributor Covenant
• License

You can support further development of the extension by fiscal donations:

to ourLFortan project on NumFOCUS

Or

directly sponsoring developers throughGitHub Sponsors