[MITgcm-devel] Strings and netcdf

[Chris Hill]

We do pass strings to c++ in esmf but its bundled with gizillion other
gizmos.

I think we should just go with lots of different link pathnames and move on.

Whats next? What is the status of parallel netCDF?

Chris 

> -----Original Message-----
> From: mitgcm-devel-bounces at mitgcm.org 
> [mailto:mitgcm-devel-bounces at mitgcm.org] On Behalf Of Ed Hill
> Sent: Wednesday, July 28, 2004 11:05 AM
> To: MITgcm-devel
> Subject: Re: [MITgcm-devel] Strings and netcdf
> 
> On Wed, 2004-07-28 at 09:44, Chris Hill wrote:
> > Hi Ed/Alistair,
> > 
> >  Whats the plan? Is it worth doing the fix so that strings don't go 
> > across the compiler - compiler interface explicitly? What 
> do you think?
> 
> 
> If we write a wiz-bang two-layer string conversion library 
> *only* to avoid compiling NetCDF for the different compilers, 
> then I think its a waste of time.
> 
> If we write a more general interface for calls between 
> Fortran and C/C++, then perhaps its worth the effort.  Has 
> something like this already been done with ESMF?  I 
> downloaded esmf_2_0_0rp2 last night, built the docs, and read 
> all about their NetCDF interface.  So far, they've punted on 
> a number of issues including basic things like:
> 
>   from ESMF_builddetail.tex:
>   "The current release of the system is prepared to link with the
>    {\tt netCDF} I/O libraries, but since the installation of the
>    libraries and include files varies widely from system to system
>    support for them is disabled by default."
> 
> Ed
> 
> --
> Edward H. Hill III, PhD
> office:  MIT Dept. of EAPS;  Rm 54-1424;  77 Massachusetts Ave.
>              Cambridge, MA 02139-4307
> emails:  eh3 at mit.edu                ed at eh3.com
> URLs:    http://web.mit.edu/eh3/    http://eh3.com/
> phone:   617-253-0098
> fax:     617-253-4464
> 
> _______________________________________________
> MITgcm-devel mailing list
> MITgcm-devel at mitgcm.org
> http://dev.mitgcm.org/mailman/listinfo/mitgcm-devel
>