--- Comment #9 from kargl at gcc dot gnu dot org 2007-06-19 03:50 ---
John,
With your acknowledgment of pault's comment, I think this
can be closed. Thanks for the reports. These types of
potential corner cases keep us on our toes.
--
kargl at gcc dot gnu dot org changed:
ot org <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: [Bug fortran/32386] Pure function not allowed in specification
> expression
>
>
>
> --- Comment #7 from pault at gcc dot gnu dot org 2007-06-18 22:49 ---
> John,
>
> 5.1
> .many snip
--- Comment #7 from pault at gcc dot gnu dot org 2007-06-18 22:49 ---
John,
5.1
.many snips.
If a specification-expr involves a reference to a specification function
(7.1.6.2), the expression is considered to be a nonconstant expression. If the
data object being declared dep
--- Comment #6 from kargl at gcc dot gnu dot org 2007-06-18 04:26 ---
In section 7.1.6.2 (which you sight), I find
A function is a specification function if it is a pure function, is not an
intrinsic function, is not an internal function, is not a statement function,
does not have
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2007-06-18 04:12
---
>From Fortran 95/2003 Explained, Metcalf. Reid, and Cohen
Page 101:
"The other way that automatic objects arise is through varying character
length. The variable word2 in
Subroutine example(word1)
ot org <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: [Bug fortran/32386] Pure function not allowed in specification
> expression
>
>
>
> --- Comment #2 from kargl at gcc dot gnu dot org 2007-06-18 01:46 ---
> According to Lahey, the code is i
ot gnu dot org <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: [Bug fortran/32386] Pure function not allowed in specification
> expression
>
>
>
> --- Comment #1 from jvdelisle at gcc dot gnu dot org 2007-06-18 01:00
> ---
> Not saying wheth
--- Comment #2 from kargl at gcc dot gnu dot org 2007-06-18 01:46 ---
According to Lahey, the code is invalid.
Lahey/Fujitsu Fortran 95 Source Check Output
Compiling program unit halvestring at line 1:
Compiling program unit testspec at line 9:
2049-S: "SOURCE.F90", line 13: Automati
--- Comment #1 from jvdelisle at gcc dot gnu dot org 2007-06-18 01:00
---
Not saying whether this is valid or not. However Intel ifort says:
fortcom: Error: john.f90, line 13: An automatic object is invalid in a main
program. [STRINGB]
CHARACTER(len(halfit(stringa))) :: stringb
