[Mitgcm-support] Ptracers routine naming

[mitgcm-support at dev.mitgcm.org]

While we are at it, do you think we can rename

      SUBROUTINE PTRACERS_INTEGERATE

to

      SUBROUTINE PTRACERS_INTEGRATE

too! Or will that break setups that people have? 

Chris

> -----Original Message-----
> From: Martin Losch [mailto:mlosch at awi-bremerhaven.de] 
> Sent: Wednesday, March 19, 2003 9:54 AM
> To: support at mitgcm.org
> Subject: Re: package ptracer does not compile on SunOS
> 
> 
> Actually, there's another one, too:
> 
> ptracers_gterm_blocking_exchanges.F
> 
> In my own copy I renamed these files to
> ptracer_gterm_exchanges.F
> ptracer_fields_exchanges.F
> 
> 
> Martin
> 
> support at mitgcm.org wrote:
> > It looks like we may have to rename the routine! We'll look 
> into it further
> > but there doesn't seem to be a compiler option to deal with this 31
> > character limit.
> > 
> > More later,
> > 
> > A.
> > 
> > A quote from a google-groups search about the error message:
> > 
> >>>Why 31, I am curious:
> >>
> >>I am perfectly happy with the choice of 31:
> >>- It is the number of characters in the longest word of my native
> >>  language (at least, the longest word in my crossword 
> puzzle dictionary).
> >>- It is the maximum number of days in a calendar month, 
> even for leap
> > 
> > years.
> > 
> >>- It is an easy number to remember: 13 reversed, and 13, of 
> course, is the
> >>  difference between 77 and 90.
> >>- It is a prime number, and I like primes.
> >>
> >>Why should I want another value ?
> > 
> > 
> > 
> 
> 
> -- 
> Martin Losch
> Alfred Wegener Institute for Polar and Marine Research
> Postfach 120161, 27515 Bremerhaven, Germany;
> Tel./Fax: ++49(0471)4831-1872/1797
> 
>