On 11/30/21 8:54 PM, Harald Anlauf via Fortran wrote:
Hi Tobias,
You seem to be quite convinced with your interpretation,
while I am simply confused.
If both compiler developers are confused, and actual compiler
implementations differ in their outcomes of the test case, IMNSHO it is
time
Hi Tobias,
Am 30.11.21 um 18:24 schrieb Tobias Burnus:
On 29.11.21 22:11, Harald Anlauf wrote:
"A whole array is a named array or a structure component whose final
part-ref is an array component name; no subscript list is appended."
I think in "h(3)" there is not really a named array – thus I
On 29.11.21 22:11, Harald Anlauf wrote:
"A whole array is a named array or a structure component whose final
part-ref is an array component name; no subscript list is appended."
I think in "h(3)" there is not really a named array – thus I read it as
if the "Otherwise ... result value is 1" appl
Hi Tobias, all,
Am 29.11.21 um 21:56 schrieb Tobias Burnus:
The problem is that the standard does not really state what the bounds
are :-(
I sort of expected that comment...
Usually, it ends up referring to LBOUND (with wordings like "each lower
bound equal to the corresponding element of LB
Hi Harald, hi Chung-Lin,
On 29.11.21 21:21, Harald Anlauf wrote:
I think you need to check the following:
allocate(c, source=h(3))
write(*,*) lbound(c,1), ubound(c,1) ! prints 1 3
...
pure function h(i) result(r)
integer, value, intent(in) :: i
integer, allocatable :: r(:)
allocate(r(3
Hi Chung-Lin,
Am 29.11.21 um 15:25 schrieb Chung-Lin Tang:
This patch by Tobias, fixes a case of setting array low-bounds, found
for particular uses of SOURCE=/MOLD=.
For example:
program A_M
implicit none
real, dimension (:), allocatable :: A, B
allocate (A(0:5))
call Init (A)
cont
