undefined

points

[-]

That certainly might be one of the oldest Fortran codebases still in use I've heard of, but not quite the largest. (Character came in '77 wasn't it?)

E3SM [0] is still maintained today, and somewhere around 2mil LoC of F90.

Modern Fortran has a lot of niceties that it brings to the table.

[0] https://e3sm.atlassian.net/wiki/spaces/DOC/overview | https://github.com/E3SM-Project/E3SM

by 2 hours ago|

parent|

[-]

deleted

by bbatha32 minutes ago|

prev|

[-]

Besides the short names, common blocks and computed gotos were the bane of my existence maintaining primordial Fortran. My first and intern project was translating a punch card era (early 60s was the best bet) code base that had been textified and could compile in f77. Fortunately I didn’t have to really deal with any strings

by rbanffy3 hours ago|

prev|

[-]

> It also gave me an appreciation for JavaBeanFactoryFactory

If nothing else, short variable names create an incentive to keep functions small enough you can easily figure out what ILBNK1 means.

by obviouslynotme2 hours ago|

parent|

[-]

You would think, but that isn't what happened at all. Half the code was very nice and readable but half was giant subroutines doing complex mathematics. The largest subroutine was over 10kloc.

The best part is that the code was originally punched onto cards, so most of the early code's comments and documentation were on paper in filing cabinets, if you could find them.

by robotnikman2 hours ago|

prev|

[-]

>It also gave me an appreciation for JavaBeanFactoryFactory.

My favorite is SimpleBeanFactoryAwareAspectInstanceFactory

by nocman1 hours ago|

parent|

[-]

WOW. I went googling, sorta hoping this was a joke, but nope, there it is:

https://docs.spring.io/spring-framework/docs/current/javadoc...

I've been away from that world for a while, but still.

At least it was the "Simple" version. LOL.

by kflynn51 hours ago|

parent|

prev|

[-]

Also love AbstractSingletonProxyFacgoryBean