From maine@altair.dfrc.nasa.gov  Fri Mar 15 16:32:33 1996
Received: from altair.dfrc.nasa.gov ([130.134.34.72]) by dkuug.dk (8.6.12/8.6.12) with ESMTP id QAA06461 for <sc22wg5@dkuug.dk>; Fri, 15 Mar 1996 16:32:28 +0100
Received: by altair.dfrc.nasa.gov (SMI-8.6/SMI-SVR4)
	id HAA04296; Fri, 15 Mar 1996 07:33:04 -0800
Date: Fri, 15 Mar 1996 07:33:04 -0800
Message-Id: <199603151533.HAA04296@altair.dfrc.nasa.gov>
From: Richard Maine <maine@altair.dfrc.nasa.gov>
To: m-tanaka@lp.nm.fujitsu.co.jp
CC: sc22wg5@dkuug.dk
In-reply-to: <199603151136.MAA00434@dkuug.dk> (message from Minoru Tanaka on
	Fri, 15 Mar 1996 20:34:10 +0900)
Subject: Re: (SC22WG5.1048) Does anyone have complete diff between F90 and F95 ?


> We, Japanese Fortran Standard Committee, will begin to translate Fortran 95 
> to Japanese in April. We are looking for complete diff file between F90 and
> F95 in order to translate efficiently.
> Does anyone have such the diff file ?

I doubt it.  Anyway, I don't.  In fact, I don't have f90 and f95 in
compatable formats.  F90 was done in some form of troff; I don't
recall the details (Walt Brainerd knows).  There was considerable work
in converting the f90 document source into a form useable by Frame,
which is used for f95.  The first step of this was an automatic
converter, but a lot of manual fix-up was required after the translator
was run.  Fixing up problems in the format translation was done
concurrently with incorporation of edits from corrigendum 1.  Thus,
there was never a Frame version of the original f90 text.

Probably the closest to a practical way of making a diff would be to get
ascii copies of both f90 and f95 and to write a suitable diff program
to work with them (the standard unix diff wouldn't do).

-- 
Richard Maine
maine@altair.dfrc.nasa.gov

