Re: Integer Coersion
- From: glen herrmannsfeldt <gah@xxxxxxxxxxxxxxxx>
- Date: Thu, 08 Feb 2007 00:33:15 -0800
Richard Maine wrote:
(snip)
The term you are looking for is still "initialization expression". The
concept "compile time" does not exist in the language. It is certainly
true that initialization expressions are designed to be doable at
compile time, but that is not a specification of the standard, which
doesn't even have the concept of a compiler at all.
Yes, but there are some things that in most implementations need
to be known before the program starts executing. COMMON and EQUIVALENCE
tend to work that way and, standard or not, people tend to know what
it means to be known at compile time. I would really be surprised
if:
COMMON /X/ A(N),B(N)
READ(*,*) N
READ(*,*) A(1),B(1)
worked, for example. I did look at the description of both initialization expression and specification expression, but I can't
say that I know which one disallows the above COMMON.
-- glen
.
- Follow-Ups:
- Re: Integer Coersion
- From: *** Hendrickson
- Re: Integer Coersion
- From: Richard Maine
- Re: Integer Coersion
- References:
- Integer Coersion
- From: PJH
- Re: Integer Coersion
- From: David Frank
- Re: Integer Coersion
- From: Steven G. Kargl
- Re: Integer Coersion
- From: glen herrmannsfeldt
- Re: Integer Coersion
- From: James Giles
- Re: Integer Coersion
- From: glen herrmannsfeldt
- Re: Integer Coersion
- From: Richard Maine
- Re: Integer Coersion
- From: glen herrmannsfeldt
- Re: Integer Coersion
- From: Richard Maine
- Integer Coersion
- Prev by Date: Re: How to compile XFoil with FTN95?
- Next by Date: Re: Integer Coersion
- Previous by thread: Re: Integer Coersion
- Next by thread: Re: Integer Coersion
- Index(es):