JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for COMP-FORTRAN-90 Archives


COMP-FORTRAN-90 Archives

COMP-FORTRAN-90 Archives


COMP-FORTRAN-90@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

COMP-FORTRAN-90 Home

COMP-FORTRAN-90 Home

COMP-FORTRAN-90  2004

COMP-FORTRAN-90 2004

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Fortran/C Speed

From:

Van Snyder <[log in to unmask]>

Reply-To:

Fortran 90 List <[log in to unmask]>

Date:

Tue, 13 Jul 2004 18:19:15 -0700

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (53 lines)

Naomi Greenberg <[log in to unmask]> wrote:

> Thank you all for your replies.  I agree with everything you've said, but it
> would be helpful to me if there were actual references I could cite proving
> this point, rather than stating opinions, albeit those of the experts.  Has
> anyone seen any comparitive studies or articles on the subjects of either
> speed considerations or, as James points out, cost ineffectiveness of
> converting legacy codes?

I can't give you articles, but I can give a real non-hypothetical example.

JPL has used a suite of Fortran 77 programs, amounting to six million
lines or so, for spacecraft navigation.  Development of this program
was begun using the FAP assemler for IBM 709 sometime before 1960.  By
1964, it was being developed in Fortran.

In 1996, a know-nothing manager got a wasp up his ass, and decided it
would be a wonderful thing to replace this program suite with one written
in C++.  The argument is that this would reduce maintenance costs.  The
cost of maintaining the Fortran program was seven work years per year
at that time.  The estimate to redevelop the suite in C++ was 120 work
years.  If the redevelopment project had been completely finished at
the instant it was proposed, and if it could reduce maintenance costs
to zero, it would break even in 2014.  Actually, the redevelopment was
to be finished in 2002, so break even would occur in 2020.  So far, the
program suite isn't finished; the estimated effort to completion is --
guess what? -- 126 work years.

Leslie Hatton (do a google search) has studied maintenance costs of
programs in various languages.  He finds that C++ programs have roughly
two to three times the density of statically-detectable defects as
equivalent programs in Fortran or Ada, and a cost-to-repair roughly
two to three times higher per defect, for a total lifetime "ownership"
cost of six times the cost of an equivalent program in Fortran or Ada.

This dosn't speak to C.

Stephen Zeigler has studied programmer's diaries from Verdix corporation
when Rational absorbed them.  They had a suite of programs of similar
functionality to Rational's.  Verdix's offerings were coded in C; Rational's
were coded in Ada.  Zeigler found that C programs have a lifetime
ownership cost roughly twice the cost of Ada programs.  Starting with
Fortran 90, many concepts pioneered in Ada have made their way into
Fortran.  Although there are no studies of which I am aware that
document this, it suggests that C programs would cost more to own
than equivalent programs in Fortran.

--
Van Snyder                    |  What fraction of Americans believe
[log in to unmask]       |  Wrestling is real and NASA is fake?
Any alleged opinions are my own and have not been approved or disapproved
by JPL, CalTech, NASA, Sean O'Keefe, George Bush, the Pope, or anybody else.

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

December 2023
February 2023
November 2022
September 2022
February 2022
January 2022
June 2021
November 2020
September 2020
June 2020
May 2020
April 2020
December 2019
October 2019
September 2019
March 2019
February 2019
January 2019
November 2018
October 2018
September 2018
August 2018
July 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
December 2015
November 2015
October 2015
September 2015
August 2015
June 2015
April 2015
March 2015
January 2015
December 2014
November 2014
October 2014
August 2014
July 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
July 2013
June 2013
May 2013
April 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
August 2010
July 2010
June 2010
March 2010
February 2010
January 2010
December 2009
October 2009
August 2009
July 2009
June 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
January 2007
2006
2005
2004
2003
2002
2001
2000
1999
1998
1997


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager