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

COMP-FORTRAN-90 June 2010

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Fortran 2003 and 2008 compiler conformance table

From:

Tobias Burnus <[log in to unmask]>

Reply-To:

Fortran 90 List <[log in to unmask]>

Date:

Wed, 16 Jun 2010 18:20:27 +0200

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (56 lines)

On 06/16/2010 05:25 PM, Craig Dedo wrote:
> Since this information is changing very rapidly, it may be helpful to put an "as
> of:" date at the top of the article.  I.e., what is the latest date that the information
> is known to be good?  Also, what are the version numbers of the compilers that are listed?
> Some compilers, e.g., gfortran, are updated very frequently.
>
> Please consider these suggestions in the version you are publishing in the August
> edition of the Fortran Forum.
>   

If I recall correctly, the data was collected around April. I think for
the commercial compilers, the data was relative to what should be the
current version in August (though, I think most tried to be on the save
side by stating the status of the already released version if the
release was not imminent).

For gfortran, the data is always relative to the trunk version
(currently, GCC 4.6) on that date. I think in case of gfortran, it makes
sense to refer to the trunk version as seemingly most users, which are
interested in Fortran 2003/2008, seem to use it. Given the kind of
annual release cycle of GCC with feature freezes around November and
releases in spring, I think the April issues of Fortran Forum roughly
matches the GCC release versions. For this year's August issue, I have
send an update a few days ago, which seemingly has just made it into the
August version.

My impression is that many Fortran 2003 features can now be used - and
also F2008 features are slowly getting implemented. And seemingly,
judging from the gfortran bugreports, as soon as there is new feature
implemented, some users immediately use them for real-world code.

I think the Fortran Forum conformance tables really help to choose as
user the features which one can safely use and (to a lesser degree) aid
compiler developers to decide which features should be implemented next.
Thus: Thanks to Ian and Jane for collecting the data and publishing it
in ACM Fortran Forum!

Tobias

PS: For gfortran, see also http://gcc.gnu.org/wiki/GFortran#news , the
normal release notes (cf. http://gcc.gnu.org/ ) and the status lists at
http://gcc.gnu.org/wiki/Fortran2003Status and
http://gcc.gnu.org/wiki/Fortran2008Status

PPS: I hope that the new Fortran features help to make Fortran more
popular. I started with Fortran 95, but a few years ago I attended a
lecture* where the codes (of the lecturer) were essentially  FORTRAN 66.
(No indentation, no filenames but fort.nn etc.) Unfortunately, that
gives a completely wrong impression of Fortran and does not help to
attract students - though most students which encounter Fortran 90+ in
their master or Ph.D. thesis tend to like it. At least, I did and I know
of others.

* = a graduate physics course where some parts where illustrated with
short FORTRAN programs

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