Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!news-1.dfn.de!news.dfn.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Clive Page <usenet@page2.eu>
Newsgroups: comp.lang.fortran,comp.lang.perl.misc,comp.lang.python
Subject: Re: Program Translation - Nov. 14, 2013
Date: Fri, 15 Nov 2013 11:46:30 +0000
Lines: 19
Message-ID: <bemfspF99cuU1@mid.individual.net>
References: <ro-dnch2dPtbRhnPnZ2dnUVZ_rSdnZ2d@earthlink.com> <l63014$nk9$1@dont-email.me> <l631mj$2ri$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: individual.net Z9mBvm0Bm/O2/Dmi7abvIAbOEvIDWtgm82+dL0dPHe1vhNppS+
Cancel-Lock: sha1:H2AHsR97jQAaFniB6CD9rwthIiw=
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
In-Reply-To: <l631mj$2ri$1@dont-email.me>
Xref: csiph.com comp.lang.fortran:39258 comp.lang.perl.misc:9975 comp.lang.python:59512

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