# Comp.lang.fortran and Fortran-lang relation

**URL:** <https://fortran-lang.discourse.group/t/comp-lang-fortran-and-fortran-lang-relation/4495>\
**Category:** Meta\
**Created:** [October 7, 2022, 9:18pm UTC](https://fortran-lang.discourse.group/t/comp-lang-fortran-and-fortran-lang-relation/4495 "2022-10-07T21:18:30Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![RonShepard](https://avatars.discourse-cdn.com/v4/letter/r/a3d4f5/32.png) [@RonShepard](https://fortran-lang.discourse.group/u/RonShepard)\
**Post date:** [October 20, 2022, 9:15pm UTC](https://fortran-lang.discourse.group/t/comp-lang-fortran-and-fortran-lang-relation/4495/15 "2022-10-20T21:15:06Z")

</div>

> [@kargl](#):
>
> I used `xpn` as my newsreader; but ironically, `xpn` is written in python 2.7 and no longer works (as 2.7 is EOL and incompatible with 3.x).

Let this be a warning to those who want to introduce changes to fortran that are not backwards compatible. All languages do this to greater or lesser extents, but it is frustrating when it happens, especially with a language that you are not fluent with. I recently went through some of this with some old perl scripts.

---

_[View the full topic](https://fortran-lang.discourse.group/t/comp-lang-fortran-and-fortran-lang-relation/4495)._