hodgesse1 / rfortran

Automatically exported from code.google.com/p/rfortran
0 stars 0 forks source link

Fortran-2003 constructs #43

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
*** What steps will reproduce the problem?

Compile/build RFortran

*** What is the expected output?

A code bult using Fortran-95 and required binding extensions

*** What do you see instead?

Fortran-2003 features, which are, in general, only tentatively supported by
current compilers. They can be identified by turning the standard checking
on and selecting Fortran-95.

*** What version of RFortran are you using?

v 1.0.0

*** Please provide any additional information below.

Unless truly needed to enable some functionality, I would suggest using
only Fortran-95 facilities+extensions. REAL(16)::GOD only knows when/IF
F2003 will be properly supported.

Original issue reported on code.google.com by dmitri.k...@gmail.com on 6 Aug 2009 at 6:45

GoogleCodeExporter commented 8 years ago
Will be addressed in v2.1

Original comment by mark.th...@gmail.com on 19 Feb 2010 at 5:50

GoogleCodeExporter commented 8 years ago

Original comment by mark.th...@gmail.com on 19 Feb 2010 at 5:50

GoogleCodeExporter commented 8 years ago
v.2.0.1 of RFortran is almost fully compliant to F2003 standard.

F2003 standard was chosen because it allows the following (which F95 does not)
(a) allocatable dummy arguments
(b) allocatable components of derived types. 
(c) longer variable names

As some of these features are used in RFortran it would create a large amount 
of 
unnecessary warnings if F95 standard was used.

Original comment by mark.th...@gmail.com on 4 Mar 2010 at 1:31