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 2008

COMP-FORTRAN-90 August 2008

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: j3 responses to public comments

From:

Toon Moene <[log in to unmask]>

Reply-To:

Fortran 90 List <[log in to unmask]>

Date:

Sat, 23 Aug 2008 15:50:36 +0200

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (60 lines)

Jean Vézina wrote:

> I have read with much interest the J3 response about the public comments.

> I have noticed the following remarks from Richard Maine about the 
> reasons of the current lack of full Fortran 2003 compilers:
> 
> "1. The f2003 standard is a failure. In that case the committee should 
> be studying and addressing the reasons for the failure instead of just 
> pressing on.
> 
> 2. It is just too early to expect full implementations of something as 
> large as f2003. In that case, it is also too early to be proposing a 
> follow-on standard."
> 
> Actually, compilers vendors should answer directly why there are still 
> no full implementations of Fortran 2003 processors. 

As a "representative" (well, not officially) of the GNU Fortran effort, 
I am looked upon by the WG5/J3 committees as representing a "vendor".

At the London joint WG5/J3 meeting in August 2007 I tried to explain 
where we stand on this matter.

GNU Fortran is different from other vendors because we do not directly 
compete in bids.  That makes it easier for us to "avoid" the "you should 
support the Fortran X Standard, or else" decisions.  That also means we 
tend to implement what we think is implementable (by the team that we 
have); essentially, people take on projects they think they have a good 
chance of completing.

Although I do not think the Fortran 2003 Standard is a failure, this 
attitude of ours *does* put it at a disadvantage for GNU Fortran: 
Several features of the 2003 Standard mean an overhaul of sorts in 
either the compiler proper, or - more extensively - its run time 
library.  This means there is a tendency to "hesitate to implement" 
these features.

That said, I hear (in the public comments and elsewhere) that the fact 
that so few completely conformant Fortran 2003 compilers exist as a 
reason for slowing down the Fortran 2008 Standard.  I think this 
reasoning is faulty.  Few, if any, of the new features in Fortran 2008 
are dependent on new additions in Fortran 2003 (that is, Fortran 2008 
can largely be considered an update to Fortran 95).

In fact, this is what can be observed in GNU Fortran development (one of 
the nice things about being a free compiler is that its development 
process can be open): Both Fortran 2003 and Fortran 2008 features are 
developed alongside, without interference.

I hope this helps the discussion.

Kind regards,

-- 
Toon Moene - e-mail: [log in to unmask] - phone: +31 346 214290
Saturnushof 14, 3738 XG  Maartensdijk, The Netherlands
At home: http://moene.indiv.nluug.nl/~toon/
Progress of GNU Fortran: http://gcc.gnu.org/ml/gcc/2008-01/msg00009.html

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