|
|
|
Size
|
Re: A question on the feature 'recursive components of allocatable type' from Fortran 2008
|
Malcolm Cohen |
Thu, 1 Jun 2017 10:47:36 +0900 |
388 lines |
Re: A question on the feature 'recursive components of allocatable type' from Fortran 2008
|
Vipul Parekh |
Thu, 1 Jun 2017 11:56:51 -0400 |
76 lines |
Re: A question on the feature 'recursive components of allocatable type' from Fortran 2008
|
Van Snyder |
Thu, 1 Jun 2017 11:38:05 -0700 |
90 lines |
Re: A question on the feature 'recursive components of allocatable type' from Fortran 2008
|
Malcolm Cohen |
Fri, 2 Jun 2017 13:12:35 +0900 |
180 lines |
Re: A question on the feature 'recursive components of allocatable type' from Fortran 2008
|
Malcolm Cohen |
Fri, 2 Jun 2017 14:32:41 +0900 |
37 lines |
Re: Features for the next Fortran Standard (following Fortran 2015)
|
Robin Vowels |
Fri, 2 Jun 2017 16:22:05 +1000 |
23 lines |
Re: Features for the next Fortran Standard (following Fortran 2015)
|
Malcolm Cohen |
Fri, 2 Jun 2017 15:55:09 +0900 |
41 lines |
Re: Features for the next Fortran Standard (following Fortran 2015)
|
Robin Vowels |
Fri, 2 Jun 2017 17:40:03 +1000 |
37 lines |
Re: Features for the next Fortran Standard (following Fortran 2015)
|
Robin Vowels |
Fri, 2 Jun 2017 17:51:42 +1000 |
52 lines |
Re: Features for the next Fortran Standard (following Fortran 2015)
|
Malcolm Cohen |
Fri, 2 Jun 2017 17:30:08 +0900 |
37 lines |
Re: Features for the next Fortran Standard (following Fortran 2015)
|
Robin Vowels |
Fri, 2 Jun 2017 18:43:27 +1000 |
60 lines |
Re: A question on the feature 'recursive components of allocatable type' from Fortran 2008
|
Vipul Parekh |
Fri, 2 Jun 2017 09:32:03 -0400 |
32 lines |
Re: Features for the next Fortran Standard (following Fortran 2015)
|
Bill Long |
Fri, 2 Jun 2017 15:48:30 +0000 |
68 lines |
Re: Features for the next Fortran Standard (following Fortran 2015)
|
Robin Vowels |
Sat, 3 Jun 2017 13:15:41 +1000 |
54 lines |
Re: Features for the next Fortran Standard (following Fortran 2015)
|
Van Snyder |
Fri, 2 Jun 2017 22:51:01 -0700 |
33 lines |
Re: Features for the next Fortran Standard (following Fortran 2015)
|
Bill Long |
Sun, 4 Jun 2017 23:25:16 +0000 |
60 lines |
Re: Features for the next Fortran Standard (following Fortran 2015)
|
John Harper |
Tue, 6 Jun 2017 10:06:47 +1200 |
53 lines |
Re: Features for the next Fortran Standard (following Fortran 2015)
|
John Harper |
Tue, 6 Jun 2017 12:12:22 +1200 |
73 lines |
Re: Features for the next Fortran Standard (following Fortran 2015)
|
Malcolm Cohen |
Tue, 6 Jun 2017 10:00:16 +0900 |
70 lines |
Re: Features for the next Fortran Standard (following Fortran 2015)
|
W. J. Metzger |
Tue, 6 Jun 2017 09:41:30 +0200 |
91 lines |
Re: +AFs-COMP-FORTRAN-90+AF0- Features for the next Fortran Standard (following Fortran 2015)
|
Malcolm Cohen |
Tue, 6 Jun 2017 17:12:00 +0900 |
146 lines |
Re: Features for the next Fortran Standard (following Fortran 2015)
|
Vipul Parekh |
Tue, 6 Jun 2017 09:09:55 -0400 |
96 lines |
Re: Features for the next Fortran Standard (following Fortran 2015)
|
Bill Long |
Tue, 6 Jun 2017 15:10:38 +0000 |
88 lines |
A question on CMPLX function
|
Vipul Parekh |
Tue, 6 Jun 2017 12:32:02 -0400 |
79 lines |
Re: A question on CMPLX function
|
Anton Shterenlikht |
Tue, 6 Jun 2017 18:14:07 +0100 |
83 lines |
Re: A question on CMPLX function
|
Vipul Parekh |
Tue, 6 Jun 2017 14:26:16 -0400 |
42 lines |
Re: Features for the next Fortran Standard (following Fortran 2015)
|
Phillip Helbig |
Tue, 6 Jun 2017 23:10:55 +0200 |
17 lines |
Re: Features for the next Fortran Standard (following Fortran 2015)
|
David Vowles |
Wed, 7 Jun 2017 00:04:12 +0000 |
46 lines |
Re: Features for the next Fortran Standard (following Fortran 2015)
|
Dick Hendrickson |
Tue, 6 Jun 2017 20:06:40 -0500 |
258 lines |
Re: Features for the next Fortran Standard (following Fortran 2015)
|
Phillip Helbig |
Wed, 7 Jun 2017 10:33:37 +0200 |
21 lines |
Re: Features for the next Fortran Standard (following Fortran 2015)
|
W. J. Metzger |
Wed, 7 Jun 2017 11:02:32 +0200 |
162 lines |
Re: Features for the next Fortran Standard (following Fortran 2015)
|
Clune, Thomas L. (GSFC-6101) |
Wed, 7 Jun 2017 11:40:12 +0000 |
138 lines |
Re: Features for the next Fortran Standard (following Fortran 2015)
|
Bill Long |
Wed, 7 Jun 2017 14:40:20 +0000 |
32 lines |
On the matter of an alternate constructor for a COMPLEX type
|
Vipul Parekh |
Wed, 7 Jun 2017 15:50:45 -0400 |
119 lines |
Re: Features for the next Fortran Standard (following Fortran 2015)
|
John Harper |
Thu, 8 Jun 2017 09:46:45 +1200 |
75 lines |
Re: On the matter of an alternate constructor for a COMPLEX type
|
Dick Hendrickson |
Wed, 7 Jun 2017 20:21:31 -0500 |
312 lines |
Re: Features for the next Fortran Standard (following Fortran 2015)
|
Robin Vowels |
Thu, 8 Jun 2017 12:07:00 +1000 |
85 lines |
Re: Features for the next Fortran Standard (following Fortran 2015)
|
Robin Vowels |
Thu, 8 Jun 2017 12:08:49 +1000 |
24 lines |
Re: Features for the next Fortran Standard (following Fortran 2015)
|
Robin Vowels |
Thu, 8 Jun 2017 12:21:37 +1000 |
52 lines |
Re: Features for the next Fortran Standard (following Fortran 2015)
|
Robin Vowels |
Thu, 8 Jun 2017 12:23:37 +1000 |
29 lines |
Re: Features for the next Fortran Standard (following Fortran 2015)
|
Van Snyder |
Wed, 7 Jun 2017 19:25:28 -0700 |
41 lines |
Re: Features for the next Fortran Standard (following Fortran 2015)
|
Robin Vowels |
Thu, 8 Jun 2017 12:32:03 +1000 |
41 lines |
Re: Features for the next Fortran Standard (following Fortran 2015)
|
Robin Vowels |
Thu, 8 Jun 2017 12:37:19 +1000 |
34 lines |
Re: A question on CMPLX function
|
Robin Vowels |
Thu, 8 Jun 2017 12:42:00 +1000 |
50 lines |
Re: Features for the next Fortran Standard (following Fortran 2015)
|
Robin Vowels |
Thu, 8 Jun 2017 12:45:33 +1000 |
32 lines |
Re: Features for the next Fortran Standard (following Fortran 2015)
|
Robin Vowels |
Thu, 8 Jun 2017 12:51:17 +1000 |
63 lines |
Re: Features for the next Fortran Standard (following Fortran 2015)
|
Robin Vowels |
Thu, 8 Jun 2017 12:52:49 +1000 |
35 lines |
Re: Features for the next Fortran Standard (following Fortran 2015)
|
Robin Vowels |
Thu, 8 Jun 2017 12:57:13 +1000 |
56 lines |
Re: On the matter of an alternate constructor for a COMPLEX type
|
Vipul Parekh |
Thu, 8 Jun 2017 00:07:11 -0400 |
92 lines |
Re: +AFs-COMP-FORTRAN-90+AF0- Features for the next Fortran Standard (following Fortran 2015)
|
Malcolm Cohen |
Thu, 8 Jun 2017 13:22:17 +0900 |
49 lines |
Re: On the matter of an alternate constructor for a COMPLEX type
|
Malcolm Cohen |
Thu, 8 Jun 2017 13:35:26 +0900 |
31 lines |
Re: +AFs-COMP-FORTRAN-90+AF0- Features for the next Fortran Standard (following Fortran 2015)
|
Robin Vowels |
Thu, 8 Jun 2017 15:04:20 +1000 |
67 lines |
Re: +AFs-COMP-FORTRAN-90+AF0- +AFs-COMP-FORTRAN-90+AF0- Features for the next Fortran Standard (following Fortran 2015)
|
Malcolm Cohen |
Thu, 8 Jun 2017 14:40:34 +0900 |
40 lines |
Re: Features for the next Fortran Standard (following Fortran 2015)
|
Robin Vowels |
Thu, 8 Jun 2017 16:30:56 +1000 |
59 lines |
Re: Features for the next Fortran Standard (following Fortran 2015)
|
Phillip Helbig |
Thu, 8 Jun 2017 10:07:14 +0200 |
17 lines |
Re: Features for the next Fortran Standard (following Fortran 2015)
|
Robin Vowels |
Thu, 8 Jun 2017 20:18:01 +1000 |
32 lines |
Re: Features for the next Fortran Standard (following Fortran 2015)
|
Dan Nagle |
Thu, 8 Jun 2017 09:45:01 -0600 |
53 lines |
Re: Features for the next Fortran Standard (following Fortran 2015)
|
Bill Long |
Thu, 8 Jun 2017 16:14:36 +0000 |
41 lines |
Re: Features for the next Fortran Standard (following Fortran 2015)
|
Phillip Helbig |
Thu, 8 Jun 2017 20:58:35 +0200 |
26 lines |
Re: Features for the next Fortran Standard (following Fortran 2015)
|
Steve Lionel |
Thu, 8 Jun 2017 15:15:29 -0400 |
61 lines |
Re: Features for the next Fortran Standard (following Fortran 2015)
|
Phillip Helbig |
Thu, 8 Jun 2017 21:18:22 +0200 |
32 lines |
Re: Features for the next Fortran Standard (following Fortran 2015)
|
Steve Lionel |
Thu, 8 Jun 2017 15:42:22 -0400 |
84 lines |
Re: On the matter of an alternate constructor for a COMPLEX type
|
Vipul Parekh |
Thu, 8 Jun 2017 22:27:06 -0400 |
53 lines |
Re: Features for the next Fortran Standard (following Fortran 2015)
|
Ian Chivers |
Fri, 9 Jun 2017 09:14:09 +0100 |
187 lines |
Re: On the matter of an alternate constructor for a COMPLEX type
|
Anton Shterenlikht |
Fri, 9 Jun 2017 10:02:48 +0100 |
20 lines |
Re: Features for the next Fortran Standard (following Fortran 2015)
|
Phillip Helbig |
Fri, 9 Jun 2017 12:36:26 +0200 |
28 lines |
Re: Features for the next Fortran Standard (following Fortran 2015)
|
Vipul Parekh |
Fri, 9 Jun 2017 11:14:24 -0400 |
42 lines |
Re: Features for the next Fortran Standard (following Fortran 2015)
|
Van Snyder |
Fri, 9 Jun 2017 08:31:00 -0700 |
39 lines |
Re: Features for the next Fortran Standard (following Fortran 2015)
|
Steve Lionel |
Fri, 9 Jun 2017 11:47:52 -0400 |
31 lines |
DTIO question
|
Walt Brainerd |
Sat, 10 Jun 2017 11:19:23 -0600 |
144 lines |
Re: DTIO question
|
Steve Lionel |
Sat, 10 Jun 2017 17:24:45 -0400 |
89 lines |
Re: DTIO question
|
Bill Long |
Sat, 10 Jun 2017 21:47:33 +0000 |
110 lines |
Re: DTIO question
|
Malcolm Cohen |
Mon, 12 Jun 2017 09:38:24 +0900 |
486 lines |
Re: DTIO question
|
Daniel C Chen |
Mon, 12 Jun 2017 10:21:39 -0400 |
200 lines |
Re: DTIO question
|
Walt Brainerd |
Mon, 12 Jun 2017 08:30:21 -0600 |
397 lines |
LITERAL_KINDS, a statement that can help enhance working with literal constants in Fortran?
|
Vipul Parekh |
Mon, 12 Jun 2017 18:13:30 -0400 |
115 lines |
Re: LITERAL_KINDS, a statement that can help enhance working with literal constants in Fortran?
|
Malcolm Cohen |
Tue, 13 Jun 2017 14:34:07 +0900 |
147 lines |
Re: LITERAL_KINDS, a statement that can help enhance working with literal constants in Fortran?
|
Vipul Parekh |
Tue, 13 Jun 2017 16:21:04 -0400 |
45 lines |
Re: LITERAL_KINDS, a statement that can help enhance working with literal constants in Fortran?
|
Malcolm Cohen |
Wed, 14 Jun 2017 08:59:17 +0900 |
77 lines |
Re: LITERAL_KINDS, a statement that can help enhance working with literal constants in Fortran?
|
Robin Vowels |
Wed, 14 Jun 2017 10:56:20 +1000 |
130 lines |
Re: Features for the next Fortran Standard (following Fortran 2015)
|
Robin Vowels |
Wed, 14 Jun 2017 11:47:17 +1000 |
58 lines |
Re: LITERAL_KINDS, a statement that can help enhance working with literal constants in Fortran?
|
Vipul Parekh |
Wed, 14 Jun 2017 00:32:21 -0400 |
24 lines |
Re: LITERAL_KINDS, a statement that can help enhance working with literal constants in Fortran?
|
Robin Vowels |
Wed, 14 Jun 2017 16:56:17 +1000 |
38 lines |
elements of array coarray var defined/referenced in unordered segments
|
Anton Shterenlikht |
Thu, 22 Jun 2017 11:39:47 +0100 |
40 lines |
Re: elements of array coarray var defined/referenced in unordered segments
|
John Reid |
Thu, 22 Jun 2017 11:57:17 +0100 |
56 lines |
Re: elements of array coarray var defined/referenced in unordered segments
|
Anton Shterenlikht |
Thu, 22 Jun 2017 12:13:21 +0100 |
41 lines |
Re: elements of array coarray var defined/referenced in unordered segments
|
John Reid |
Thu, 22 Jun 2017 12:43:57 +0100 |
58 lines |
Re: elements of array coarray var defined/referenced in unordered segments
|
Anton Shterenlikht |
Thu, 22 Jun 2017 13:06:23 +0100 |
27 lines |
Re: elements of array coarray var defined/referenced in unordered segments
|
Bill Long |
Thu, 22 Jun 2017 15:04:13 +0000 |
95 lines |