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  August 2010

COMP-FORTRAN-90 August 2010

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Reusing an interface for procedure-type arguments

From:

Van Snyder <[log in to unmask]>

Reply-To:

Fortran 90 List <[log in to unmask]>

Date:

Fri, 6 Aug 2010 12:16:36 -0700

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (54 lines)

On Thu, 2010-08-05 at 19:14 -0700, Vivek Rao wrote:
> Especially someone who has proposed many features in Fortran 2008
> should be aware that several compiler vendors have decided not to
> produce compilers beyond Fortran 95 (except for some TR's).
> Silverfrost is one example. Lahey, which allied with Fujitsu, is
> another. Maybe someone can comment about Pathscale.

I was told by Fujitsu, by way of Lahey, that they had no plans for
development of the 32-bit Linux product, and this included maintenance.
My questions about their 64-bit Linux product, or Windows products, or
products for Fujitsu supercomputers, were greeted with silence.

Fujitsu, Silverfrost, Pathscale and Absoft do not participate in Fortran
standardization, or this mailing list as far as I can tell.  Perhaps
Vivek could convince them to tell Ian Chivers their plans.

> Fortran 2008 has been finalized, right?

Yes, two years ago.  That's why it's called "Fortran 2008" instead of
"Fortran 2010."

> The committee should restrict itself to maintenance mode until full
> F2008 compilers are available.

Why?  With the exception of coarrays, Fortran 2008 was essentially a
maintenance project.  Although the table of contents of
ftp://ftp.nag.co.uk/sc22wg5/N1801-N1850/N1828.pdf is more than two pages
long, everything described therein except coarrays were minor projects.

A significant reason that Fortran fell into bad odor in the computer
science community between 1966 and 1990 was that it had stagnated.
Fortran 90 added free source form, modules, dynamic storage, derived
types... and then stagnated again at Fortran 95.  Notwithstanding that
Fortran 2003 was a major increment, especially by providing for
object-oriented programming, there are still things that Fortran lacks
(from a computer-science standpoint) that other languages have.  First
in line would be a generic programming facility akin to C++ templates or
Ada generic packages.  Others would be a block-structured exception
handling mechanism, assertions and other facilities for "programming by
contract," a more complete type system....

For those who use Fortran for its targeted purpose, that is, scientific
and engineering computing, a system of physical units would go quite
some distance toward catching and correcting units-related errors at
compile time, and to a certain extent at run time.  Those who develop
mathematical software that needs access to client code, such as
quadrature evaluators, differential equations solvers, minimizers,
nonlinear equation solvers... would welcome coroutines....

If ANSI and ISO committees had taken Vivek's advice in 2004 (and there
were others offering the same advice), Fortran 2008 wouldn't have
co-arrays, which are an enormous leap forward compared to PVM or MPI or
HPC or OpenMP.

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