| > In that declaration is where some comments would be. Here's the declaration of the parameters: INTEGER N, INCFD, NE, IERR
REAL X(*), F(INCFD,*), D(INCFD,*), XE(*), FE(*)
LOGICAL SKIP
Sorry, but no comments to be found :)> NE,XE, and FE "E" means "error"? Maybe. Wrong guess - "E" means "Evaluation" as in "to be evaluated" in this case. It's also not clear which are inputs and outputs and primitive data types give no indication at all about constraints and use-case. > IERR is an error flag. Idiomatic fortran there. Now that's true, but idiomatic cases that are well documented and don't benefit from AI documentation. Simple pattern matching will do. The point I was trying to make wasn't really about any specific programming language either. The point is rather that documentation requires translating implementation to intent and purpose. If you have a system that's capable of translating a program into purpose, constraints, and usage example(s) expressed in plain natural language; you have created a system to end all programming languages, because the inverse transform would be possible as well... |
nice to see someone else using fortran 77. or at least reading it.