[MITgcm-devel] removing SEAICE_GET_FORCING ?
Martin Losch
Martin.Losch at awi.de
Tue Dec 4 03:08:39 EST 2007
Yeah, yeah, yeah, get rid off SEAICE_EXTERNAL_FORCING and all the
stupid CPP-Flags that go with it, please.
On 4 Dec 2007, at 02:23, Dimitris Menemenlis wrote:
>
>> Also, at the same time, would be good to take the #include
>> "EXF_FIELDS.h"
>> out off SEAICE_FFIELDS.h
>
> Any suggestions how best to do that? This is equivalent to, e.g.,
> seaice accessing DYNVARS variables. The alternative of duplicating
> EXF_FIELDS.h in a pkg/seaice header seems like it could cause trouble?
I don't understand? Whereever there is a #include "SEAICE_FFIELDS.h",
you replace it by "EXF_FIELDS.h", and SEAICE_FFIELDS.h can be
removed. Unless you want to keep the possibility of adding a
different "exf-like" forcing package later, then I don't know.
Martin
More information about the MITgcm-devel
mailing list