# Using & Including flang in Modern Fortran VS Code

**URL:** <https://fortran-lang.discourse.group/t/using-including-flang-in-modern-fortran-vs-code/3417>\
**Category:** Help\
**Created:** [May 9, 2022, 1:58pm UTC](https://fortran-lang.discourse.group/t/using-including-flang-in-modern-fortran-vs-code/3417 "2022-05-09T13:58:29Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![gnikit](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/gnikit/32/1213_2.png) [@gnikit](https://fortran-lang.discourse.group/u/gnikit)\
**Post date:** [May 9, 2022, 1:58pm UTC](https://fortran-lang.discourse.group/t/using-including-flang-in-modern-fortran-vs-code/3417/1 "2022-05-09T13:58:29Z")

</div>

I was wondering if anyone has a quick way of testing the [`flang`](https://github.com/flang-compiler/flang) compiler (on Linux)? I wanted to add it as one of the linting compilers for [Modern Fortran in VS Code](https://github.com/fortran-lang/vscode-fortran-support) which means that I have to use it and reverse engineer the diagnostic messages of the compiler. To be clear I am referring to `flang` previously known as `f18` and not `flang-7`.

My go-to online testbed, [https://godbolt.org/](https://godbolt.org/), does not have a working version of flang, [see](https://github.com/compiler-explorer/compiler-explorer/issues). I am installing flang from source as I make this post but IMO it shouldn’t be that complicated or time consuming to install a compiler.

This leads me to my other question; do you think `flang` (previously `f18`) should even be one of the available linting compilers for VS Code given how unlikely it is for non-technical users to be using it?