Program Translation - Nov. 14, 2013

Clive Page usenet at
Fri Nov 15 12:46:30 CET 2013

On 14/11/2013 17:36, Gordon Sande wrote:

> Indeed! Under NAGWare Fortran it runs to completion with C=all but pulls an
> undefined reference when C=undefined is added.
> Lots of obsolete features and other warnings but no compiler error
> messages.
> The obvious lessons are that 1. Fortran has very good historical continuity
> and 2. the good debugging Fortran compilers do a good job.

I would also check it out with FTNCHEK as well - it usually finds lots 
of potential or actual problems with code of this vintage.

Clive Page

More information about the Python-list mailing list