[MITgcm-devel] exf_set_uv.F

[Alistair Adcroft]

JMC's soln's both work for me - despite the absence of a democrary I vote
for this.

Does "dimension" carry over to f90?

A.
--
Dr Alistair Adcroft            http://www.mit.edu/~adcroft
MIT Climate Modeling Initiative        tel: (617) 253-5938
EAPS 54-1523,  77 Massachusetts Ave,  Cambridge,  MA,  USA

-----Original Message-----
From: mitgcm-devel-bounces at mitgcm.org
[mailto:mitgcm-devel-bounces at mitgcm.org] On Behalf Of Jean-Michel Campin
Sent: Wednesday, March 24, 2004 4:18 PM
To: heimbach at mit.edu
Cc: MITgcm-devel at mitgcm.org
Subject: RE: [MITgcm-devel] exf_set_uv.F


Hi patrick,

What about this other solution (that i don't like too much):

a)  declare the type first:
    _RL uvec_lat0, uvec_lat_inc
b)  after the #ifdef USE_EXF_INTERPOLATION , declare the size:
    DIMENSION uvec_lat_inc(MAX_LAT_INC)

And this other one (that I prefer):
As it's done in many .h files, the common blocks can be placed 
within the appropriate #ifdef []  #endif block (so that, for 
instance, exf_param.h could be included without using memory space) 
but the declaration of dimension
       integer MAX_LAT_INC
       parameter(MAX_LAT_INC = 250)
would be left outside the #ifdef []  #endif block
and therefore available in S/R exf_set_uv.F 
to dimension S/R arguments.

Jean-Michel
_______________________________________________
MITgcm-devel mailing list
MITgcm-devel at mitgcm.org http://dev.mitgcm.org/mailman/listinfo/mitgcm-devel