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:

Monospaced Font

LISTSERV Archives

LISTSERV Archives

COMP-FORTRAN-90 Home

COMP-FORTRAN-90 Home

COMP-FORTRAN-90  1997

COMP-FORTRAN-90 1997

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: wishlist

From:

"Dr W.W. Schulz" <[log in to unmask]>

Reply-To:

Dr W.W. Schulz

Date:

Thu, 20 Nov 1997 18:16:02 +0000 (GMT)

Content-Type:

TEXT/PLAIN

Parts/Attachments:

Parts/Attachments

TEXT/PLAIN (111 lines)

Some more general remarks on F90 etc.

I have started wondering after responses to my earlier wishlist
which actually unknowingly duplicated proposals of others.
From some of the responses it must have become clear that
new features are wanted but only few will be added. Even
some very obvious ones are still not on the committee's
agenda.

Questions:
-Are any of the members on the j3 committee listening to our
 debate (with the exception of van snyder and m cohen, of course)?
 If not most of our discussions are useless.

-Is J3 actively seeking opinions on wanted features from users
 other than the main computer and compiler vendors?
 Is there feedback from classes learning Fortran, from
 Computer Science departments (if you like it or not, they
 set the fashion on computer languages, and Fortran is
 rather old-fashioned to them), from other science departments
 (physics, chemistry, engineering, etc)?

-Is there a broad agreed direction that Fortran should take?

-Some new features show problems. Is the committee willing to
 correct/change them to something better? If the F90 base is
 not very big yet this should not cause to many problems.
 Asking colleagues and friends most of them still don't use F90!
 They even don't know some of the most important features!


Some raised objections:
-Some of the wanted features exist in other languages (e.g., enum in C,C++)
 so that there should be little problem of implementing them.
-The example of extending case to real variables must be trivial
 any objection to it is -in my mind- more obstruction than anything
 else since it just regularizes what we already have with more
 complicated if-then-else structures.
-Initializing ADT's, inheritance (at least simple) is also
 done all over the place, so there shouldn't be any great difficulties.

I have some problems with modules, the issue of separating
interface and implementation is one and already discussed by others.
A second one is why this new feature was not introduced
with safety in mind, i.e. everything in a module is private
unless declared public.
This is a general problem and if the safety/robustness issue
is not incorporated from the beginning in any new Fortran feature
it will haunt us later again and again. Examples include
-ALLOCATED (F95 automatically deallocates)
-NULL for pointers (but there are still undefined pointers
 that cannot be tested)
-PRIVATE vs PUBLIC (see above)
-initialized ADT's (F95 has it)

In the many attributes I listed for Fortran I didn't mention
efficiency. Fortran has always claimed to be more efficient than
others but some C++ code seems to be coming closer (blitz++)
or an example for FFT's shows code with recursions to be very
fast (http://theory.lcs.mit.edu/~fftw/homepage.html).

Two points of view are possible:
  If this advantage of Fortran is lost or less obvious than the
  general power of a language to express what the user wants to
  do becomes more important. And Fortran is behind here (except
  for array notation).
Or
  Some features are actually not as bad as is generally claimed
  and with a little bit of discipline hardly any loss of speed
  is suffered. And Fortran loses one of its attractive features.
In any case Fortran has to improve.

There are sometimes objections to make some features oobsolete
since older code will become incompatible with any new Fortran.
F95 has done it already, the F and elf subsets even more.
F77 compilers will be around for some time, and is no one
maintaining code? A lot of old code is rewritten anyway
since the old codes are not suitable anymore (Or are undocumented
and no one knows anymore, so one have to rewrite)
Code is still is best document of itself and clarity of
code (and language) is worth a lot.
But people are of course very stubborn, I still alot of NEW code
using EISPACK/LINPACK routines instead of the better LAPACK
ones.

In my field of ab-initio quantum mechanical calculations most
of the speed gains come -at the moment- from improved theoretical
methods and less from computing features. Traditionally this has
all been done in Fortran and is still done. But in many cases
we need a more expressive language with modular features so that
it is easy to adapt to rather quickly changing times, more robustness
and safety.

F90 has done a lot in this direction and without it I would have
switched to C++ or something else some time ago. But I want and
need more. And other users feel the same.

WWS
-----------------------------------------------------------------------
| Werner W Schulz |
| Dept of Chemistry email: [log in to unmask] |
| University of Cambridge Phone: (+44) (0)1223 336 502 |
| Lensfield Road Secretary: 1223 336 338 |
| Cambridge CB2 1EW Fax: 1223 336 536 |
| United Kingdom WWW: |
-----------------------------------------------------------------------



%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

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