Subscribe to Simply Fortran news via RSS!
June 7, 2021
Simply Fortran Version 3.19 Released
After a long development cycle, Approximatrix is happy to announce the availability of Simply Fortran 3.19 for all supported platforms. This release incorporates several bug fixes and compatibility improvements on all platforms, cosmetic and compatibility fixes for the Windows release, and increased functionality in the Apple Silicon macOS release.
In the Project Options window, selecting initialization of variables to zero and enabling coarrays are now mutually exclusive as this...
April 21, 2021
New Builds Available on Windows and GNU/Linux
New installers and archives are now available for Windows and GNU/Linux that address outstanding issues with Simply Fortran version 3.18. These builds do not add new features but address critical issues with Simply Fortran on these platforms.
The new Windows builds incorporate fixes to the runtime and coarray libraries. Specifically, a long-standing issue with quad-precision intrinsic procedures, causing certain programs to crash due to bugs resetting floating point...
March 15, 2021
Simply Fortran 3.18 Now Available
Approximatrix is happy to announce version 3.18 of Simply Fortran for all supported platforms. This release brings improvements to included development libraries, additional requested features, and development environment bug fixes. On all platforms, the development environment's initial folder for projects can be configured using the Appearance and Behavior Options window under the Projects category. Checking for updates can be disabled via the same window in the Updates...
Feb. 17, 2021
Bug Fixes for Version 3.17 Released
Thanks to feedback from users, a major bug has been identified and fixed in Simply Fortran that may have caused crashes and/or lock-ups in the development environment. Specifically, when syntax checking was enabled, certain compiler messages could exceed an expected size, causing the development environment to crash. The issue was somewhat uncommon, but the verbose messages emitted by the current Fortran compiler could cause the issue to manifest itself more often.
The latest builds are...
