JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for COMP-FORTRAN-90 Archives


COMP-FORTRAN-90 Archives

COMP-FORTRAN-90 Archives


COMP-FORTRAN-90@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

COMP-FORTRAN-90 Home

COMP-FORTRAN-90 Home

COMP-FORTRAN-90  March 2011

COMP-FORTRAN-90 March 2011

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: order of statements

From:

Andres Legarra <[log in to unmask]>

Reply-To:

Fortran 90 List <[log in to unmask]>

Date:

Tue, 29 Mar 2011 11:27:30 +0200

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (124 lines)

Hi,

the way I see it is that a guy (actually the compiler) is reading the 
code. In order to know how to allocate

d(k)

he needs to know the value for k.
Yes, it might be inconvenient. But I also found it logical (and clean) 
for human programmers to know and detail k before d(k).

Cheers
Andres




Le 29/03/2011 11:17, W.J. Metzger a écrit :
> Thanks for the reply,  However it is not an answer to what I intended to
> ask.  Let me rephrase the question.
>
> Type declarations, e.g.,  DoublePrecision d
> dimensions, e.g.,         Dimension d(2)
> common,                   common /c/ d
> can appear in any order.  But giving a name to a constant, e.g.,
>                           Parameter (k=5)
> must appear before the first use of the named constant, i.e.,
>                           Parameter (k=5, l=2*k)
> is fine, but
>                           Parameter (l=2*k, k=5)
> is not;
>                           Parameter (k=5)
>                           Dimension d(k)
> is fine, but
>                           Dimension d(k)
>                           Parameter (k=5)
> is not.
>
> I do not understand the logic of this.  I was hoping someone would 
> explain
> this.  It seems to me to be contradictory to the lack of a necessary 
> order
> for type, dimension, common, etc.
>
> Cheers, Wes
>
>
> On Mon, 28 Mar 2011, Andrew Chan wrote:
>
>> This is because KTMX has not got a value when the statement is 
>> processed. Thank you for your attention.
>>
>> Regards,
>>
>> Andrew
>>
>> -- 
>> You cannot change the past but you can improve the future by working 
>> on the present.
>> -- 
>> Eur. Ing. Prof. Andrew H.C. Chan: Professor in Computational Engineering
>> Deputy UG Admission Tutor, UG Admission day co-ordinator and Overseas 
>> UG Admission Tutor  for the School of Civil Engineering
>> Tel: +44 121 41 45100 Fax: +44 121 41 43675 Mobile: +44 77099 68522
>> Email: [log in to unmask] or [log in to unmask] webpage 
>> MSN Messenger: [log in to unmask] facebook skype: aquila_eagle 
>> twitter: andrewhcchan  Linkedin: [log in to unmask]
>>
>> -----Original Message-----
>> From: Fortran 90 List [mailto:[log in to unmask]] On 
>> Behalf Of W.J. Metzger
>> Sent: 28 March 2011 13:20
>> To: [log in to unmask]
>> Subject: order of statements
>>
>> It seems that the order of statements is important in the following,
>> since both ifort and gfortran give the same error.
>> But I don't understand why that must be so.  Could someone explain?
>>
>> This routine gives an error message
>>       Subroutine B (IFL, T, TA)
>>       Integer, Intent(IN)  :: IFL
>>       Real,    Intent(OUT) :: T(3,KTMX), TA(KTMX)
>>       Integer, Parameter :: KTMX=20
>>       t = ifl
>>       ta = ifl
>>       End Subroutine B
>>
>> But the following two variations of it do not
>>       Subroutine G1 (IFL, T, TA)
>>       Integer, Intent(IN)  :: IFL
>>       Real,    Intent(OUT) :: T, TA
>>       Integer, Parameter :: KTMX=20
>>       Dimension T(3,KTMX), TA(KTMX)
>>       t = ifl
>>       ta = ifl
>>       End Subroutine G1
>>
>>       Subroutine G2 (IFL, T, TA)
>>       Integer, Parameter :: KTMX=20
>>       Integer, Intent(IN)  :: IFL
>>       Real,    Intent(OUT) :: T(3,KTMX), TA(KTMX)
>>       t = ifl
>>       ta = ifl
>>       End Subroutine G2
>>
>>
>>
>> -- 
>> Dr. W. J. Metzger            Experimental High Energy Physics Group
>> tel. +31-24-3653127          Faculty of Science
>>      +31-24-3652099 (secr.)  Radboud University Nijmegen
>> fax. +31-24-3652191          Heyendaalseweg 135
>>                              6525 AJ  Nijmegen,  The Netherlands
>> e-mail:  [log in to unmask]       or   [log in to unmask]
>> http://home.cern.ch/metzger/ or   http://www.hef.ru.nl/~wes
>

-- 
Andres Legarra
+33 561285182
INRA, UR 631 SAGA
BP 52627
31326 Castanet Tolosan, France

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

September 2018
August 2018
July 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
December 2015
November 2015
October 2015
September 2015
August 2015
June 2015
April 2015
March 2015
January 2015
December 2014
November 2014
October 2014
August 2014
July 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
July 2013
June 2013
May 2013
April 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
August 2010
July 2010
June 2010
March 2010
February 2010
January 2010
December 2009
October 2009
August 2009
July 2009
June 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
January 2007
2006
2005
2004
2003
2002
2001
2000
1999
1998
1997


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager