# Which five features should Fortran 202Y implement?

**URL:** <https://fortran-lang.discourse.group/t/which-five-features-should-fortran-202y-implement/3977>\
**Category:** Uncategorized\
**Created:** [July 11, 2022, 6:45pm UTC](https://fortran-lang.discourse.group/t/which-five-features-should-fortran-202y-implement/3977 "2022-07-11T18:45:43Z")\
**Posts on this page:** 1\
**Showing post:** 63

<div class="post-metadata">

**Author:** ![JohnCampbell](https://avatars.discourse-cdn.com/v4/letter/j/5daacb/32.png) [@JohnCampbell](https://fortran-lang.discourse.group/u/JohnCampbell)\
**Post date:** [July 24, 2022, 12:13pm UTC](https://fortran-lang.discourse.group/t/which-five-features-should-fortran-202y-implement/3977/63 "2022-07-24T12:13:57Z")

</div>

> [@Beliavsky](#):
>
> ```auto
> subroutine foo()
> integer :: n = 42
> 
> ```

How do you propose a compiler to process this statement ?  
There is an intent from the coder in what is a legal Fortran statement.

Or, should we delete the DATA statement also ?

Forcing " integer, save :: n = 42 " just adds to modern Fortran bloat with it’s more and more verbose unnecessary text.

---

_[View the full topic](https://fortran-lang.discourse.group/t/which-five-features-should-fortran-202y-implement/3977)._