# Research articles using Fortran, 2025 on

**URL:** <https://fortran-lang.discourse.group/t/research-articles-using-fortran-2025-on/9070>\
**Category:** Announcements\
**Created:** [January 14, 2025, 2:08am UTC](https://fortran-lang.discourse.group/t/research-articles-using-fortran-2025-on/9070 "2025-01-14T02:08:00Z")\
**Posts on this page:** 1\
**Showing post:** 23

<div class="post-metadata">

**Author:** ![ivanpribec](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/ivanpribec/32/3290_2.png) [@ivanpribec](https://fortran-lang.discourse.group/u/ivanpribec)\
**Post date:** [October 15, 2026, 9:35pm UTC](https://fortran-lang.discourse.group/t/research-articles-using-fortran-2025-on/9070/23 "2026-10-15T21:35:04Z")

</div>

> **[Migrating Esope to Fortran 2008 using model transformations](https://arxiv.org/abs/2601.21755v1)**
>
> Legacy programming languages such as FORTRAN 77 still play a vital role in many industrial applications. Maintaining and modernizing these languages is challenging, especially when migrating to newer standards such as Fortran 2008. This is...

It looks like the continuation of work which has been discussed previously on Discourse (cc @uNouss):

- [Looking for parsers for fortran77](https://fortran-lang.discourse.group/t/looking-for-parsers-for-fortran77/4606)
- [Parsing Fortran-77 with proprietary extensions (preprint)](https://fortran-lang.discourse.group/t/parsing-fortran-77-with-proprietary-extensions-preprint/6483)

The techniques could be of interest to other companies or groups dealing with non-standard FORTRAN extensions.

---

_[View the full topic](https://fortran-lang.discourse.group/t/research-articles-using-fortran-2025-on/9070)._