(j3.2006) (SC22WG5.5168) [ukfortran] [ Draft corrigendum 3]
Keith Bierman
khbkhb
Mon Dec 23 15:03:57 EST 2013
"Are there still any structuring engines available?"
http://www.xtran-llc.com/
I've never used it, but the author comments in a variety of Fortran related
fora and purports to be a tool designed for re-engineering existing codes.
Also
http://www.polyhedron.com/spag0html
spag did an OK job on a few tests I ran 18 or so years back. I don't recall
putting the results back into production, it was more a PoC.
Keith Bierman
khbkhb at gmail.com
kbiermank AIM
303 997 2749
On Mon, Dec 23, 2013 at 12:56 PM, Van Snyder <Van.Snyder at jpl.nasa.gov>wrote:
> On Sun, 2013-12-22 at 10:29 -0600, Bill Long wrote:
> > I would not be opposed to moving most of 5.4 into the obsolescent
> > column.
>
> I would rather not see any more stuff moved to the obsolescent column.
> Do it in textbooks or offline tools.
>
> I don't think I'm alone in using well-tested codes that are forty years
> old. I try to get rid of unreferenced identifiers, which are sometimes
> signals of mistakes. So it's unhelpful to see a few dozen warnings
> whizzing by on my screen. I pause the "make" and scroll back and say
> "Oh, yeah, that's my Newton solver from 1974, complaining that computed
> GO TO and arithmetic IF are obsolescent."
>
> The argument is that computed GO TO ought to be replaced by SELECT CASE.
> Well, the code is a coroutine. When it suspends, it's supposed to
> resume after the suspend. The suspend point is frequently inside a loop
> or an IF construct, or another SELECT CASE construct. You can't get
> back to it with a SELECT CASE construct without enormous reorganization
> of the code. The code has been used for nearly forty years. It works
> well. We haven't discovered any bugs in it for at least thirty years.
> I'm afraid to make a massive reorganization of it, for fear that it will
> be ten years before we discover the bugs thereby introduced.
>
> In the 1970's and 1980's, Caine, Farber and Gordon were selling a
> structured Fortran preprocessor called S-Fortran. When Fortran 90 was
> finally available, there wasn't much use for it (or Ratfor or SFtran or
> any of the others). But... they also sold a product called the
> Structuring Engine, that would turn "spaghetti code" into S-Fortran.
> Unfortunately, that went away also.
>
> Are there still any structuring engines available?
>
>
> _______________________________________________
> J3 mailing list
> J3 at mailman.j3-fortran.org
> http://mailman.j3-fortran.org/mailman/listinfo/j3
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.j3-fortran.org/pipermail/j3/attachments/20131223/29212fda/attachment.html
More information about the J3
mailing list