(j3.2006) fortran 2003 and 2008 compiler conformance table in fortran forum
Ian Chivers
ian.chivers
Fri Dec 31 07:28:02 EST 2010
Thanks Bill,
I'll go ahead with your and Stan's suggestions.
-----Original Message-----
From: j3-bounces at j3-fortran.org [mailto:j3-bounces at j3-fortran.org] On Behalf
Of Bill Long
Sent: 30 December 2010 23:02
To: fortran standards email list for J3
Subject: Re: (j3.2006) fortran 2003 and 2008 compiler conformance table in
fortran forum
Hi Ian,
I wold vote for the N1828 names for two reasons. They are more accurate
descriptions of the features, and we want to point readers to the N1828
paper rather than N1729. Having the cited paper and the table match is
helpful since it allows the reader to directly get more details on a
feature.
Cheers,
Bill
On 12/28/10 10:53 AM, Ian Chivers wrote:
>
> Stan Whitlock emailed me on 10th November regarding
> The table and made the following comment
>
> Quoting Stan
>
> I hope you will be updating the F2008 features list based on John Reid's
> updated article:
>
> ISO/N1828 - Features of F2008 - John Reid - latest adds features
>
> End quoting Stan.
>
> Being lazy I hadn't :-).
>
> I've taken the table of contents from 1729 and 1828 and added
> Them as text below.
>
> Lines ending N1729 come from the original article
> And appear in the table in Fortran Forum.
>
> Lines ending in N1828 come from the most recent version.
>
> Could people let me know what they want in the table
> In the future? Most of it would obviously be much the same.
>
> For this to go into the April edition I need feed back fairly
> Quickly as I have to let the compiler vendors have plenty
> Of time to complete their entries.
>
> (cray, g95, gfortran, hp, ibm, intel, nag, sun)
>
> Problems with missing space characters are due to pdf funnies.
>
> 2 Submodules N1729
> 2 Submodules N1828
> 3 Coarrays N1729
> 3 Coarrays N1828
> 4 Performance enhancements N1729
> 4 Performance enhancements N1828
> 4.1 do concurrent N1729
> 4.1 do concurrent N1828
> 4.2 Contiguous attribute N1729
> 4.2 Contiguous attribute N1828
> 4.3 Simply contiguous arrays N1729
> 4.3 Simply contiguous arrays N1828
> 5 Data declaration N1828
> 5 Data enhancements N1729
> 5.1 Maximum rank N1729
> 5.1 Maximum rank N1828
> 5.2 Long integers N1729
> 5.2 Long integers N1828
> 5.3 Allocatable components N1729
> 5.3 Allocatable components of recursive type N1828
> 5.4 Implied-shape array N1729
> 5.4 Implied-shape array N1828
> 5.5 Pointer initialization N1729
> 5.5 Pointer initialization N1828
> 5.6 Data statement restrictions lifted N1828
> 5.6 Kind offorall index N1729
> 5.7 Allocatingpolymorphic variable N1729
> 5.7 Kind offorall index N1828
> 5.8 Type statement for intrinsic types N1828
> 5.9 Declaring type-bound procedures N1828
> 6 Accessing data objects N1729
> 6 Data usage N1828
> 6.1 Accessing real and imaginary parts N1729
> 6.1 Omitting an allocatable component instructure constructor
N1828
> 6.2 Copying the bounds ofsource array in an allocate statement
> N1828
> 6.2 Pointer functions N1729
> 6.3 Allocatingpolymorphic variable N1828
> 6.4 Accessing real and imaginary parts N1828
> 6.5 Pointer functions N1828
> 6.6 Elemental dummy argument restrictions lifted N1828
> 7 Input/Output N1729
> 7 Input/Output N1828
> 7.1 Findingunit when opening
> le N1729
> 7.1 Findingunit when openingfile N1828
> 7.2 g0 edit descriptor N1729
> 7.2 g0 edit descriptor N1828
> 7.3 Unlimited format item N1729
> 7.3 Unlimited format item N1828
> 7.4 Recursive input/output N1729
> 7.4 Recursive input/output N1828
> 8 Execution control N1729
> 8 Execution control N1828
> 8.1 The block construct N1729
> 8.1 The block construct N1828
> 8.2 Exit statement N1729
> 8.2 Exit statement N1828
> 8.3 Stop code N1729
> 8.3 Stop code N1828
> 9 Intrinsic procedures and modules N1828
> 9 Intrinsic procedures for bit processsing N1729
> 9.1 Bit processsing N1828
> 9.1 Bit sequence comparison N1729
> 9.1.1 Bit sequence comparison N1828
> 9.1.2 Combined shifting N1828
> 9.1.3 Counting bits N1828
> 9.1.4 Masking bits N1828
> 9.1.5 Shifting bits N1828
> 9.1.6 Merging bits N1828
> 9.1.7 Bit transformational functions N1828
> 9.10 Location of maximum or minimum value in an array N1828
> 9.11 Find location in an array N1828
> 9.12 String comparison N1828
> 9.13 Constants N1828
> 9.14 Module procedures N1828
> 9.2 Combined shifting N1729
> 9.2 Storage size N1828
> 9.3 Counting bits N1729
> 9.3 Taking radix into account when selectingreal kind N1828
> 9.4 Extensions to trigonometric and hyperbolic intrinsic functions
> N1828
> 9.4 Masking bits N1729
> 9.5 Bessel functions N1828
> 9.5 Shifting bits N1729
> 9.6 Error and gamma functions N1828
> 9.6 Merging bits N1729
> 9.7 Bit transformational functions N1729
> 9.7 Euclidean vector norms N1828
> 9.8 Parity N1828
> 9.9 Execute command line N1828
> 10 Intrinsic procedures and modules N1729
> 10 Programs and procedures N1828
> 10.1 Save attribute for module and submodule data N1828
> 10.1 Storage size N1729
> 10.2 Empty contains section N1828
> 10.2 Selectingreal kind N1729
> 10.3 Form of the end statement for an internal or module procedure
> N1828
> 10.3 Hyperbolic intrinsic functions N1729
> 10.4 Bessel functions N1729
> 10.4 Internal procedure as an actual argument or pointer target
> N1828
> 10.5 Null pointer or unallocated allocatable as an absent dummy argument
> N1828
> 10.5 Tangent function N1729
> 10.6 Error and gamma functions N1729
> 10.6 Pointer dummy arguments N1828
> 10.7 Euclidean vector norms N1729
> 10.7 Generic resolution by pointer/allocatable or data/procedure
> N1828
> 10.8 Elemental procedures that are not pure N1828
> 10.8 Parity N1729
> 10.9 Entry statement becomes obsolescent N1828
> 10.9 Execute command line N1729
> 10.10 Location of maximum or minimum value in an array N1729
> 10.11 Find location in an array N1729
> 10.12 Constants N1729
> 10.13 Module procedures N1729
> 11 Programs and procedures N1729
> 11 Source form N1828
> 11.1 Empty contains section N1729
> 11.1 Semicolon at line start N1828
> 11.2 Internal procedure as an actual argument N1729
> 11.3 Generic resolution by pointer or allocatable attribute N1729
> 11.4 Null pointer asmissing dummy argument N1729
> 11.5 Elemental procedures that are not pure N1729
> 11.6 Entry statement becomes obsolescent N1729
>
> Cheers
>
> Ian Chivers
--
Bill Long longb at cray.com
Fortran Technical Support & voice: 651-605-9024
Bioinformatics Software Development fax: 651-605-9142
Cray Inc./Cray Plaza, Suite 210/380 Jackson St./St. Paul, MN 55101
_______________________________________________
J3 mailing list
J3 at j3-fortran.org
http://j3-fortran.org/mailman/listinfo/j3
More information about the J3
mailing list