Re: Syntax check for IMPLICIT statement
- From: glen herrmannsfeldt <gah@xxxxxxxxxxxxxxxx>
- Date: Sun, 27 Apr 2008 17:45:16 -0800
Michael Metcalf wrote:
"James Van Buskirk" <not_valid@xxxxxxxxxxx> wrote in message news:wpmdnYLdJ7wLl4jVnZ2dnUVZ_jednZ2d@xxxxxxxxxxxxxx
In attempting to create a digestible version of a program that gives
gfortran an ICE and causes incorrect output for ifort, the critical
factor for both seems to be a line such as:
implicit character(len=*,kind=kind('A')) (Q)
"For a scalar named constant or for a dummy argument ... a len-value may be specified as an asterisk" ("Fortran 95/2003 Explained", Section 7.13).
Even so, it shouldn't ICE.
Still, I don't see, as James seems to believe, that dummy arguments and named constants (also, external functions) can't be done through
IMPLICIT. It might be bad style, but is it illegal?
Does it only fail if used in a MODULE?
-- glen
.
- References:
- Syntax check for IMPLICIT statement
- From: James Van Buskirk
- Re: Syntax check for IMPLICIT statement
- From: Michael Metcalf
- Syntax check for IMPLICIT statement
- Prev by Date: Re: Bug in gfortran when reading end of file?
- Next by Date: Re: gfortran produces huge executables
- Previous by thread: Re: Syntax check for IMPLICIT statement
- Next by thread: Re: Syntax check for IMPLICIT statement
- Index(es):
Relevant Pages
|
|
